Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Carsten Ziegeler
Upayavira wrote: Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Joerg Heinicke
On 16.10.2005 16:53, Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Daniel Fagerstrom
Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. WDYT?

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Sylvain Wallez
Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. +1.

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Carsten Ziegeler
Sylvain Wallez wrote: +1. And as we decided to have fixed releases, what about planning 2.1.9 right now? Let's say that code freeze for 2.1.9 starts on 20th January (3rd friday) and release happens on 27th. Hmm, do we need fixed dates for a maintenance branch? I think we should just

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Jean-Baptiste Quenot
* Carsten Ziegeler: It seems that most major problems have been solved What do you mean with « major problems »? Which ones have been solved? Best regards, -- Jean-Baptiste Quenot Systèmes d'Information ANYWARE TECHNOLOGIES Tel : +33 (0)5 61 00 52 90 Fax : +33 (0)5 61 00 51 46

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Carsten Ziegeler
Jean-Baptiste Quenot wrote: * Carsten Ziegeler: It seems that most major problems have been solved What do you mean with « major problems »? Which ones have been solved? It's just a phrase - what I actually meant was that there are no blocking issues and we now know how to include

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Ralph Goers
Sylvain Wallez wrote: Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Ralph Goers
Carsten Ziegeler wrote: Sylvain Wallez wrote: +1. And as we decided to have fixed releases, what about planning 2.1.9 right now? Let's say that code freeze for 2.1.9 starts on 20th January (3rd friday) and release happens on 27th. Hmm, do we need fixed dates for a maintenance

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Peter Hunsberger
On 10/17/05, Ralph Goers [EMAIL PROTECTED] wrote: I think it is important to plan a date for 2.1.9 simply to give customers reassurance that we won't abandon 2.1 until after 2.2 is stable. We'll test 2.1.8 and if it works for us we'll eventually migrate to it. If it doesn't work having a

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Vadim Gritsenko
Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. WDYT?

Re: [QVote] Release plan for 2.1.8

2005-10-17 Thread Carsten Ziegeler
Vadim Gritsenko schrieb: Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on

[QVote] Release plan for 2.1.8

2005-10-16 Thread Carsten Ziegeler
It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. WDYT? Carsten -- Carsten Ziegeler

Re: [QVote] Release plan for 2.1.8

2005-10-16 Thread Ralph Goers
Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. WDYT?

Re: [QVote] Release plan for 2.1.8

2005-10-16 Thread Jorg Heymans
Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. +1 !

Re: [QVote] Release plan for 2.1.8

2005-10-16 Thread hepabolu
Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. WDYT?

Re: [QVote] Release plan for 2.1.8

2005-10-16 Thread Leszek Gawron
Carsten Ziegeler wrote: It seems that most major problems have been solved and we can release. To give everyone some more days time to finish/polish everything, I propose to start the code freeze on friday, 21st of October, and I will do the release one week later on 28th of October. WDYT?