It's been a while since our last (and first) release, and I think times
are ripe for a new one - alpha2.
This new release would mainly consist in wrapping up all working
functionalities that we currently have, making sure that they really are
working, and rolling out all corresponding native installers and jars.
I hope that we would be able to speed up our release loop after that and
be able to bring out alpha3 (that, among other things would include FMJ
and would no longer have the J1.4 compatibility condition).
The list of issues that we need to address before rolling out the
release is here:
During the following days we will decide what else we need to add there
and what are the issues that we need to push back to alpha3. Generally
however, I wouldn't want to see anything that would take more than a
couple of hours of work in it. As I said, the purpose of this release is
to simply wrap up everything working and put a release stamp on the
Yana would shortly create an alpha2 SVN branch and we will be using it
as the source for the release.
I've asked Romain Kuntz to be our release manager for alpha2 and he has
accepted. When describing the role of a release manager I like using a
quotation from Richard Hall that he once sent to the Felix mailing list:
"The release manager is the person who is responsible for making sure
all of the T's are crossed and all of the I's are dotted when we go to
make a release (e.g., making sure we have the appropriate LICENSE and
NOTICE everywhere they are supposed to be, tagging the release, signing
the release, etc.)."
Developers should therefore be prepared to receive a fair amount of
prodding from Romain during the following weeks as he would be following
the status of all alpha2 issues, and making sure that someone would
either take care of them or push them back to alpha3.
Good luck to all, and let's hope we'll soon pop the bubbly!