Ok, as I understand the current system, we'd need a GA release of all
the subprojects, including Action 1, in order to declare a GA 1.3 release.
How much work does those involved think this will be? If a bit, I'm
thinking it might be easier in the long run to go ahead, consolidate the
subprojects, and even merge a few like taglibs and EL. Then, we can
push for a single release instead of having to roll and evaluate the 6
subprojects, each might take a few releases to get GA.
I'm willing to defer to those who have been doing all the hard work to
get this far, and I'd like to help do whatever it takes to get a stable
release out there. I'm just wondering if one larger release will be
quicker and easier than 6 releases. In fact, here is an idea at how to
getting a release out ASAP and make Action easier to manage:
- Put all subprojects under Action 1
- Merge Faces into Extras
- Merge EL into taglibs
- Get strict with tickets - only let bugs hold us up, and then, only
ones we agree should hold us back. Most projects ship with bugs, just
we'd make sure to document them.
Bottom line, the fewer subprojects and even "modules", the quicker a GA
release will happen and the easier the project will be to manage. We
are _way_ overdue on this release and I'm now hearing some literally
don't think it will _ever_ be finished, and worse, that we don't care.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
