[xwiki-devs] [VOTE] XE 2.6 Roadmap
Hi, I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc) In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it. If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long. Here's my +1 Thanks -Vincent
On 10/20/2010 10:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I'd like to also commit some changes to the velocity templates and skin to improve the support for portlet integration. Hope this is fine.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
+1 Thanks, Marius
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Oct 20, 2010, at 11:22 AM, Marius Dumitru Florea wrote:
On 10/20/2010 10:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I'd like to also commit some changes to the velocity templates and skin to improve the support for portlet integration. Hope this is fine.
Yes the only requirement for committers wanting to commit stuff would be that they are not "dangerous" (i.e. well tested and not core stuff that are potentially complex and thus dangerous) and that they fit in the timeframe. Thanks -Vincent
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
+1
Thanks, Marius
Thanks -Vincent
+1, JV. On Wed, Oct 20, 2010 at 9:31 AM, Vincent Massol <[email protected]> wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 Alex On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 -- Thibaut On Wed, Oct 20, 2010 at 3:22 PM, Alex Busenius <[email protected]
wrote:
+1
Alex
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release. So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Le 21 oct. 2010 à 01:08, Sergiu Dumitriu a écrit :
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release. +1
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
+1, also we should debate about what should be the "mission" of 3.0, let me explain : the purpose of 2.x version was to have a very user friendly wiki (wysiwig, improved UX, etc.), the "big thing" about 3.0 should be then discussed and defined. the actual things are : - an easy platform to develop in (extension manager, more dev documentation, features to make easy devs like "app within a minute", etc.) - a social wiki (cf. wiki 3.0 project ...) - ?... => an intense debate about it ?... => then a survey ?...
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Thu, Oct 21, 2010 at 01:08, Sergiu Dumitriu <[email protected]> wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
I strongly agree with Sergui. There are many small issues (event not yet discovered) and annoyances that have been left back and that should not go into a 3.0 release. There is probably also some improvement on security required. So pursuing a while with regular 2.x release to stabilized the 3.0 release is for me a must. I know that I have not much time to participate these days, and hopelessly this will not improve soo, but I will try to helps as much as I can on these one.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
Starting development on 3.x trunk simultaneously is a good way to keep visual improvements going. Discussion on what the 3.x should be is obviously required. Ttargeting an old core and legacy code free version for 4.0 is really what I am dreaming about. WDYT ? My +1 for stabilisations releases. Denis
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
Hi Sergiu, On Oct 21, 2010, at 1:08 AM, Sergiu Dumitriu wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
I actually think that 3 weeks is already almost too much actually, since the longest the likeliest people will introduce new features and not do stabilization. In addition this gives less chance for people to test the stabilization release(s) (people only test when there are final releases). I'd really like to keep the proposed dates. Please let me know if it's ok with you since you're the only one who voiced a concern on the date. Thanks -Vincent
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
On 10/25/2010 12:32 PM, Vincent Massol wrote:
Hi Sergiu,
On Oct 21, 2010, at 1:08 AM, Sergiu Dumitriu wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
I actually think that 3 weeks is already almost too much actually, since the longest the likeliest people will introduce new features and not do stabilization.
WDYM 3 weeks? When did you start counting? 1st is next week, so just one week between 2.5 and 2.6RC1. Also, trunk became 2.6 on the 14th, so that would be only two weeks since the 2.6 version was introduced, I really don't understand where the 3 weeks before the RC came. Note that I only proposed moving the RC date, not the final date.
In addition this gives less chance for people to test the stabilization release(s) (people only test when there are final releases).
I'd really like to keep the proposed dates. Please let me know if it's ok with you since you're the only one who voiced a concern on the date.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Oct 25, 2010, at 2:21 PM, Sergiu Dumitriu wrote:
On 10/25/2010 12:32 PM, Vincent Massol wrote:
Hi Sergiu,
On Oct 21, 2010, at 1:08 AM, Sergiu Dumitriu wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
I actually think that 3 weeks is already almost too much actually, since the longest the likeliest people will introduce new features and not do stabilization.
WDYM 3 weeks?
End to end, it's actually 3.5 weeks (I don't know why I put the date of 18th of Nov. I think I wanted to put 15th initially but that slipped for some reason... anyway let's keep 18th but with no slippage ;) ie we should start releasing no later than the 15th, if not earlier ;)).
When did you start counting? 1st is next week, so just one week between 2.5 and 2.6RC1. Also, trunk became 2.6 on the 14th, so that would be only two weeks since the 2.6 version was introduced, I really don't understand where the 3 weeks before the RC came. Note that I only proposed moving the RC date, not the final date.
I thought you were proposing to move the final date. I'm +0 to move only the RC by one week (although this gives less time for stabilization and may result in more features being added in). A few days instead of a week would be better. We need the stabilization time as much as possible IMO. One week less means less stabilization on the new features add for RC1. Note that Raluca thinks she'll have finished the Recent Activity feature for the 1st of Nov. Thanks -Vincent
In addition this gives less chance for people to test the stabilization release(s) (people only test when there are final releases).
I'd really like to keep the proposed dates. Please let me know if it's ok with you since you're the only one who voiced a concern on the date.
On 10/25/2010 02:26 PM, Vincent Massol wrote:
On Oct 25, 2010, at 2:21 PM, Sergiu Dumitriu wrote:
On 10/25/2010 12:32 PM, Vincent Massol wrote:
Hi Sergiu,
On Oct 21, 2010, at 1:08 AM, Sergiu Dumitriu wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
I actually think that 3 weeks is already almost too much actually, since the longest the likeliest people will introduce new features and not do stabilization.
WDYM 3 weeks?
End to end, it's actually 3.5 weeks (I don't know why I put the date of 18th of Nov. I think I wanted to put 15th initially but that slipped for some reason... anyway let's keep 18th but with no slippage ;) ie we should start releasing no later than the 15th, if not earlier ;)).
When did you start counting? 1st is next week, so just one week between 2.5 and 2.6RC1. Also, trunk became 2.6 on the 14th, so that would be only two weeks since the 2.6 version was introduced, I really don't understand where the 3 weeks before the RC came. Note that I only proposed moving the RC date, not the final date.
I thought you were proposing to move the final date.
I'm +0 to move only the RC by one week (although this gives less time for stabilization and may result in more features being added in). A few days instead of a week would be better. We need the stabilization time as much as possible IMO. One week less means less stabilization on the new features add for RC1.
I'm +0 on either date, my statement was just a "if possible", since 18 days between a RC and the final release is a more than what we usually do.
Note that Raluca thinks she'll have finished the Recent Activity feature for the 1st of Nov.
Thanks -Vincent
In addition this gives less chance for people to test the stabilization release(s) (people only test when there are final releases).
I'd really like to keep the proposed dates. Please let me know if it's ok with you since you're the only one who voiced a concern on the date.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Oct 25, 2010, at 2:44 PM, Sergiu Dumitriu wrote:
On 10/25/2010 02:26 PM, Vincent Massol wrote:
On Oct 25, 2010, at 2:21 PM, Sergiu Dumitriu wrote:
On 10/25/2010 12:32 PM, Vincent Massol wrote:
Hi Sergiu,
On Oct 21, 2010, at 1:08 AM, Sergiu Dumitriu wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
I actually think that 3 weeks is already almost too much actually, since the longest the likeliest people will introduce new features and not do stabilization.
WDYM 3 weeks?
End to end, it's actually 3.5 weeks (I don't know why I put the date of 18th of Nov. I think I wanted to put 15th initially but that slipped for some reason... anyway let's keep 18th but with no slippage ;) ie we should start releasing no later than the 15th, if not earlier ;)).
When did you start counting? 1st is next week, so just one week between 2.5 and 2.6RC1. Also, trunk became 2.6 on the 14th, so that would be only two weeks since the 2.6 version was introduced, I really don't understand where the 3 weeks before the RC came. Note that I only proposed moving the RC date, not the final date.
I thought you were proposing to move the final date.
I'm +0 to move only the RC by one week (although this gives less time for stabilization and may result in more features being added in). A few days instead of a week would be better. We need the stabilization time as much as possible IMO. One week less means less stabilization on the new features add for RC1.
I'm +0 on either date, my statement was just a "if possible", since 18 days between a RC and the final release is a more than what we usually do.
Indeed. I think I messed up the end date. what about a RC2 for the 8th of Nov. 2.6RC1: 1st of Nov 2.6RC2: 8th of Nov 2.6 final: start 15th, done for the 18th at latest Thanks -Vincent
Note that Raluca thinks she'll have finished the Recent Activity feature for the 1st of Nov.
Thanks -Vincent
In addition this gives less chance for people to test the stabilization release(s) (people only test when there are final releases).
I'd really like to keep the proposed dates. Please let me know if it's ok with you since you're the only one who voiced a concern on the date.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On 10/25/2010 02:51 PM, Vincent Massol wrote:
On Oct 25, 2010, at 2:44 PM, Sergiu Dumitriu wrote:
On 10/25/2010 02:26 PM, Vincent Massol wrote:
On Oct 25, 2010, at 2:21 PM, Sergiu Dumitriu wrote:
On 10/25/2010 12:32 PM, Vincent Massol wrote:
Hi Sergiu,
On Oct 21, 2010, at 1:08 AM, Sergiu Dumitriu wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote: > The idea would be to have the following dates: > - 2.6RC1: 1st of November 2010 (there's no M1) > - 2.6 final: 18h of November
I'd move the RC one week later.
I actually think that 3 weeks is already almost too much actually, since the longest the likeliest people will introduce new features and not do stabilization.
WDYM 3 weeks?
End to end, it's actually 3.5 weeks (I don't know why I put the date of 18th of Nov. I think I wanted to put 15th initially but that slipped for some reason... anyway let's keep 18th but with no slippage ;) ie we should start releasing no later than the 15th, if not earlier ;)).
When did you start counting? 1st is next week, so just one week between 2.5 and 2.6RC1. Also, trunk became 2.6 on the 14th, so that would be only two weeks since the 2.6 version was introduced, I really don't understand where the 3 weeks before the RC came. Note that I only proposed moving the RC date, not the final date.
I thought you were proposing to move the final date.
I'm +0 to move only the RC by one week (although this gives less time for stabilization and may result in more features being added in). A few days instead of a week would be better. We need the stabilization time as much as possible IMO. One week less means less stabilization on the new features add for RC1.
I'm +0 on either date, my statement was just a "if possible", since 18 days between a RC and the final release is a more than what we usually do.
Indeed. I think I messed up the end date. what about a RC2 for the 8th of Nov.
2.6RC1: 1st of Nov 2.6RC2: 8th of Nov 2.6 final: start 15th, done for the 18th at latest
+1.
Note that Raluca thinks she'll have finished the Recent Activity feature for the 1st of Nov.
Thanks -Vincent
In addition this gives less chance for people to test the stabilization release(s) (people only test when there are final releases).
I'd really like to keep the proposed dates. Please let me know if it's ok with you since you're the only one who voiced a concern on the date.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Thu, Oct 21, 2010 at 1:08 AM, Sergiu Dumitriu <[email protected]> wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
I would like to add "annotations" to this list (especially making them work w/o JS and and activated by default) I'm OK to work on that if we agree we want it. Jerome.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Oct 26, 2010, at 5:39 PM, Jerome Velociter wrote:
On Thu, Oct 21, 2010 at 1:08 AM, Sergiu Dumitriu <[email protected]> wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
I would like to add "annotations" to this list (especially making them work w/o JS and and activated by default)
Could you be more specific re annotations?
I'm OK to work on that if we agree we want it.
For 2.6? Thanks -Vincent
Jerome.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Tue, Oct 26, 2010 at 6:44 PM, Vincent Massol <[email protected]> wrote:
On Oct 26, 2010, at 5:39 PM, Jerome Velociter wrote:
On Thu, Oct 21, 2010 at 1:08 AM, Sergiu Dumitriu <[email protected]> wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
I would like to add "annotations" to this list (especially making them work w/o JS and and activated by default)
Could you be more specific re annotations?
Yes. I meant at least two things : * Activate annotations as a default setting * Have annotations displayed even when JavaScript is not available (that means moving code from the annotation application to the platform - but that's another story) And a third item, a bit more ambitious (so maybe for 2.7 ?) : * Fusion annotations with comments (at least in the U. Probably in the storage (read: XClass) by default too - to make the UI easier to write). Comments would then become annotations without a context. That would already be great. Jerome.
I'm OK to work on that if we agree we want it.
For 2.6?
Thanks -Vincent
Jerome.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Oct 28, 2010, at 5:29 PM, Jerome Velociter wrote:
On Tue, Oct 26, 2010 at 6:44 PM, Vincent Massol <[email protected]> wrote:
On Oct 26, 2010, at 5:39 PM, Jerome Velociter wrote:
On Thu, Oct 21, 2010 at 1:08 AM, Sergiu Dumitriu <[email protected]> wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
I would like to add "annotations" to this list (especially making them work w/o JS and and activated by default)
Could you be more specific re annotations?
Yes. I meant at least two things :
* Activate annotations as a default setting * Have annotations displayed even when JavaScript is not available (that means moving code from the annotation application to the platform - but that's another story)
And a third item, a bit more ambitious (so maybe for 2.7 ?) :
* Fusion annotations with comments (at least in the U. Probably in the storage (read: XClass) by default too - to make the UI easier to write). Comments would then become annotations without a context.
That would already be great.
Are you proposing to implement these features yourself? If not, we need someone to volunteer. Thanks -Vincent
Jerome.
I'm OK to work on that if we agree we want it.
For 2.6?
Thanks -Vincent
Jerome.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
On Thu, Oct 28, 2010 at 5:37 PM, Vincent Massol <[email protected]> wrote:
On Oct 28, 2010, at 5:29 PM, Jerome Velociter wrote:
On Tue, Oct 26, 2010 at 6:44 PM, Vincent Massol <[email protected]> wrote:
On Oct 26, 2010, at 5:39 PM, Jerome Velociter wrote:
On Thu, Oct 21, 2010 at 1:08 AM, Sergiu Dumitriu <[email protected]> wrote:
On 10/20/2010 09:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose to sprint for a winter 3.0 release. I believe that since 2.0 we've added (or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready to be promoted as 3.0. This means that the number of new features should be kept to a minimum, trying to finish all the stuff that was already started: gadgets, portlets (a bit difficult, so this is not a hard requirement), new UIs (administration, multipage export, standard forms, maybe rights), xwiki/2.1 syntax, extension manager.
I would like to add "annotations" to this list (especially making them work w/o JS and and activated by default)
Could you be more specific re annotations?
Yes. I meant at least two things :
* Activate annotations as a default setting * Have annotations displayed even when JavaScript is not available (that means moving code from the annotation application to the platform - but that's another story)
And a third item, a bit more ambitious (so maybe for 2.7 ?) :
* Fusion annotations with comments (at least in the U. Probably in the storage (read: XClass) by default too - to make the UI easier to write). Comments would then become annotations without a context.
That would already be great.
Ah and I forgot : by default activate show the annotation pop-up upon just selection, not Meta + M - (but keep it configurable as it is)
Are you proposing to implement these features yourself?
For the first 2 (+ that new one), yes I can do it. For the merging with comments UI, it's a bit more work, so I don't think I can engage myself on it yet. Jerome.
If not, we need someone to volunteer.
Thanks -Vincent
Jerome.
I'm OK to work on that if we agree we want it.
For 2.6?
Thanks -Vincent
Jerome.
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
I'd move the RC one week later.
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
I could do it as well, if nobody else volunteers.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
We could already create a 3.1 branch/trunk for new stuff when needed, although this will increase the number of maintained branches a bit too much. To help here, we can decide not to do maintainance releases for the 2.6+ branches, since these are short releases.
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 Thanks, Florin Ciubotaru On Wed, Oct 20, 2010 at 10:31 AM, Vincent Massol <[email protected]> wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 On Wed, Oct 20, 2010 at 09:31, Vincent Massol <[email protected]> wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
VOTE has passed. I've published it: http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap Thanks -Vincent On Oct 20, 2010, at 9:31 AM, Vincent Massol wrote:
Hi,
I'd like to propose that we have a short XE 2.6 release. The rationale is that we've been developing lots of new features in the past releases and I think it's time to stabilize what we have. By stabilize I mean: - fix bugs - homogenize UI - clean up stuff (refactoring, etc)
In addition we have 2 features we had planned for 2.5 which have slipped and we could finish them in 2.6 too (Sergiu said he was almost done with the "Email this page" feature and didn't have the time to slip it in the 2.5): - Email this page: Sergiu - Recent Activity (refactoring of Recent Changes based on the Activity Stream): Raluca + Caty + JV to apply the patch
The idea would be to have the following dates: - 2.6RC1: 1st of November 2010 (there's no M1) - 2.6 final: 18h of November
If we agree, is there anyone who'd like to be the release manager for this release? If nobody volunteers I can do it.
If we agree, I'll send another mail afterwards with some ideas for XE 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first step in stabilizing XE for an upcoming 3.0 release :) But even without this vision doing a short stabilization release from time to time is always a good think I believe. It's also not too long so that people don't need to hold new stuff for too long.
Here's my +1
Thanks -Vincent
participants (11)
-
Alex Busenius -
Denis Gervalle -
Florin Ciubotaru -
Gregory GUENEAU -
Jean-Vincent Drean -
Jerome Velociter -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thibaut Camberlin -
Thomas Mortagne -
Vincent Massol