Antoine Levy-Lambert wrote:
Kev Jackson wrote:
Hi,
Checked the planning wiki this morning and noticed that the release
schedule for the first beta of 1.7 is set at May/June this year.
Since this is rapidly approaching, what are the thoughts on
a: timing,
each release requires a vote. A vote is open one week. but the next
issues are more important
b: fixes/features that still need to go in before release
the wiki says this :
*
Fix for key IDE bugs (see eclipse, netbeans bugzillas) [all]
*
<classloader> to allow adding of jars to the current classloader
(would solve a /lot/ of problems at the cost of some
issues)[peter] (status RE "some issues" risk? -MJB)
*
Junit 4 integration to a level that Ant-dev and junit are happy.
Who can take care of what here ? Which are the key IDE bugs ?
I agree that this list as it stands is a little vague. Junit 4
integration would be another case of having special code to deal with a
Java5 environment.
c: anything else
I see issues/questions/improvement points concerning the release process
Some points spring to my mind :
- signing of zips, tgzs, ...
I did this manually for 1.6.x. Stefan Bodewig had informed us of the
development of the openpgp module of jakarta commons [2].
We should check if this works for us and somehow bundle this in the build.
So as part of the release target, openpgp is used to sign the archives
created - sounds good to me
- release instructions
the release instructions need to be updated for subversion. I never
created branches in subversion ...
Branching in svn is pretty easy, but as far as I know, svn does a lazy
copy - ie it doesn't copy files over to the branch until there's a
change recorded - just something to be aware of
- branches
we will need to decide if we will want to branch ant, and if yes when.
Experience from the 1.6 time showed that during a long time we did
double maintenance of 1.6 branch and HEAD.
We might want to delay the creation of a 1.7 branch until there is a say
at least 1.7.1 ...
- antlibs
do we want to release antunit, dotnet and svn antlibs at the same time ?
or parallel ?
Should each antlib be in principle like an independent project and have
its own release instructions ?
Since 1.7 is the first version to properly support antlibs, wouldn't it
make sense to release the first batch of ant libs at the same time, but
then after to have them on their own release schedules?
- dependencies of ant
we have removed from the build 4 external jars which were not to be
found anymore anywhere. Still, gathering the dependencies is a problem
for the release manager.
For instance to get the weblogic.jar I downloaded an eval version of
weblogic. (Lengthy process involving registration ...).
I have this jar if anyone needs it (WebLogic 8.1, I also have 9 too I
think). I agree that getting that particular jar is a pain - thankfully
we don't have any oracle dependencies - that website always makes me
want to kill kittens - I don't know how much user unfriendly they can be.
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
