You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Rahul Akolkar <ra...@gmail.com> on 2008/05/04 06:11:27 UTC
[VOTE] Release commons-parent 10
This is a vote to release v10 of the commons-parent pom. This is one
more step towards an established m2 release process for all of
Commons.
Here is a summary of changes to the pom since v9, chronologically:
* Markmail archives links have been updated
* Staging repos for RCs with final version numbers are chosen such
that the stage plugin can be used
* Continuum notifier has been removed to prevent further "on error" spam
No changes to site.xml.
Here is a complete diff since v9 (actually v9 + license header put back):
http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=636552&r2=652870&diff_format=h
The version number in the pom will be updated automatically during the
release process.
[ ] +1
[ ] =0
[ ] -1
Vote is open for 72 hours. TIA.
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 10
Posted by Emmanuel Bourg <eb...@apache.org>.
+1
Emmanuel Bourg
Rahul Akolkar a écrit :
> This is a vote to release v10 of the commons-parent pom. This is one
> more step towards an established m2 release process for all of
> Commons.
>
> Here is a summary of changes to the pom since v9, chronologically:
>
> * Markmail archives links have been updated
> * Staging repos for RCs with final version numbers are chosen such
> that the stage plugin can be used
> * Continuum notifier has been removed to prevent further "on error" spam
>
> No changes to site.xml.
>
> Here is a complete diff since v9 (actually v9 + license header put back):
>
> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=636552&r2=652870&diff_format=h
>
> The version number in the pom will be updated automatically during the
> release process.
>
> [ ] +1
> [ ] =0
> [ ] -1
>
> Vote is open for 72 hours. TIA.
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 10
Posted by Niall Pemberton <ni...@gmail.com>.
+1
Niall
On Sun, May 4, 2008 at 5:11 AM, Rahul Akolkar <ra...@gmail.com> wrote:
> This is a vote to release v10 of the commons-parent pom. This is one
> more step towards an established m2 release process for all of
> Commons.
>
> Here is a summary of changes to the pom since v9, chronologically:
>
> * Markmail archives links have been updated
> * Staging repos for RCs with final version numbers are chosen such
> that the stage plugin can be used
> * Continuum notifier has been removed to prevent further "on error" spam
>
> No changes to site.xml.
>
> Here is a complete diff since v9 (actually v9 + license header put back):
>
> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=636552&r2=652870&diff_format=h
>
> The version number in the pom will be updated automatically during the
> release process.
>
> [ ] +1
> [ ] =0
> [ ] -1
>
> Vote is open for 72 hours. TIA.
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 10
Posted by Luc Maisonobe <Lu...@free.fr>.
Rahul Akolkar a écrit :
> This is a vote to release v10 of the commons-parent pom. This is one
> more step towards an established m2 release process for all of
> Commons.
>
> Here is a summary of changes to the pom since v9, chronologically:
>
> * Markmail archives links have been updated
> * Staging repos for RCs with final version numbers are chosen such
> that the stage plugin can be used
> * Continuum notifier has been removed to prevent further "on error" spam
>
> No changes to site.xml.
>
> Here is a complete diff since v9 (actually v9 + license header put back):
>
> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=636552&r2=652870&diff_format=h
>
> The version number in the pom will be updated automatically during the
> release process.
>
> [ ] +1
> [ ] =0
> [ ] -1
+1
Luc
>
> Vote is open for 72 hours. TIA.
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
[RESULT] [VOTE] Release commons-parent 10
Posted by Rahul Akolkar <ra...@gmail.com>.
Adding my own vote, this vote passes with 4 +1s from:
Emmanuel Bourg
Luc Maisonobe
Niall Pemberton
Rahul Akolkar
I'll cut the release shortly. I'll update the POMs once v10 has
sync'ed and post about the continuum notifications thereafter.
Thanks to those who had a look.
-Rahul
On 5/4/08, Rahul Akolkar <ra...@gmail.com> wrote:
> This is a vote to release v10 of the commons-parent pom. This is one
> more step towards an established m2 release process for all of
> Commons.
>
> Here is a summary of changes to the pom since v9, chronologically:
>
> * Markmail archives links have been updated
> * Staging repos for RCs with final version numbers are chosen such
> that the stage plugin can be used
> * Continuum notifier has been removed to prevent further "on error" spam
>
> No changes to site.xml.
>
> Here is a complete diff since v9 (actually v9 + license header put back):
>
> http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=636552&r2=652870&diff_format=h
>
> The version number in the pom will be updated automatically during the
> release process.
>
> [ ] +1
> [ ] =0
> [ ] -1
>
> Vote is open for 72 hours. TIA.
>
>
> -Rahul
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 10
Posted by Rahul Akolkar <ra...@gmail.com>.
On 5/5/08, Jörg Schaible <Jo...@elsag-solutions.com> wrote:
> Hi Rahul,
>
>
> Rahul Akolkar wrote:
> > This is a vote to release v10 of the commons-parent pom. This is one
> > more step towards an established m2 release process for all of
> > Commons.
> >
> > Here is a summary of changes to the pom since v9, chronologically:
> >
> > * Markmail archives links have been updated
> > * Staging repos for RCs with final version numbers are chosen such
> > that the stage plugin can be used
> > * Continuum notifier has been removed to prevent further "on
> > error" spam
>
>
> Hmmm. Although the failing continuum notifiers are a bit annoying, they are still useful to detect a problem. What about sending the notification to the issues list?
>
<snip/>
(thanks for taking a look -- I've read the rest of the thread, will reply here)
Sure, thats one possibility, but lets do that through the continuum
UI, which is a more lightweight process (each pom configuration change
requires a release, releases have overhead etc).
I tried to explain in a recent thread, in short:
* Currently all notifications are sent to dev@, which IMO isn't the best option
* It seems the continuum UI allows us to configure notifications with
a finer granularity ("on error" messages can be treated differently
than build successes or failures from a notification PoV)
* If you're subscribed to all Commons lists (such as dev, issues,
commits) you shouldn't notice any difference WRT success and failure
messages on a per commit or nightly basis when we're done (we can drop
the error notifications, mainly caused by CI problems so far,
configure them on a per project basis as deemed fit, or retain all of
them on issues@ -- this is TBD)
Roadmap is:
1) Release v10
2) Configure notifications via continuum UI
3) Iterate over (2) as needed (no more releases for that)
Please let us know if this addresses your question above.
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 10
Posted by sebb <se...@gmail.com>.
2008/5/5 Jörg Schaible <Jo...@elsag-solutions.com>:
> sebb wrote:
> > 2008/5/5 Jörg Schaible <Jo...@elsag-solutions.com>:
> >> Hi Rahul,
> >>
> >>
> >> Rahul Akolkar wrote:
> >> > This is a vote to release v10 of the commons-parent pom. This is
> >> one > more step towards an established m2 release process for all
> >> of > Commons. >
> >> > Here is a summary of changes to the pom since v9,
> >> chronologically: > > * Markmail archives links have been updated
> >> > * Staging repos for RCs with final version numbers are chosen
> >> such > that the stage plugin can be used
> >> > * Continuum notifier has been removed to prevent further "on >
> >> error" spam
> >>
> >> Hmmm. Although the failing continuum notifiers are a bit
> > annoying, they are still useful to detect a problem. What
> > about sending the notification to the issues list?
> >>
> >
> > Whichever list they are sent to will likely be flooded from
> > time to time.
>
> Only if the CI system has a problem in general.
>
>
> > How about picking one project - or adding a dummy project to Continuum
> > - and have just that send the notifications?
>
> Main reason is to get a notification when a commit causes for whatever reason a problem. That requires individual mails. Therefore I see no benefit in a dummy project.
>
You're right. I was thinking only of the SVN error messages.
Maybe Continuum should be cleverer about sending messages...
>
> - Jörg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [VOTE] Release commons-parent 10
Posted by Jörg Schaible <Jo...@Elsag-Solutions.com>.
sebb wrote:
> 2008/5/5 Jörg Schaible <Jo...@elsag-solutions.com>:
>> Hi Rahul,
>>
>>
>> Rahul Akolkar wrote:
>> > This is a vote to release v10 of the commons-parent pom. This is
>> one > more step towards an established m2 release process for all
>> of > Commons. >
>> > Here is a summary of changes to the pom since v9,
>> chronologically: > > * Markmail archives links have been updated
>> > * Staging repos for RCs with final version numbers are chosen
>> such > that the stage plugin can be used
>> > * Continuum notifier has been removed to prevent further "on >
>> error" spam
>>
>> Hmmm. Although the failing continuum notifiers are a bit
> annoying, they are still useful to detect a problem. What
> about sending the notification to the issues list?
>>
>
> Whichever list they are sent to will likely be flooded from
> time to time.
Only if the CI system has a problem in general.
> How about picking one project - or adding a dummy project to Continuum
> - and have just that send the notifications?
Main reason is to get a notification when a commit causes for whatever reason a problem. That requires individual mails. Therefore I see no benefit in a dummy project.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release commons-parent 10
Posted by sebb <se...@gmail.com>.
2008/5/5 Jörg Schaible <Jo...@elsag-solutions.com>:
> Hi Rahul,
>
>
> Rahul Akolkar wrote:
> > This is a vote to release v10 of the commons-parent pom. This is one
> > more step towards an established m2 release process for all of
> > Commons.
> >
> > Here is a summary of changes to the pom since v9, chronologically:
> >
> > * Markmail archives links have been updated
> > * Staging repos for RCs with final version numbers are chosen such
> > that the stage plugin can be used
> > * Continuum notifier has been removed to prevent further "on
> > error" spam
>
> Hmmm. Although the failing continuum notifiers are a bit annoying, they are still useful to detect a problem. What about sending the notification to the issues list?
>
Whichever list they are sent to will likely be flooded from time to time.
How about picking one project - or adding a dummy project to Continuum
- and have just that send the notifications?
> [snip]
>
> - Jörg
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [VOTE] Release commons-parent 10
Posted by Jörg Schaible <Jo...@Elsag-Solutions.com>.
Hi Rahul,
Rahul Akolkar wrote:
> This is a vote to release v10 of the commons-parent pom. This is one
> more step towards an established m2 release process for all of
> Commons.
>
> Here is a summary of changes to the pom since v9, chronologically:
>
> * Markmail archives links have been updated
> * Staging repos for RCs with final version numbers are chosen such
> that the stage plugin can be used
> * Continuum notifier has been removed to prevent further "on
> error" spam
Hmmm. Although the failing continuum notifiers are a bit annoying, they are still useful to detect a problem. What about sending the notification to the issues list?
[snip]
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org