I think we are in a good shape to post the actual release. I've done
fairly extensive testing and fixed a number of last minute bugs (see
my earlier emails). I am wrapping up with documentation work.
Since this is the first release of an unstable branch done using a
new build system (Maven), I think we may deviate from our earlier
procedure of doing a coordinated release testing over IRC. I suspect
the testing can take more time, so we should do it offline.
So I suggest this:
1. Once I am done with documentation checkins, I will create a
release tag in SVN (tonight)
2. I will also post a Maven snapshot of the code in the snapshot repo
3. Myself and others who volunteer to help should check out the tag
and try to run unit tests against various DB's (I would also
encourage build local assemblies and see if they look any good, i.e.
the Modeler starts, all the jars are in place), etc.
4. Also somebody needs to check the tag code with RAT tool. Any
volunteers to do that? If not I will do it.
5. Once we hear back from everybody involved, I can post signed
release artifacts for the vote. I expect this to happen within 4-5 days.
Does this plan look ok?
Andrus
