27 Sep
2009
27 Sep
'09
5:57 a.m.
Vincent Massol wrote:
Hi devs,
I'd like to propose a stabilisation operation starting now and for 1
month (ie from now to the 1st of November)
The idea would be that **no new feature** is allowed to be committed
in SVN.
I don't quite agree with this. Yes, we should concentrate on stabilizing
existing code, but let's not block innovation.
Also, is a new feature that participates to the stabilization allowed or
not? Like, the create color theme wizard from the incubator is a new
feature, compared to the current trunk, but it is a key element of the
Colibri skin.
We have several domains to stabilize quickly after the
2.0 release:
- Colibri skin
- WYSIWYG editor
- Rendering
- XAR 2.0
- conversion to 2.0 syntax.
- internationalization texts
- Various (office importer page shouldn't be displayed when the office
server is not running, wiki macro textarea should be larger, etc)
These should go in both the trunk (2.1) and for 2.0.x
If there would be no new features, why have two branches?
I also propose to release a 2.0.1 in 2 weeks time
(i.e. for the 12th
of October) and to continue 2.0.x release every 2 weeks till we reach
that month's end.
WDYT?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/