Ate Douma wrote: <snip>
- 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.
I know. Still, I hope to do (much) more the next few weeks/months and I would like to target a J2-final before this summer. Its long overdue in my opinion and we simple *must* step up our effort if we don't want to get too far behind and lose community support...
Because each release carries some overhead we have to keep the number of intermediate releases down.
I propose that we plan for J2-final (June) and decide if a release is needed between M2 and J2-final.
The M2 release will slow down development since it needs to be synchronized with J1-Fusion and a lot of refactoring will go in. Once we get up to speed again we shouldn't be slow down with another release.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
