RE: [Vote] Release plan for 2.1.9
On 21.03.2006 09:20, Carsten Ziegeler wrote: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) +1 Matthew
[Vote] Release plan for 2.1.9
Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Vote] Release plan for 2.1.9
Le 21 mars 06 à 09:20, Carsten Ziegeler a écrit : ...So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens).. +1 -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: [Vote] Release plan for 2.1.9
Bertrand Delacretaz said the following on 21-03-2006 09:46: Le 21 mars 06 à 09:20, Carsten Ziegeler a écrit : ...So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens).. +1 Bye, Helma
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: Please cast your votes +1 Thanks, Andrew. -- Andrew Savory, Managing Director, Luminas Limited Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 Web: http://www.luminas.co.uk/ Orixo alliance: http://www.orixo.com/
Re: [Vote] Release plan for 2.1.9
On Tue, 2006-03-21 at 09:20 +0100, Carsten Ziegeler wrote: Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes +1 -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote:
Although we already agreed informaly on the release plan, we should
do a formal vote.
As I won't be able to do the release on the 31st of March, we have to
delay it by one week (unless someone else volunteers to do it).
So the proposed plan to release 2.1.9 is:
- Start code freeze on the 31st of March
- Release on the 6th of April (if nothing bad happens)
+1 (but won't spend much time for tests)
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
RE: [Vote] Release plan for 2.1.9
So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) +1 Cheers, Alfred. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company.
Re: [Vote] Release plan for 2.1.9
On 21 Mar 2006, at 08:20, Carsten Ziegeler wrote: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) +1 please! Pier smime.p7s Description: S/MIME cryptographic signature
Re: [Vote] Release plan for 2.1.9
Il giorno 21/mar/06, alle ore 09:20, Carsten Ziegeler ha scritto: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes +1 Ugo -- Ugo Cei Blog: http://agylen.com/ Open Source Zone: http://oszone.org/ Evil or Not?: http://evilornot.info/ Company: http://www.sourcesense.com/
RE: [Vote] Release plan for 2.1.9
So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) +1 max
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes +1 Sylvain -- Sylvain Wallez http://bluxte.net Apache Software Foundation Member
Re: [Vote] Release plan for 2.1.9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 21 Mar 2006, Carsten Ziegeler wrote: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes +1 - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEH/cELNdJvZjjVZARAnpQAJ9JxRBkZt/lIzCSiYOGop+lwGe1aQCgiS5w tpUZ+ysKWniW5ExGmFKZJoY= =SWy2 -END PGP SIGNATURE-
Re: [Vote] Release plan for 2.1.9
On 3/21/06, Carsten Ziegeler [EMAIL PROTECTED] wrote: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes +1 -- Gianugo Rabellino Sourcesense, making sense of Open Source: http://www.sourcesense.com Orixo, the XML business alliance: http://www.orixo.com (blogging at http://www.rabellino.it/blog/)
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler skrev: Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes Carsten +1 /Daniel
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes Carsten +1 Best Regards, Antonio Gallardo
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) +1 Vadim
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes +1 Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) +1
Re: [Vote] Release plan for 2.1.9
* Carsten Ziegeler: Although we already agreed informaly on the release plan, we should do a formal vote. +0 I don't see the point of voting for such an obvious decision. Is there a rule requiring new releases to be first approved by a vote? I mean new releases should be automatic. IMHO it's not very useful to cast any vote for a maintenance release in a stable branch. -- Jean-Baptiste Quenot http://caraldi.com/jbq/
Re: [Vote] Release plan for 2.1.9
On 21 Mar 2006, at 17:42, Jean-Baptiste Quenot wrote: * Carsten Ziegeler: Although we already agreed informaly on the release plan, we should do a formal vote. +0 I don't see the point of voting for such an obvious decision. Is there a rule requiring new releases to be first approved by a vote? I mean new releases should be automatic. IMHO it's not very useful to cast any vote for a maintenance release in a stable branch. http://cocoon.apache.org/devinfo/releasing.html Pier smime.p7s Description: S/MIME cryptographic signature
Re: [Vote] Release plan for 2.1.9
Jean-Baptiste Quenot wrote:
* Carsten Ziegeler:
Although we already agreed informaly on the release plan, we
should do a formal vote.
+0 I don't see the point of voting for such an obvious decision.
Is there a rule requiring new releases to be first approved by a
vote? I mean new releases should be automatic. IMHO it's not
very useful to cast any vote for a maintenance release in a stable
branch.
The PMC has to vote about the actual software artifact but there is no rule that
we have to vote that we will do a release. After the many attempts to do a 2.1.9
release in the past, I think that Carsten wanted to be sure that this time
everybody is on board.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [Vote] Release plan for 2.1.9
* Pier Fumagalli: On 21 Mar 2006, at 17:42, Jean-Baptiste Quenot wrote: * Carsten Ziegeler: Although we already agreed informaly on the release plan, we should do a formal vote. +0 I don't see the point of voting for such an obvious decision. Is there a rule requiring new releases to be first approved by a vote? I mean new releases should be automatic. IMHO it's not very useful to cast any vote for a maintenance release in a stable branch. http://cocoon.apache.org/devinfo/releasing.html This document states that we have to vote once the new version is tagged, to be sure that there is no showstopper. So we are not applying the rule, right? -- Jean-Baptiste Quenot http://caraldi.com/jbq/
Re: [Vote] Release plan for 2.1.9
* Reinhard Poetz: The PMC has to vote about the actual software artifact but there is no rule that we have to vote that we will do a release. After the many attempts to do a 2.1.9 release in the past, I think that Carsten wanted to be sure that this time everybody is on board. Just to be clear: I think Carsten is doing a valuable work as release manager. It's just that I feel this vote useless, I mean just go ahead. We might vote once the release is tagged. -- Jean-Baptiste Quenot http://caraldi.com/jbq/
Re: [Vote] Release plan for 2.1.9
Jean-Baptiste Quenot wrote:
* Reinhard Poetz:
The PMC has to vote about the actual software artifact but there
is no rule that we have to vote that we will do a release. After
the many attempts to do a 2.1.9 release in the past, I think
that Carsten wanted to be sure that this time everybody is on
board.
Just to be clear: I think Carsten is doing a valuable work as
release manager. It's just that I feel this vote useless, I mean
just go ahead. We might vote once the release is tagged.
Then the PMC *has to* vote.
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Voting on releases? (was: [Vote] Release plan for 2.1.9)
Le 21 mars 06 à 18:42, Jean-Baptiste Quenot a écrit : ...Is there a rule requiring new releases to be first approved by a vote?... Maybe not, but we've been doing it this way for about 25 years and it works ;-) Seriously, making sure we agree on release plans (code freeze dates etc.) is a Good Thing - I've seen several projects arguing or disagreeing on releases, so it's certainly good to be a bit careful and to make sure everyone is on the same page. It doesn't cost much and there are at least social benefits. So, +1 for voting on release plans ;-) -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: [Vote] Release plan for 2.1.9
On 21.03.2006 09:20, Carsten Ziegeler wrote: So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) +1 Jörg
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes Carsten +1. Hopefully nothing bad will happen. Ralph
Re: [Vote] Release plan for 2.1.9
Carsten Ziegeler wrote: Although we already agreed informaly on the release plan, we should do a formal vote. As I won't be able to do the release on the 31st of March, we have to delay it by one week (unless someone else volunteers to do it). So the proposed plan to release 2.1.9 is: - Start code freeze on the 31st of March - Release on the 6th of April (if nothing bad happens) Please cast your votes +1 -David
Re: Voting on releases? (was: [Vote] Release plan for 2.1.9)
Bertrand Delacretaz wrote: Jean-Baptiste Quenot a ?crit : ...Is there a rule requiring new releases to be first approved by a vote?... Maybe not, but we've been doing it this way for about 25 years and it works ;-) I think that there is a requirement for PMCs to vote on all releases. Cocoon doesn't yet have its project guidelines, but other PMC guidelines are definite. Most say majority approval is required. Seriously, making sure we agree on release plans (code freeze dates etc.) is a Good Thing - I've seen several projects arguing or disagreeing on releases, so it's certainly good to be a bit careful and to make sure everyone is on the same page. It doesn't cost much and there are at least social benefits. So, +1 for voting on release plans ;-) +1, i agree that we should vote on the release plan as well. -David
