Apropos to this and to the IT/development expectations, is the Maven
2.1.x process going to have strong infrastructure around build
automation? At this point, I think Continuum 1.1-alpha-* builds are
probably stable enough to be used for CI, and a secondary "build
fresh" nightly build and an interation/milestone build could easily
be scheduled. This nightly build could be scooped off and staged
somewhere for testing.
I think this would free up the developers from mindless staging of
non-release, or partial release builds, and keep people focused on
architectural and developmental progress.
I'd be willing to do some scut-work around this, taking care of some
infrastructure hassle if it'll help move the process forward. I'm
not deeply comfortable with plexus and maven internals yet to really
keep up with this crowd in terms of development, but if I can help to
clear the way at all, please let me know.
Christian
On Jun 21, 2007, at 10:56 PM, Brett Porter wrote:
5) map out the incremental releases (around 4 weeks apart for 2.1-
alpha-1, alpha-2, etc), and which jiras are incorporated
I think until the first beta arrives bash them out as fast as
possible. We can start his anytime provide people are aware that
it's alpha and though pretty stable they use it at their own risk
and if you use it for production builds you will have an exciting
time.
Yeah, I'm happy with that, probably just a matter of terminology,
though - great to have regular stable builds, but if you look at
what IDEA do they have both really regular builds, then milestones
where the less brave can still try it out, then betas, then final,
which is a good model.
christian gruber + [EMAIL PROTECTED] + mob 410.900.0796 + mob2
416.998.6023
process coach and architect + ISRÁFÍL CONSULTING SERVICES
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
