26 Nov
2007
26 Nov
'07
8:25 p.m.
Here's the result:
* Item 1), 4 +1
* Item 2), 4 +1
* Item 3), 3 +1 (and a +1 from XEM from Thomas)
Only "issue" is that nobody working on Curriki has answered point 3.
Can curriki use version 1.2 which is planned to be out in final in 2
weeks from now or will Curriki need a 1.1.3 before that (I hope not
since doing a 1.1.3 release will harm the rest as it's always a pain
to do a release).
To repeat: I'd like to remove the 1.1 branch. If someone suddenly and
urgently needs a new 1.1.x release he can also branch the 1.1.2 tag
and commit there and release.
Ludovic?
Thanks
-Vincent
On Nov 18, 2007, at 7:22 PM, Vincent Massol wrote:
Hi,
Since we're nearing the final XE 1.2 release I'd like that we vote on
each of the following:
1) Once Panels app 1.2 is released, separate the versioning of the
Panels app from the versioning of XE/Platform, i.e. next version will
be 1.3 without milestones. Same as for the other apps/plugins.
2) Create a branch now for XE/Platform/Panels 1.2RC1 so that work can
start on trunk for Platform 1.3M1 and XE 1.3M1.
3) Don't do a XE/PF/Panels 1.1.3 release and instead move XEM and
other products to XE/PF/Panels 1.2 final (since it's going to be
released in less than a month). This will also allow to have only 2
branches to manage: the trunk and the branch from 2). This also means
that we should probably release a XEM 1.0 quickly (that'll use PF
1.1.2) and start working on XEM 1.1 on trunk which will use PF 1.2.
Here's my +1 to all 3 items above.
Thanks
-Vincent