You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Kenney Westerhof <fo...@neonics.com> on 2005/09/13 14:49:34 UTC
Release Phase? (was Re: svn commit: r280540 - in
/maven/components/trunk: maven-plugins/pom.xml pom.xml)
On Tue, 13 Sep 2005, Emmanuel Venisse wrote:
Hi, I've got some questions on the release phase in general:
I can't find any document describing the release process (except the
release plan).
For instance, since voting isn't finished yet - when is the version
tagged, or, which revision will be used?
What can be changed when voting starts, or aren't there supposed to be any
commits until the voting ends?
And about this part from the release plan:
Test each plugin's new release with alpha-3 and release in advance
* Peg to released versions of Maven, which should all be in dependency
management section of the parent
* Deploy parent
* Resolve any snapshots in the plugin
* Test and release individual plugins using release plugin
Does this mean that the beta-1 plugins will depend on maven 2.0-alpha-3?
I can't find a part that sais 'upgrade plugin deps to beta-1'..
Plus, very few plugins will work (i guess none) with alpha-3.
-- Kenney
> Thanks, you can't introduce new snapshots in a release phase
>
> Emmanuel
>
> kenney@apache.org wrote:
> > Author: kenney
> > Date: Tue Sep 13 04:44:19 2005
> > New Revision: 280540
> >
> > URL: http://svn.apache.org/viewcvs?rev=280540&view=rev
> > Log:
> > Changed modello-maven-plugin version to 1.0-alpha-4 since alpha-5
> > hasn't any snapshots released yet.
> >
> > Modified:
> > maven/components/trunk/maven-plugins/pom.xml
> > maven/components/trunk/pom.xml
> >
> > Modified: maven/components/trunk/maven-plugins/pom.xml
> > URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/pom.xml?rev=280540&r1=280539&r2=280540&view=diff
> > ==============================================================================
> > --- maven/components/trunk/maven-plugins/pom.xml (original)
> > +++ maven/components/trunk/maven-plugins/pom.xml Tue Sep 13 04:44:19 2005
> > @@ -147,7 +147,7 @@
> > <dependency>
> > <groupId>org.codehaus.modello</groupId>
> > <artifactId>modello-maven-plugin</artifactId>
> > - <version>1.0-alpha-5-SNAPSHOT</version>
> > + <version>1.0-alpha-4</version>
> > </dependency>
> > </dependencies>
> > </dependencyManagement>
> >
> > Modified: maven/components/trunk/pom.xml
> > URL: http://svn.apache.org/viewcvs/maven/components/trunk/pom.xml?rev=280540&r1=280539&r2=280540&view=diff
> > ==============================================================================
> > --- maven/components/trunk/pom.xml (original)
> > +++ maven/components/trunk/pom.xml Tue Sep 13 04:44:19 2005
> > @@ -175,7 +175,7 @@
> > <dependency>
> > <groupId>org.codehaus.modello</groupId>
> > <artifactId>modello-maven-plugin</artifactId>
> > - <version>1.0-alpha-5-SNAPSHOT</version>
> > + <version>1.0-alpha-4</version>
> > </dependency>
> > </dependencies>
> > </dependencyManagement>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release Phase? (was Re: svn commit: r280540 - in /maven/components/trunk:
maven-plugins/pom.xml pom.xml)
Posted by Brett Porter <br...@apache.org>.
Kenney Westerhof wrote:
>On Tue, 13 Sep 2005, Emmanuel Venisse wrote:
>
>Hi, I've got some questions on the release phase in general:
>
>I can't find any document describing the release process (except the
>release plan).
>
>
It would certainly be good to document. I think we've almost got it down
now, so that should be feasible.
>For instance, since voting isn't finished yet - when is the version
>tagged, or, which revision will be used?
>What can be changed when voting starts, or aren't there supposed to be any
>commits until the voting ends?
>
>
This can often go either way. I usually vote first, based on the svn rev
of the time, limiting changes to feedback coming from that voting,
preparing test bundles and getting more feedback before releasing.
Jakarta commons, on the other hand, produce the release first, then vote
(then apply changes, vote again, and so on for a few RCs).
>And about this part from the release plan:
>
> Test each plugin's new release with alpha-3 and release in advance
>
> * Peg to released versions of Maven, which should all be in dependency
> management section of the parent
> * Deploy parent
> * Resolve any snapshots in the plugin
> * Test and release individual plugins using release plugin
>
>Does this mean that the beta-1 plugins will depend on maven 2.0-alpha-3?
>I can't find a part that sais 'upgrade plugin deps to beta-1'..
>
>
This would have been ideal (have them work with the oldest release
possible).
>Plus, very few plugins will work (i guess none) with alpha-3.
>
>
>
Unfortunately this was the case due to some significant changes. Won't
happen next time, and I don't expect to be doing plugin releases at the
same time as the core again.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org