|[eclipse.org-planning-council] RE: [cross-project-issues-dev] Re: Re-spin process|
There are a lot of great points about leveraging internet style continuous update vs. package software releases. Putting the debate aside, I would like to get input of a solutions on the problems we have at hand with BIRT project...
The specific issue we have is a missing plugin dependency in a feature definition. It prevents user from using update manager to download BIRT thru Europa Discovery site when the user ONLY selects BIRT and click “Select Required…” . If user selects both BIRT and DTP, he/she will not have this issue. It was a testing hole pre-release, since we always select DTP, WTP along with BIRT. We shall add such test case in the future.. But I suspect that we won't be able to test all the combinations of feature selections on the update site to discover all the missing dpendencies. The request of re-spin is to add the plugin depdency in a feature so that user will get all the required plugins installed for BIRT.
From: cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of Bjorn Freeman-Benson
Sent: Sun 7/8/2007 8:15 PM
To: Cross project issues; eclipse.org-planning-council
Subject: [cross-project-issues-dev] Re: Re-spin process
While not as appalled as Doug, I do agree that re-spinning brings up the question of whether the bits were truly ready for release. Of course there are always bugs (sigh), but part of the Europa-mature release process was to limit the set of those to the Fall and Winter Maintenance Releases.
At the same time, I like John's concept of the open and closed streams.
Back to the top