Jason van Zyl wrote:
Hi,
I want to call a vote for 2.0.5. All the issues that are going to get
done are done. We'll release and move on.
I would like to start building all releases from a standard machine with
the same JDK. I would like to propose the maven.org machine which is
monitored 24/7 running Linux. It serves as the central repository but
can easily handle a few builds. They can be built from that machine and
deployed to Apache. I think this is far better then each of us building
stuff from our own machines and deploying.
Otherwise everything for 2.0.5 is ready to go.
Then I think it should be released.
I will also chop up what's in JIRA into some smaller versions as I think
some micro releases for improvements and smaller changes is better then
waiting 7 months for another release. If we schedule them out them
people can decide whether they want to upgrade or not. But I know there
are several things I would like to get in and I know that Mike/Ralph
would like to get in MNG-1577 which we can squeeze into a 2.0.6 in a
week or two. These are micro release.
I don't think micro releases is the way to go in general, if you define
micro releases to be in the scale of a a couple of weeks. The 7 months
that has passes since 2.0.4 is too long, don't get me wrong but having
very frequent micro releases is just going to confuse people and lead to
inconsistent developer environments.
Just a though on making bi-weekly/monthly micro releases the new way.
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
