If you're working on a fix that requires a specific fix and is not
something that is in ongoing, high-flux development then can people
release first and then incorporate.
Two example of late are plexus-utils in trunk, and the Maven parent POM.
Snapshots are for intra-project, high-flux development. Having them
as external dependencies is not good. We either have to change
repository settings around which sucks, or things are very well
tested. For the Maven parent POM I can't use it in the branch because
it's not released, and it causes a CCE in the remote-resources plugin
(Kulp, you may want to look at that, it's a CCE between and
ArtifactRepository and org.apache.maven.model.Repository).
I don't think there's any problem with pushing out tons of micro
releases and just makes things far more stable (and releasable).
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
