|
View:
New views
11 Messages
—
Rating Filter:
Alert me
|
|
|
Site Update for Maven 3.0-alpha-3Hi,
I noticed that we didn't mention previous alphas of 3.0 on the Maven site. How do we want to go about that with alpha-3? To attract more testers, I think we should have this alpha listed in the download section. E.g. some structure like * Stable Releases 2.2.1 2.1.0 2.0.10 * Alpha/Beta Releases 3.0-alpha-3 * Previous Releases WDYT? Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3Can't hurt. I have no problem promoting alpha-3. It's the best Maven
that's existed. I say go for it. On 2009-11-13, at 12:59 AM, Benjamin Bentmann wrote: > Hi, > > I noticed that we didn't mention previous alphas of 3.0 on the Maven > site. How do we want to go about that with alpha-3? > > To attract more testers, I think we should have this alpha listed in > the download section. E.g. some structure like > > * Stable Releases > 2.2.1 > 2.1.0 > 2.0.10 > * Alpha/Beta Releases > 3.0-alpha-3 > * Previous Releases > > WDYT? > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote: > Hi, > > I noticed that we didn't mention previous alphas of 3.0 on the Maven site. How do we want to go about that with alpha-3? > > To attract more testers, I think we should have this alpha listed in the download section. E.g. some structure like > > * Stable Releases > 2.2.1 > 2.1.0 > 2.0.10 > * Alpha/Beta Releases > 3.0-alpha-3 > * Previous Releases > > WDYT? +1, though I think we can remove 2.1.0 from the list as it is superceded by 2.2.1. When I started trying to automate more of the release process for 2.0.11, I already did this (moved to a branch now): http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=792808&r2=792807&pathrev=792808 There was general support, but I also split the release notes which raised some concerns. And then I ran out of spare time with my holiday, etc. :) I believe consensus was: - use JIRA as the authoritative source for release notes - support the split structure provided above for posting online (later moving to pull information from JIRA) - also produce an aggregated release notes (I believe for a series, not all releases), which can be done automatically So, options: - merge down just the bits that split into stable / preview versions - fix the aggregated release notes and merge the lot Thoughts? I'll update the branch for current versions. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3On 13/11/2009, at 11:28 AM, Brett Porter wrote: > > > On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote: > >> Hi, >> >> I noticed that we didn't mention previous alphas of 3.0 on the Maven site. How do we want to go about that with alpha-3? >> >> To attract more testers, I think we should have this alpha listed in the download section. E.g. some structure like >> >> * Stable Releases >> 2.2.1 >> 2.1.0 >> 2.0.10 >> * Alpha/Beta Releases >> 3.0-alpha-3 >> * Previous Releases >> >> WDYT? > > +1, though I think we can remove 2.1.0 from the list as it is superceded by 2.2.1. > > When I started trying to automate more of the release process for 2.0.11, I already did this (moved to a branch now): > > http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=792808&r2=792807&pathrev=792808 > > There was general support, but I also split the release notes which raised some concerns. And then I ran out of spare time with my holiday, etc. :) > > I believe consensus was: > - use JIRA as the authoritative source for release notes > - support the split structure provided above for posting online (later moving to pull information from JIRA) > - also produce an aggregated release notes (I believe for a series, not all releases), which can be done automatically > > So, options: > - merge down just the bits that split into stable / preview versions > - fix the aggregated release notes and merge the lot > > Thoughts? > > I'll update the branch for current versions. I've updated the branch here: http://svn.apache.org/repos/asf/maven/site/branches/release-presentation What would be required to add a new release is illustrated here: http://svn.apache.org/repos/asf/maven/site/branches/release-presentation/README.txt I've staged a sample site here: http://people.apache.org/~brett/staged-maven-site/ Alpha 3 is on the download page only, and release notes are drafted: http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html The aggregated release notes are here: http://people.apache.org/~brett/staged-maven-site/release-notes-all.html Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3IMO 2.1.0 should stay as it is, if I'm not mistaken, most recent stable
release of maven which is compatible with Java 1.4. When maven 2.2.1 is configured as default external maven installation m2eclipse 0.9.9 refuses to build projects (like maven core plugins) which still require Java 1.4. Maybe 2.0.10 could be removed instead. Regards, Stevo. On Fri, Nov 13, 2009 at 5:25 AM, Brett Porter <brett@...> wrote: > > On 13/11/2009, at 11:28 AM, Brett Porter wrote: > > > > > > > On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote: > > > >> Hi, > >> > >> I noticed that we didn't mention previous alphas of 3.0 on the Maven > site. How do we want to go about that with alpha-3? > >> > >> To attract more testers, I think we should have this alpha listed in the > download section. E.g. some structure like > >> > >> * Stable Releases > >> 2.2.1 > >> 2.1.0 > >> 2.0.10 > >> * Alpha/Beta Releases > >> 3.0-alpha-3 > >> * Previous Releases > >> > >> WDYT? > > > > +1, though I think we can remove 2.1.0 from the list as it is superceded > by 2.2.1. > > > > When I started trying to automate more of the release process for 2.0.11, > I already did this (moved to a branch now): > > > > > http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=792808&r2=792807&pathrev=792808 > > > > There was general support, but I also split the release notes which > raised some concerns. And then I ran out of spare time with my holiday, etc. > :) > > > > I believe consensus was: > > - use JIRA as the authoritative source for release notes > > - support the split structure provided above for posting online (later > moving to pull information from JIRA) > > - also produce an aggregated release notes (I believe for a series, not > all releases), which can be done automatically > > > > So, options: > > - merge down just the bits that split into stable / preview versions > > - fix the aggregated release notes and merge the lot > > > > Thoughts? > > > > I'll update the branch for current versions. > > I've updated the branch here: > http://svn.apache.org/repos/asf/maven/site/branches/release-presentation > > What would be required to add a new release is illustrated here: > http://svn.apache.org/repos/asf/maven/site/branches/release-presentation/README.txt > > I've staged a sample site here: > http://people.apache.org/~brett/staged-maven-site/<http://people.apache.org/%7Ebrett/staged-maven-site/> > > Alpha 3 is on the download page only, and release notes are drafted: > http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html<http://people.apache.org/%7Ebrett/staged-maven-site/docs/3.0-alpha-3/release-notes.html> > > The aggregated release notes are here: > http://people.apache.org/~brett/staged-maven-site/release-notes-all.html<http://people.apache.org/%7Ebrett/staged-maven-site/release-notes-all.html> > > Cheers, > Brett > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > > |
|
|
Re: Site Update for Maven 3.0-alpha-3Brett Porter wrote:
> I've staged a sample site here: http://people.apache.org/~brett/staged-maven-site/ +1, I like the proposed structure. Just one minor thing: I believe the JAR/PDF of the site should be listed separately as currently and not be part of the table listing the 2.2.1 downloads. The site is meant to cover various Maven versions so I consider the structure at http://people.apache.org/~brett/staged-maven-site/download.html irritating as it suggests the docs are meant specifically for 2.2.1. > Alpha 3 is on the download page only, and release notes are drafted: http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html Thanks, I happily grabbed that and copied it over to the trunk. Before we completely merge the branch to trunk, we should look into releasing the updated plexus-velocity component. There are already enough snapshot things involved in the site for my taste. Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3The stable versions are 2.0.10 and 2.2.1, 2.1.0 is not considered stable.
On Fri, Nov 13, 2009 at 1:59 AM, Stevo Slavić <sslavic@...> wrote: > IMO 2.1.0 should stay as it is, if I'm not mistaken, most recent stable > release of maven which is compatible with Java 1.4. When maven 2.2.1 is > configured as default external maven installation m2eclipse 0.9.9 refuses to > build projects (like maven core plugins) which still require Java 1.4. Maybe > 2.0.10 could be removed instead. > > Regards, > Stevo. > > On Fri, Nov 13, 2009 at 5:25 AM, Brett Porter <brett@...> wrote: > >> >> On 13/11/2009, at 11:28 AM, Brett Porter wrote: >> >> > >> > >> > On 13/11/2009, at 10:59 AM, Benjamin Bentmann wrote: >> > >> >> Hi, >> >> >> >> I noticed that we didn't mention previous alphas of 3.0 on the Maven >> site. How do we want to go about that with alpha-3? >> >> >> >> To attract more testers, I think we should have this alpha listed in the >> download section. E.g. some structure like >> >> >> >> * Stable Releases >> >> 2.2.1 >> >> 2.1.0 >> >> 2.0.10 >> >> * Alpha/Beta Releases >> >> 3.0-alpha-3 >> >> * Previous Releases >> >> >> >> WDYT? >> > >> > +1, though I think we can remove 2.1.0 from the list as it is superceded >> by 2.2.1. >> > >> > When I started trying to automate more of the release process for 2.0.11, >> I already did this (moved to a branch now): >> > >> > >> http://svn.apache.org/viewvc/maven/site/trunk/pom.xml?r1=792808&r2=792807&pathrev=792808 >> > >> > There was general support, but I also split the release notes which >> raised some concerns. And then I ran out of spare time with my holiday, etc. >> :) >> > >> > I believe consensus was: >> > - use JIRA as the authoritative source for release notes >> > - support the split structure provided above for posting online (later >> moving to pull information from JIRA) >> > - also produce an aggregated release notes (I believe for a series, not >> all releases), which can be done automatically >> > >> > So, options: >> > - merge down just the bits that split into stable / preview versions >> > - fix the aggregated release notes and merge the lot >> > >> > Thoughts? >> > >> > I'll update the branch for current versions. >> >> I've updated the branch here: >> http://svn.apache.org/repos/asf/maven/site/branches/release-presentation >> >> What would be required to add a new release is illustrated here: >> http://svn.apache.org/repos/asf/maven/site/branches/release-presentation/README.txt >> >> I've staged a sample site here: >> http://people.apache.org/~brett/staged-maven-site/<http://people.apache.org/%7Ebrett/staged-maven-site/> >> >> Alpha 3 is on the download page only, and release notes are drafted: >> http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html<http://people.apache.org/%7Ebrett/staged-maven-site/docs/3.0-alpha-3/release-notes.html> >> >> The aggregated release notes are here: >> http://people.apache.org/~brett/staged-maven-site/release-notes-all.html<http://people.apache.org/%7Ebrett/staged-maven-site/release-notes-all.html> >> >> Cheers, >> Brett >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@... >> For additional commands, e-mail: dev-help@... >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3On 13/11/2009, at 11:50 PM, Benjamin Bentmann wrote: > Brett Porter wrote: > >> I've staged a sample site here: http://people.apache.org/~brett/staged-maven-site/ > > +1, I like the proposed structure. > > Just one minor thing: I believe the JAR/PDF of the site should be listed separately as currently and not be part of the table listing the 2.2.1 downloads. The site is meant to cover various Maven versions so I consider the structure at > > http://people.apache.org/~brett/staged-maven-site/download.html > > irritating as it suggests the docs are meant specifically for 2.2.1. Done that, thanks. > >> Alpha 3 is on the download page only, and release notes are drafted: http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html > > Thanks, I happily grabbed that and copied it over to the trunk. > > Before we completely merge the branch to trunk, we should look into releasing the updated plexus-velocity component. There are already enough snapshot things involved in the site for my taste. Agreed. I'll start that process now and merge it once it's released. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3Can't we keep 2.0.10 only in archives ?
I don't think it is necessary to do some advertisement for it. Latest stable is 2.2.1 and latest Alpha/Beta is 3.0-alpha-3 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Mon, Nov 16, 2009 at 1:17 PM, Brett Porter <brett@...> wrote: > > On 13/11/2009, at 11:50 PM, Benjamin Bentmann wrote: > > > Brett Porter wrote: > > > >> I've staged a sample site here: > http://people.apache.org/~brett/staged-maven-site/ > > > > +1, I like the proposed structure. > > > > Just one minor thing: I believe the JAR/PDF of the site should be listed > separately as currently and not be part of the table listing the 2.2.1 > downloads. The site is meant to cover various Maven versions so I consider > the structure at > > > > http://people.apache.org/~brett/staged-maven-site/download.html > > > > irritating as it suggests the docs are meant specifically for 2.2.1. > > Done that, thanks. > > > > >> Alpha 3 is on the download page only, and release notes are drafted: > http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html > > > > Thanks, I happily grabbed that and copied it over to the trunk. > > > > Before we completely merge the branch to trunk, we should look into > releasing the updated plexus-velocity component. There are already enough > snapshot things involved in the site for my taste. > > Agreed. I'll start that process now and merge it once it's released. > > - Brett > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > > |
|
|
Re: Site Update for Maven 3.0-alpha-3On 16/11/2009, at 11:38 PM, Arnaud HERITIER wrote:
> Can't we keep 2.0.10 only in archives ? > I don't think it is necessary to do some advertisement for it. > Latest stable is 2.2.1 and latest Alpha/Beta is 3.0-alpha-3 There are apparently some who haven't upgraded to 2.2.x, either due to a build incompat. or being stuck on JDK 1.4. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Site Update for Maven 3.0-alpha-3Ok, I've merged this over. I haven't deployed the site - I assume Benjamin will be doing so shortly after adding the 3.0-alpha-4 release notes. The aggregated release notes for 3.0-alpha-3+ is there too.
Let me know whether there is anything else I can do to help. Cheers, Brett On 16/11/2009, at 11:17 PM, Brett Porter wrote: > > On 13/11/2009, at 11:50 PM, Benjamin Bentmann wrote: > >> Brett Porter wrote: >> >>> I've staged a sample site here: http://people.apache.org/~brett/staged-maven-site/ >> >> +1, I like the proposed structure. >> >> Just one minor thing: I believe the JAR/PDF of the site should be listed separately as currently and not be part of the table listing the 2.2.1 downloads. The site is meant to cover various Maven versions so I consider the structure at >> >> http://people.apache.org/~brett/staged-maven-site/download.html >> >> irritating as it suggests the docs are meant specifically for 2.2.1. > > Done that, thanks. > >> >>> Alpha 3 is on the download page only, and release notes are drafted: http://people.apache.org/~brett/staged-maven-site/docs/3.0-alpha-3/release-notes.html >> >> Thanks, I happily grabbed that and copied it over to the trunk. >> >> Before we completely merge the branch to trunk, we should look into releasing the updated plexus-velocity component. There are already enough snapshot things involved in the site for my taste. > > Agreed. I'll start that process now and merge it once it's released. > > - Brett > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
| Free embeddable forum powered by Nabble | Forum Help |