25 Sep
2009
25 Sep
'09
2:33 p.m.
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.
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
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?
Thanks
-Vincent
25 Sep
25 Sep
2:39 p.m.
+1
On Fri, Sep 25, 2009 at 15:33, Vincent Massol <vincent(a)massol.net> 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.
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
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?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:40 p.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.
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)
- documentation
& user/dev experience from the pov presented at
http://markmail.org/thread/aljoc6h27bgwudbw .
These should go in both the trunk (2.1) and for 2.0.x
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?
very +1
Happy coding,
Anca
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:40 p.m.
Hi,
On Fri, Sep 25, 2009 at 2:33 PM, Vincent Massol <vincent(a)massol.net> 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.
Sounds good. We need to make sure all the new stuff we built in the past
month is at the best quality level we can achieve.
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
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.
Yep, releasing the 2.0.1 version in a couple weeks sounds good.
Guillaume
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
2:53 p.m.
+1
On Fri, Sep 25, 2009 at 14:33, Vincent Massol <vincent(a)massol.net> 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.
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
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?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
2:57 p.m.
+1,
JV.
On Fri, Sep 25, 2009 at 2:33 PM, Vincent Massol <vincent(a)massol.net> 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.
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
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?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4:36 p.m.
+1
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.
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
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?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
6:43 p.m.
On Fri, Sep 25, 2009 at 6:03 PM, Vincent Massol <vincent(a)massol.net> 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.
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
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?
+1
Thanks.
- Asiri
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
27 Sep
27 Sep
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/
9:30 a.m.
On Sep 27, 2009, at 5:57 AM, Sergiu Dumitriu wrote:
The choice of 2 branches precedes this proposal. In addition this
proposal to stabilize is not forever. It's limited in time.
We already have changes in trunk so it's going to be a bit difficult
maybe to remove the branch. If you have some idea to make it less
painful they are very welcome (even using git is an idea but someone
would need to setup a git svn mirror ad provide some explanations ;)).
Thanks
-Vincent
Vincent Massol wrote:
The point is to act as a team. We would all prefer to work on
innovation but:
1) it's not quite fair that some of us do while others are fixing bugs
2) we really have a huge backlogs of known bugs and small needed
improvements and we need a way to reduce them for 2.0.1
That said, this is only a proposal and everyone is free to work on
whatever he wants so yes I agree with your remark too. There's no hard
forbidding, it's just a recommendation that is there purely to try to
stabilize what we have, as a team.
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.
Whatever has to go in 2.0.1 is ok.
In this case I'd say it's ok since I think we'd want this in 2.0.1
since what we have now is a bit too basic.
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?
28 Sep
28 Sep
3:51 p.m.
Hi,
On Sun, Sep 27, 2009 at 9:30 AM, Vincent Massol <vincent(a)massol.net> wrote:
I'll send an email about XE 2.1 later this afternoon.
Guillaume
The choice of 2 branches precedes this proposal. In addition this
proposal to stabilize is not forever. It's limited in time.
We already have changes in trunk so it's going to be a bit difficult
maybe to remove the branch. If you have some idea to make it less
painful they are very welcome (even using git is an idea but someone
would need to setup a git svn mirror ad provide some explanations ;)).
Thanks
-Vincent
--
Guillaume Lerouge
Product Manager - XWiki
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
On Sep 27, 2009, at 5:57 AM, Sergiu Dumitriu wrote:
I agree with Vincent here:
- We've added a huge number of features in our last 4 releases so I don't
really think that putting new features on hold for one month means that we
would be blocking innovation on XWiki
- We've got plenty of bugs that make our new features less usable than
they should and fixing them matters a lot to get to a finished state (for
instance I was affected by
http://jira.xwiki.org/jira/browse/XSCOLIBRI-50this morning while
trying to set a colorTheme for a private wiki)
Vincent Massol wrote:
The point is to act as a team. We would all prefer to work on
innovation but:
1) it's not quite fair that some of us do while others are fixing bugs
2) we really have a huge backlogs of known bugs and small needed
improvements and we need a way to reduce them for 2.0.1
That said, this is only a proposal and everyone is free to work on
whatever he wants so yes I agree with your remark too. There's no hard
forbidding, it's just a recommendation that is there purely to try to
stabilize what we have, as a team.
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
The color theme creator can be viewed as an improvement to the ColorTheme
application more than a new feature per se. I understand Vincent's general
point as "increase the quality of the stuff that is already there" and I
think the improved ColorTheme space homepage fits in this category.
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.
Whatever has to go in 2.0.1 is ok.
In this case I'd say it's ok since I think we'd want this in 2.0.1
since what we have now is a bit too basic.
> 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?
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5467
days inactive
5470
days old
10 comments
9 participants
participants (9)
-
Anca Luca -
Asiri Rathnayake -
Ecaterina Valica -
Guillaume Lerouge -
Jean-Vincent Drean -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol