On 02 Jan 2003 11:12:06 +0100, Olivier Chapuis wrote: > > The problem is that since 2003-01-01 fvwm/fvwm is feature freezed! > Yes, we do not get a warning message from Dominik ...
I noticed you worked very hard to fulfil this date. I would not make dates holy, fvwm should be ready for the freeze first. If we cut it on some date, it may be a set of random features not working well together. Additionally, I see no problems if someone has plans (and I wrote that I have my todo list, just didn't have a time to post it on December) and asks for some additional time. Since we did not really discuss the freeze date. I suggest to do it now. Let it be January, 15 for the core? At least we have a time to think what is missing. > Dominik, are you still our maintainer for 2.5.x/2.6.x ? I strongly > hope this. Note that we should fix a date for module feature freeze > and also a date for string freeze (for translation; this involves > fvwmrc discussion). I hope too. There is also perllib, that I will decide when will be its freeze date, I don't think it will be before March/April. It should be finalized as API for 2.6.x and future versions and it is not complete yet. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
