[xwiki-devs] [VOTE] Release XE/XEM 2.3 final
Hi devs, Since we've been stabilizing the 2.3 branch for a week [1] and that tests are ok (Caleb is looking at the last failing test) I think now would be a good time to release XE/XEM 2.3 final instead of RC2, I suggest to do the release tomorrow. Please shout if you need more time to commit things before 2.3 final. Here's my +1. [1] http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr... Thanks, JV.
On Apr 22, 2010, at 11:33 AM, Jean-Vincent Drean wrote:
Hi devs,
Since we've been stabilizing the 2.3 branch for a week [1] and that tests are ok (Caleb is looking at the last failing test) I think now would be a good time to release XE/XEM 2.3 final instead of RC2, I suggest to do the release tomorrow. Please shout if you need more time to commit things before 2.3 final.
Here's my +1.
+1 we shouldn't delay more IMO since we're already a bit late compared to the roadmap and we also have 3 branches to support ATM which is harder than it could be ;) If you agree with the vote please make sure that you finish everything you have to do for 2.3 before tonight EOD so that Jean-Vincent could release tomorrow morning. Anyone knows of a blocker bug that should absolutely be in XE 2.3 and that we have forgotten ? Thanks -Vincent
[1] http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr...
Thanks, JV.
Vincent Massol wrote:
On Apr 22, 2010, at 11:33 AM, Jean-Vincent Drean wrote:
Hi devs,
Since we've been stabilizing the 2.3 branch for a week [1] and that tests are ok (Caleb is looking at the last failing test) Changed assert to waitFor, now working locally.
I think now would be a good time to release XE/XEM 2.3 final instead of RC2, I suggest to do the release tomorrow. Please shout if you need more time to commit things before 2.3 final.
Here's my +1.
+1 we shouldn't delay more IMO since we're already a bit late compared to the roadmap and we also have 3 branches to support ATM which is harder than it could be ;) I like the idea of supporting more than 2 branches. Of course this isn't the place to discuss that.
+1 Caleb
If you agree with the vote please make sure that you finish everything you have to do for 2.3 before tonight EOD so that Jean-Vincent could release tomorrow morning.
Anyone knows of a blocker bug that should absolutely be in XE 2.3 and that we have forgotten ?
Thanks -Vincent
[1] http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr...
Thanks, JV.
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+0 for the release On Thu, Apr 22, 2010 at 12:06, Caleb James DeLisle <[email protected]
wrote:
+1 we shouldn't delay more IMO since we're already a bit late compared to the roadmap and we also have 3 branches to support ATM which is harder than it could be ;) I like the idea of supporting more than 2 branches. Of course this isn't the place to discuss that.
+1 for more branches :) Denis -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
On Apr 22, 2010, at 5:43 PM, Denis Gervalle wrote:
+0 for the release
On Thu, Apr 22, 2010 at 12:06, Caleb James DeLisle <[email protected]
wrote:
+1 we shouldn't delay more IMO since we're already a bit late compared to the roadmap and we also have 3 branches to support ATM which is harder than it could be ;) I like the idea of supporting more than 2 branches. Of course this isn't the place to discuss that.
+1 for more branches :)
You do realize that +1 means you're going to have to do the work of maintaining them yourself, right (maybe with Caleb since he also wants to do that + anyone who want to do it) ? :) Maintaining = * merge changes to them * test them * release them I'm certainly -1 to force any dev to do that, we already have way too much work and too little manpower. It's already taxing to support 2 branches. However we don't have any rule for preventing anyone to maintain branches though so there's nothing to change IMO. You can already maintain as many as you want. Which branches would you like to commit to support yourself? Thanks -Vincent
On Thu, Apr 22, 2010 at 17:53, Vincent Massol <[email protected]> wrote:
On Apr 22, 2010, at 5:43 PM, Denis Gervalle wrote:
+0 for the release
On Thu, Apr 22, 2010 at 12:06, Caleb James DeLisle < [email protected]
wrote:
+1 we shouldn't delay more IMO since we're already a bit late compared to the roadmap and we also have 3 branches to support ATM which is harder than it could be ;) I like the idea of supporting more than 2 branches. Of course this isn't the place to discuss that.
+1 for more branches :)
You do realize that +1 means you're going to have to do the work of maintaining them yourself, right (maybe with Caleb since he also wants to do that + anyone who want to do it) ? :)
Hey, don't go too fast, +1 means "I agree and I'll help as I can", and not more ! ;) Maintaining =
* merge changes to them
I already do so for some major fixes on version we have in production.
* test them
I even go to production, this is real life test, no ?
* release them
This is the part I am not aware of, and that I really need to learn more...
I'm certainly -1 to force any dev to do that, we already have way too much work and too little manpower. It's already taxing to support 2 branches.
However we don't have any rule for preventing anyone to maintain branches though so there's nothing to change IMO. You can already maintain as many as you want.
I will think about that, and Caleb or anyone helps is welcomed
Which branches would you like to commit to support yourself?
2.2 sound great for now, but let me discover the release process first ! I really like the idea of the LTS support of Ubuntu. On a short time, since 5 years is long, but supporting a release for longer than 3 months would be surely useful and appreciated by users So, let me think about this... and helps is welcomed ! Denis -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
Jean-Vincent Drean wrote:
Hi devs,
Since we've been stabilizing the 2.3 branch for a week [1] and that tests are ok (Caleb is looking at the last failing test) I think now would be a good time to release XE/XEM 2.3 final instead of RC2, I suggest to do the release tomorrow. Please shout if you need more time to commit things before 2.3 final.
Here's my +1.
I'm not done with http://jira.xwiki.org/jira/browse/XWIKI-4728 but the change it pretty big and dangerous for 2.3 final so I'll commit on trunk, for 2.4M1. +1 for releasing 2.3 final Thanks, Marius
[1] http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr...
Thanks, JV. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 04/22/2010 11:33 AM, Jean-Vincent Drean wrote:
Hi devs,
Since we've been stabilizing the 2.3 branch for a week [1] and that tests are ok (Caleb is looking at the last failing test) I think now would be a good time to release XE/XEM 2.3 final instead of RC2, I suggest to do the release tomorrow. Please shout if you need more time to commit things before 2.3 final.
Here's my +1.
[1] http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr...
+1 -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi all, I plan to fix http://jira.xwiki.org/jira/browse/XAANNOTATIONS-3 http://jira.xwiki.org/jira/browse/XAANNOTATIONS-10 and http://jira.xwiki.org/jira/browse/XAANNOTATIONS-17 by tonight. Otherwise, 0 for the release. Happy coding, Anca On 04/22/2010 12:33 PM, Jean-Vincent Drean wrote:
Hi devs,
Since we've been stabilizing the 2.3 branch for a week [1] and that tests are ok (Caleb is looking at the last failing test) I think now would be a good time to release XE/XEM 2.3 final instead of RC2, I suggest to do the release tomorrow. Please shout if you need more time to commit things before 2.3 final.
Here's my +1.
[1] http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr...
Thanks, JV. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi devs, Since we did not have the tests running successfully I haven't been able to do the release today. Tests should now be fixed, we should see successful builds this week-end, if so I'll perform the release on monday morning. If you plan on committing code before that please be careful not to commit in the modules included in the release plan: xwiki-configuration-resources xwiki-core (2.3 branch) xwiki-skin-colibri xwiki-platform-web (2.3 branch) xwiki-application-administration xwiki-application-annotations xwiki-product-enterprise (2.3 branch) http://dev.xwiki.org/xwiki/bin/view/Community/ReleasePlans Thanks, JV. On Thu, Apr 22, 2010 at 11:33 AM, Jean-Vincent Drean <[email protected]> wrote:
Hi devs,
Since we've been stabilizing the 2.3 branch for a week [1] and that tests are ok (Caleb is looking at the last failing test) I think now would be a good time to release XE/XEM 2.3 final instead of RC2, I suggest to do the release tomorrow. Please shout if you need more time to commit things before 2.3 final.
Here's my +1.
[1] http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr...
Thanks, JV.
participants (7)
-
Anca Luca -
Caleb James DeLisle -
Denis Gervalle -
Jean-Vincent Drean -
Marius Dumitru Florea -
Sergiu Dumitriu -
Vincent Massol