Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[aspectj-dev] Schedule options for AspectJ 1.2 release


I propose the following strategy for the management of the AspectJ 1.2 release schedule:

We'd like to put a release out in time for the AOSD 2004 conference, week of 22nd March. Ideally this would be the 1.2 final release. To get there, we'll need a release candidate out around the last week of February, to give users a chance to report any remaining bugs. I propose we shoot for these dates - if things go well with the first release candidate we'll put out 1.2 final in March, otherwise we'll put out a second release candidate, and delay the final release until we have achieved the desired quality levels.

Note that this strategy does not include alpha or beta releases as we have done before. This is for 2 reasons - (1) the package, test and release cycle consumes precious project resources everytime we go through it, time that could be spent improving the quality of the code base instead, and (2) since our last release we have an introduced a stage to our automated build process that posts the results of the most recent build to Eclipse.org, making it easy for alpha and beta testers to download the most recent build at any time. If we change the cruise control scripts so that the aspectj-DEVELOPMENT.jar is only posted to eclipse.org when a build passes all of the test suite, then this will effectively become the 'best-so-far' build. Part of the release strategy would then be to publicize more widely the location of the install jar (i.e. to aspectj-users) so that those who want to participate in early testing can do so.

If we find we cannot make a release candidate by the end of February for any reason, then rc1 will instead go out in March in time for the AOSD conference, but I hope that this delay will not be necessary.

-- Adrian
Adrian_Colyer@xxxxxxxxxx

Back to the top