[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Re: [eclipse.org-planning-council] Re: Re-spin process
|
Nick,
Is site-interim.xml the site where you publish bug fixes for your most
recent R-build or is this the site where you publish coming work on the
next minor release?
The reason I'm asking is that I think that many projects might want a
faster pace on minor releases then once a year and thus, have a new
minor release included in a Europa maintenance release. If permitted, it
brings up the question of what should be allowed on the suggested "open
stream". If that stream reflects the work towards the maintenance
release, there might be need for an additional and more restrictive "bug
fix stream" that honors the contract of not changing anything but the
bug fix number and qualifier.
"Closed stream"
Per Johns suggestion. Very high bar for changes.
"Bug fix stream"
Permits changes to bug fix number and qualifier (should not break
downstream projects). Re-spin on request.
"Europa Fall Update stream"
Like "Europa Staging" was before the release. Based on Eclipse 3.3 and
updated on green builds. Re-spin nightly.
I think both the "Closed stream" and the "Bug fix stream" can be very
appealing to end-users. The ones John mention that really have a need
for a frozen release will get that and everyone else, who just wants to
keep their IDE to up to date, can do that too without the burden of
locating all included update sites.
Regards,
Thomas Hallgren
Nick Boldt wrote:
+1 for the "non-moving target" / "Europa is a release" idea.
+1 also for the "closed / open versions" -- in EMF/EMFT/MDT/M2T we
have two update sites for exactly this purpose: one for Releases and
one for everything else (Maintenance, Integration, Stable, Milestone).
If Europa wanted to adopt this convention, here's an example of how we
do things [1], [2]:
In this case, the R builds are still the default value found in the
/updates/ folder, and linked from our feature.xml files. However,
those wanting the bleeding edge can go here [3] and be told about the
other optional site.
[1] http://download.eclipse.org/modeling/m2t/updates/site.xml (R builds)
[2] http://download.eclipse.org/modeling/m2t/updates/site-interim.xml
(I, M, S builds)
[3] http://www.eclipse.org/modeling/m2t/updates/
Cheers,
Nick
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
