26 Nov
2007
26 Nov
'07
11:18 p.m.
Vincent Massol wrote:
I can't see anything in the core that would need 1.2 for space/invitation
manager. However, those last two have to use the mailsender plugin IMO,
which was first released against the 1.2-milestone version of platform.
Maybe the watchlist plugin might be usefull also.
It could then be possible to make them compatible introducing version
checking and introspection for new methods (like minor edits), WDYT ?
FYI, I introduced a first skeleton of the spacemanager plugin in the
sandbox. I made it depend on 1.1 for now. The purpose of that plugin is to
create an "extended" idea of spaces, by managing users invitations,
membership requests, and other nice features in the future. Review and
comments would be very welcomed.
Jérôme.
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.
>
>
+1
> 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.
>
>
+1
> 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.
>
>
We will need to actually test migration to 1.2 in Curriki. This is quite
short in the Curriki 1.5 release timeframe (January 10th).
Now we should not need 1.2 features, except the new Invitation/Space
Manager plugin..
So the big question for Curriki is wether it will be possible to use the
new Invitation/Space Manager plugin with 1.1.
Aside from that I don't think Curriki needs a 1.1.3 release
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Here's my +1 to all 3 items above.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs