On 18/06/2007, at 1:52 AM, Jason van Zyl wrote:
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).
I was going to take care of that very shortly, but wanted to make
sure it was at least correct first. Using v5 was not - the gpg plugin
that was included did not work with the assemblies (as you can see
from your staging repository: http://people.apache.org/~jvanzyl/
maven-2.0.7-staging-repository/org/apache/maven/maven/2.0.7/ - the
signatures are all missing -src).
As I understood it, you weren't going to do anything from the branch
again. If I'd known that, I'd have suggested you stage and release
the parent too.
I'll call a vote on it today.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
