You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2003/09/24 11:05:51 UTC
[Vote] Releasing next version
Hi,
it seems that we had some minor problems with the 2.1.1 release
as stated recently in this list. That's why we didn't officially
announce the release.
AFAIK, the problems are all solved in the current cvs, so I suggest
that we make quickly a 2.1.2 release and announce officially.
With respect to the recent thread about release management, I propse
a release date of October, 1th which would include a freeze of the
cvs starting on monday, 29th.
If we don't want to make a 2.1.2 release yet, we have to announce
2.1.1 and provide *somehow* a patch. I think releasing 2.1.2 is
easier.
So please cast your vote for either:
a) Make a 2.1.2 release on October, 1th
OR
b) Provide a patch for 2.1.1
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
http://radio.weblogs.com/0107211/
Re: [Vote] Releasing next version
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Carsten Ziegeler wrote:
>So please cast your vote for either:
>
>a) Make a 2.1.2 release on October, 1th
>
+1.
This will allow my Woody/Flowscript presentation at the Get Together to
talk about released features ;-)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
Re: [Vote] Releasing next version
Posted by Giacomo Pati <gi...@apache.org>.
On Wed, 24 Sep 2003, Carsten Ziegeler wrote:
> Hi,
>
> it seems that we had some minor problems with the 2.1.1 release
> as stated recently in this list. That's why we didn't officially
> announce the release.
> AFAIK, the problems are all solved in the current cvs, so I suggest
> that we make quickly a 2.1.2 release and announce officially.
>
> With respect to the recent thread about release management, I propse
> a release date of October, 1th which would include a freeze of the
> cvs starting on monday, 29th.
>
> If we don't want to make a 2.1.2 release yet, we have to announce
> 2.1.1 and provide *somehow* a patch. I think releasing 2.1.2 is
> easier.
>
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
> OR
>
> b) Provide a patch for 2.1.1
Do we have to place a note why there wasn't an announcement for the
2.1.1 (people might think we'e skipped a number)?
--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
Re: [Vote] Releasing next version
Posted by Christian Haul <ha...@informatik.tu-darmstadt.de>.
Carsten Ziegeler wrote:
>
> a) Make a 2.1.2 release on October, 1th
release often, release early: +1
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
Re: [Vote] Releasing next version
Posted by Tony Collen <co...@umn.edu>.
Carsten Ziegeler wrote:
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
Tony
Re: [Vote] Releasing next version
Posted by Guido Casper <gc...@s-und-n.de>.
Carsten Ziegeler <cz...@s-und-n.de> wrote:
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
Guido
Re: [Vote] Releasing next version
Posted by Geoff Howard <co...@leverageweb.com>.
Sylvain Wallez wrote:
> Geoff Howard wrote:
>
>> Carsten Ziegeler wrote:
>>> b) Provide a patch for 2.1.1
>>
>>
>>
>> I thought this was just replacing the jxforms block jar file? Did I
>> get this wrong?
>
> Slightly ;-)
>
> JXForms is already patched in the 2.1.1, but a bug was introduced in
> Rhino-with-continuations.
Aha - that rings a bell. Ok, same question though: isn't this just
replacing the rhino-with-continuations jar?
Geoff
Re: [Vote] Releasing next version
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Geoff Howard wrote:
> Carsten Ziegeler wrote:
>
>>
>> a) Make a 2.1.2 release on October, 1th
>
>
> +1
>
>> b) Provide a patch for 2.1.1
>
>
> I thought this was just replacing the jxforms block jar file? Did I
> get this wrong?
Slightly ;-)
JXForms is already patched in the 2.1.1, but a bug was introduced in
Rhino-with-continuations.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
Re: [Vote] Releasing next version
Posted by Geoff Howard <co...@leverageweb.com>.
Carsten Ziegeler wrote:
>
> a) Make a 2.1.2 release on October, 1th
+1
> b) Provide a patch for 2.1.1
I thought this was just replacing the jxforms block jar file? Did I get
this wrong?
Geoff
Re: [Vote] Releasing next version
Posted by Vadim Gritsenko <va...@verizon.net>.
Carsten Ziegeler wrote:
>a) Make a 2.1.2 release on October, 1th
>
>
Go ahead! %-)
Vadim
Re: [Vote] Releasing next version
Posted by Ugo Cei <u....@cbim.it>.
Carsten Ziegeler wrote:
> a) Make a 2.1.2 release on October, 1th
+1
Re: [Vote] Releasing next version
Posted by Berin Loritsch <bl...@apache.org>.
Carsten Ziegeler wrote:
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
>
> OR
>
> b) Provide a patch for 2.1.1
-1 They can be messy, and if it isn't installed properly can
cause just as many problems as they solve.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
Re: [Vote] Releasing next version
Posted by Joerg Heinicke <jh...@virbus.de>.
Carsten Ziegeler wrote:
> Hi,
>
> it seems that we had some minor problems with the 2.1.1 release
> as stated recently in this list. That's why we didn't officially
> announce the release.
> AFAIK, the problems are all solved in the current cvs, so I suggest
> that we make quickly a 2.1.2 release and announce officially.
>
> With respect to the recent thread about release management, I propse
> a release date of October, 1th which would include a freeze of the
> cvs starting on monday, 29th.
>
> If we don't want to make a 2.1.2 release yet, we have to announce
> 2.1.1 and provide *somehow* a patch. I think releasing 2.1.2 is
> easier.
>
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
> OR
>
> b) Provide a patch for 2.1.1
+0
Joerg
--
System Development
VIRBUS AG
Fon +49(0)341-979-7419
Fax +49(0)341-979-7409
joerg.heinicke@virbus.de
www.virbus.de
Re: [Vote] Releasing next version
Posted by Andrew Savory <an...@luminas.co.uk>.
On Wed, 24 Sep 2003, Carsten Ziegeler wrote:
> a) Make a 2.1.2 release on October, 1th
+1
Andrew.
--
Andrew Savory Email: andrew@luminas.co.uk
Managing Director Tel: +44 (0)870 741 6658
Luminas Internet Applications Fax: +44 (0)700 598 1135
Orixo alliance: http://www.orixo.com/ Web: www.luminas.co.uk
Re: Freeze policy? (was Re: [Vote] Releasing next version)
Posted by Giacomo Pati <gi...@apache.org>.
On Wed, 24 Sep 2003, Jeff Turner wrote:
> On Wed, Sep 24, 2003 at 10:16:05AM -0400, Berin Loritsch wrote:
> > Steven Noels wrote:
> >
> > >Carsten Ziegeler wrote:
> > >
> > >>With respect to the recent thread about release management, I propse
> > >>a release date of October, 1th which would include a freeze of the
> > >>cvs starting on monday, 29th.
> > >
> > >
> > >+1 - let's do a serious freeze this time.
> > >
> > >>a) Make a 2.1.2 release on October, 1th
> > >
> > >
> > >+1
>
> +1
>
> > Better yet:
> >
> > Since the process of code freezing is not encouraged, use labels. Start
> > with the release candidate label first (i.e. marking it now before it
> > changes).
> > So that would be something like 2_1_2_RC, and if all is good, you can
> > relabel
> > that exact release 2_1_2_FINAL.
>
> We tried this in Forrest and found it didn't work very well. Unless a
> freeze is declared, people will start committing stuff for the next
> version. Any last-minute bugfixes for 2.1.2 will be mixed with changes
> for 2.2, and there's no bugfix-only version of the file to update the tag
> to. The status.xml file is guaranteed to exhibit this problem. The
> Forrest 0.5 status.xml has some bogus 0.6 entries as testament to this ;P
IIHO the right way is using a branch not just tags. During the release
period backport bug fixes to the other branch.
--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
Re: Freeze policy? (was Re: [Vote] Releasing next version)
Posted by Jeff Turner <je...@apache.org>.
On Wed, Sep 24, 2003 at 10:16:05AM -0400, Berin Loritsch wrote:
> Steven Noels wrote:
>
> >Carsten Ziegeler wrote:
> >
> >>With respect to the recent thread about release management, I propse
> >>a release date of October, 1th which would include a freeze of the
> >>cvs starting on monday, 29th.
> >
> >
> >+1 - let's do a serious freeze this time.
> >
> >>a) Make a 2.1.2 release on October, 1th
> >
> >
> >+1
+1
> Better yet:
>
> Since the process of code freezing is not encouraged, use labels. Start
> with the release candidate label first (i.e. marking it now before it
> changes).
> So that would be something like 2_1_2_RC, and if all is good, you can
> relabel
> that exact release 2_1_2_FINAL.
We tried this in Forrest and found it didn't work very well. Unless a
freeze is declared, people will start committing stuff for the next
version. Any last-minute bugfixes for 2.1.2 will be mixed with changes
for 2.2, and there's no bugfix-only version of the file to update the tag
to. The status.xml file is guaranteed to exhibit this problem. The
Forrest 0.5 status.xml has some bogus 0.6 entries as testament to this ;P
--Jeff
...
RE: Freeze policy? (was Re: [Vote] Releasing next version)
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Bertrand Delacretaz wrote:
>
> Le Mercredi, 24 sep 2003, à 17:32 Europe/Zurich, Vadim Gritsenko a
> écrit :
> > ...Personally, I prefer code freeze policy. Moving tags on individual
> > files make things messy, and global freeze gives everybody an
> > opportunity to stop for a second, take a look at what we are going to
> > release, and may be fix a bug or too...
>
> I'm with Vadim - technically I like Berin's proposal with CVS tags a
> lot, but from the team's perspective it might be better to actually
> freeze development for a while.
Yep, I absolutely agree. If we follow your proposal, Berin, than the
release tends to be a "one man show" and noone else than the release
manager will care about the release (ok, noone is too pesimistic, I know).
Look at the release problems over at Avalon where noone than the release
manager really cares about the release which makes releasing something
really painfull.
>
> And if "code freeze" = "frantically test everything before release",
> all the better.
>
Yes, this is my hope as well. A release must be a team effort.
Carsten
Re: Freeze policy? (was Re: [Vote] Releasing next version)
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Le Mercredi, 24 sep 2003, à 17:32 Europe/Zurich, Vadim Gritsenko a
écrit :
> ...Personally, I prefer code freeze policy. Moving tags on individual
> files make things messy, and global freeze gives everybody an
> opportunity to stop for a second, take a look at what we are going to
> release, and may be fix a bug or too...
I'm with Vadim - technically I like Berin's proposal with CVS tags a
lot, but from the team's perspective it might be better to actually
freeze development for a while.
And if "code freeze" = "frantically test everything before release",
all the better.
-Bertrand
Re: Freeze policy? (was Re: [Vote] Releasing next version)
Posted by Vadim Gritsenko <va...@verizon.net>.
Berin Loritsch wrote:
> Steven Noels wrote:
>
>> Carsten Ziegeler wrote:
>>
>>> With respect to the recent thread about release management, I propse
>>> a release date of October, 1th which would include a freeze of the
>>> cvs starting on monday, 29th.
>>
>>
>>
>> +1 - let's do a serious freeze this time.
>>
>>> a) Make a 2.1.2 release on October, 1th
>>
>>
>>
>> +1
>
>
> Better yet:
>
> Since the process of code freezing is not encouraged, use labels. Start
> with the release candidate label first (i.e. marking it now before it
> changes).
> So that would be something like 2_1_2_RC, and if all is good, you can
> relabel
> that exact release 2_1_2_FINAL.
>
> To ensure you have the proper set of sources, you can perform the
> following
> command:
>
> cvs -z3 up -r 2_1_2_RC
>
> After the release is made, you can reset the sticky flag for the
> release with
>
> cvs -z3 up -a
>
> This process only freezes CVS for the release manager ONLY, allowing
> work to
> move forward for everyone else. If there is a new version of a class
> or file
> that should be incorporated then you can move the RC label to the proper
> version.
>
> Does that make sense? It is easier than to enforce a code freeze for
> all the
> committers we have here.
Personally, I prefer code freeze policy. Moving tags on individual files
make things messy, and global freeze gives everybody an opportunity to
stop for a second, take a look at what we are going to release, and may
be fix a bug or too.
Vadim
Freeze policy? (was Re: [Vote] Releasing next version)
Posted by Berin Loritsch <bl...@apache.org>.
Steven Noels wrote:
> Carsten Ziegeler wrote:
>
>> With respect to the recent thread about release management, I propse
>> a release date of October, 1th which would include a freeze of the
>> cvs starting on monday, 29th.
>
>
> +1 - let's do a serious freeze this time.
>
>> a) Make a 2.1.2 release on October, 1th
>
>
> +1
Better yet:
Since the process of code freezing is not encouraged, use labels. Start
with the release candidate label first (i.e. marking it now before it changes).
So that would be something like 2_1_2_RC, and if all is good, you can relabel
that exact release 2_1_2_FINAL.
To ensure you have the proper set of sources, you can perform the following
command:
cvs -z3 up -r 2_1_2_RC
After the release is made, you can reset the sticky flag for the release with
cvs -z3 up -a
This process only freezes CVS for the release manager ONLY, allowing work to
move forward for everyone else. If there is a new version of a class or file
that should be incorporated then you can move the RC label to the proper
version.
Does that make sense? It is easier than to enforce a code freeze for all the
committers we have here.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
Re: [Vote] Releasing next version
Posted by Steven Noels <st...@outerthought.org>.
Carsten Ziegeler wrote:
> With respect to the recent thread about release management, I propse
> a release date of October, 1th which would include a freeze of the
> cvs starting on monday, 29th.
+1 - let's do a serious freeze this time.
> a) Make a 2.1.2 release on October, 1th
+1
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: [Vote] Releasing next version
Posted by Upayavira <uv...@upaya.co.uk>.
Carsten Ziegeler wrote:
>Hi,
>
>it seems that we had some minor problems with the 2.1.1 release
>as stated recently in this list. That's why we didn't officially
>announce the release.
>AFAIK, the problems are all solved in the current cvs, so I suggest
>that we make quickly a 2.1.2 release and announce officially.
>
>With respect to the recent thread about release management, I propse
>a release date of October, 1th which would include a freeze of the
>cvs starting on monday, 29th.
>
>If we don't want to make a 2.1.2 release yet, we have to announce
>2.1.1 and provide *somehow* a patch. I think releasing 2.1.2 is
>easier.
>
>So please cast your vote for either:
>
>a) Make a 2.1.2 release on October, 1th
>
>OR
>
>b) Provide a patch for 2.1.1
>
>
+1 for a)
This will also please the Forrest people, as there was a bug in the CLI
crawler that caused it to miss pages which has now been fixed.
Releasing 2.1.2 soon would enable Forrest to do a 0.5.1 release with a
released Cocoon.
Regards, Upayavira
Re: [Vote] Releasing next version
Posted by Marc Portier <mp...@outerthought.org>.
Carsten Ziegeler wrote:
>
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
>
+1
-marc=
(who is experiencing that full time giving courses is to your
email-response-times like using a 1200 baud modem again ;-))
--
Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0116284/
mpo@outerthought.org mpo@apache.org
Re: [Vote] Releasing next version
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Carsten Ziegeler dijo:
> a) Make a 2.1.2 release on October, 1th
+1
Antonio Gallardo
Re: [Vote] Releasing next version
Posted by Bruno Dumon <br...@outerthought.org>.
On Wed, 2003-09-24 at 11:05, Carsten Ziegeler wrote:
>
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
>
+1
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org bruno@apache.org
Re: [Vote] Releasing next version
Posted by Stefano Mazzocchi <st...@apache.org>.
On Wednesday, Sep 24, 2003, at 11:05 Europe/Rome, Carsten Ziegeler
wrote:
> Hi,
>
> it seems that we had some minor problems with the 2.1.1 release
> as stated recently in this list. That's why we didn't officially
> announce the release.
> AFAIK, the problems are all solved in the current cvs, so I suggest
> that we make quickly a 2.1.2 release and announce officially.
>
> With respect to the recent thread about release management, I propse
> a release date of October, 1th which would include a freeze of the
> cvs starting on monday, 29th.
>
> If we don't want to make a 2.1.2 release yet, we have to announce
> 2.1.1 and provide *somehow* a patch. I think releasing 2.1.2 is
> easier.
>
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
--
Stefano.
RE: [Vote] Releasing next version
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Carsten Ziegeler wrote:
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
>
> OR
>
> b) Provide a patch for 2.1.1
>
+1 for a)
Carsten
RE: [Vote] Releasing next version
Posted by Reinhard Poetz <re...@apache.org>.
From: Carsten Ziegeler
> Hi,
>
> it seems that we had some minor problems with the 2.1.1
> release as stated recently in this list. That's why we didn't
> officially announce the release. AFAIK, the problems are all
> solved in the current cvs, so I suggest that we make quickly
> a 2.1.2 release and announce officially.
>
> With respect to the recent thread about release management, I
> propse a release date of October, 1th which would include a
> freeze of the cvs starting on monday, 29th.
>
> If we don't want to make a 2.1.2 release yet, we have to
> announce 2.1.1 and provide *somehow* a patch. I think
> releasing 2.1.2 is easier.
>
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
>
> OR
>
> b) Provide a patch for 2.1.1
+0
Reinhard
Sun classes (was Re: [Vote] Releasing next version)
Posted by Ugo Cei <u....@cbim.it>.
Conny Pemfors wrote:
> anybody who knows anything about com.sun.xml.tree.*; classes and in what jar
> file it exists in.
You question is not appropriate for this list, you should ask on the
users list (users@cocoon.apache.org). And please use a meaningful
subject line, what do have Sun classes to do with releasing the next
version?
Anyway, I don't know where those classes are, but I know that you should
never use classes in the com.sun.* packages. Those are undocumented
classes whose interface and implementation Sun reserves the right to
change at any time without warning. If you want to process XML, take a
look at the SAX and DOM APIs instead.
Ugo
--
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: u.cei@cbim.it
com.sun.xml (was: Re: [Vote] Releasing next version)
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Conny Pemfors wrote:
>anybody who knows anything about com.sun.xml.tree.*; classes and in what jar
>file it exists in.
>
>
Would you be kind enough to use a descriptive subject in your posts and
avoid replying a thread with unrelated questions ?
Now about com.sun.xml : this sould come from the old Sun XML parser that
later went to Apache as Crimson and has been superceded months ago by
Xerces 2.
Why do you need these, and why do you ask this question on the
cocoon-dev list ?
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
Sun classes (was Re: [Vote] Releasing next version)
Posted by Ugo Cei <u....@cbim.it>.
Conny Pemfors wrote:
> anybody who knows anything about com.sun.xml.tree.*; classes and in what jar
> file it exists in.
You question is not appropriate for this list, you should ask on the
users list (users@cocoon.apache.org). And please use a meaningful
subject line, what do have Sun classes to do with releasing the next
version?
Anyway, I don't know where those classes are, but I know that you should
never use classes in the com.sun.* packages. Those are undocumented
classes whose interface and implementation Sun reserves the right to
change at any time without warning. If you want to process XML, take a
look at the SAX and DOM APIs instead.
Ugo
--
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: u.cei@cbim.it
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [Vote] Releasing next version
Posted by Conny Pemfors <co...@uarda.lu.se>.
anybody who knows anything about com.sun.xml.tree.*; classes and in what jar
file it exists in.
----- Original Message -----
From: "Jeremy Quinn" <je...@media.demon.co.uk>
To: <de...@cocoon.apache.org>
Sent: Wednesday, September 24, 2003 12:28 PM
Subject: Re: [Vote] Releasing next version
>
> On Wednesday, September 24, 2003, at 10:05 AM, Carsten Ziegeler wrote:
>
> > a) Make a 2.1.2 release on October, 1th
>
> +1
>
> regards Jeremy
>
Re: [Vote] Releasing next version
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Wednesday, September 24, 2003, at 10:05 AM, Carsten Ziegeler wrote:
> a) Make a 2.1.2 release on October, 1th
+1
regards Jeremy
RE: [Vote] Releasing next version
Posted by Reinhard Pötz <re...@at.efp.cc>.
From: Carsten Ziegeler
> Hi,
>
> it seems that we had some minor problems with the 2.1.1
> release as stated recently in this list. That's why we didn't
> officially announce the release. AFAIK, the problems are all
> solved in the current cvs, so I suggest that we make quickly
> a 2.1.2 release and announce officially.
>
> With respect to the recent thread about release management, I
> propse a release date of October, 1th which would include a
> freeze of the cvs starting on monday, 29th.
>
> If we don't want to make a 2.1.2 release yet, we have to
> announce 2.1.1 and provide *somehow* a patch. I think
> releasing 2.1.2 is easier.
>
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+1
>
> OR
>
> b) Provide a patch for 2.1.1
+0
Reuinhard
Re: [Vote] Releasing next version
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
> ...With respect to the recent thread about release management, I propse
> a release date of October, 1th which would include a freeze of the
> cvs starting on monday, 29th...
+1 for the code freeze too
> So please cast your vote for either:
>
> a) Make a 2.1.2 release on October, 1th
+ 1
-Bertrand