<snip>I want to propose the following:
- I like to call a vote on merging the J2 deployment_refactoring branch with
CVS HEAD before the end of *this week*
No objection here as long as everybody is aware that this will break Fusion for a few days.
> <snip>
- Hopefully, beginning next week we have both J2 and Fusion in sync again
- If all works out well, I'll propose to do a J2-M2 release as well as a
Fusion 1.6 release next weekend (!) as I can dedicate most of my time that
weekend doing the release.
I haven't done a release before though, so getting at least some help from
someone from the team with previous experience will be important I think.
Now that seems to me overly ambitious because it means we'll have a mostly untested release.
I don't mind having a Jetspeed M2 going out this way but I think Jetspeed 1.6 requires more testing as it is probably the last major release of Jetspeed 1, it should be as stable as possible.
How about releasing a Jetspeed M2 and a Jetspeed 1.6 RC1 at this time. Advertise the 1.6 RC1 so that users can test out the binary. If no major issue is raised on RC1, rerelease it as 1.6 final about 1 or 2 weeks after ?
- Furthermore, I'd like to propose to do releases more often (say once every
month, maybe two) at least until we reach J2-final.
The next release (M3) could contain the portlet selector (customizer)
from David if he won't be able to commit it in time for M2.
Furthermore, we should try to get most of the outstanding bugs fixed by then.
I'm willing to work on that a lot.
+1 for more releases on J2 until we reach 1.0 but then again, historically development on Jetspeed occurs in waves of big activity when some committers have time to work the project followed by a general
slow down when everybody needs to catch up with real work. It has been like this at least since Jetspeed 1.2b1 :)
Because of this, releases are rarely created on a regular basis.
- Furthermore, I am going to spend more time in April on writing documentation
as the community really is in dire need of it. I'd say the M3 release should
contain enough documentation to allow new users to start working with J2
on their own.
Hopefully, other team members and/or active community users can step up too
in providing more documentation...
++1 on the documentation effort.
-- Rapha�l Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
