[xwiki-devs] [VOTE] Upgrade xwiki.org
Hi guys, In order to finish convert extensions.xwiki.org into a valid XWiki Repository server (supported by Extension Manager) I need to put a upgrade xwiki.org and add a jar file (mostly about REST interface). Thing is I need to put the latest 3.3 snapshot version of this REST module so I can see two solutions: * upgrade to 3.2 and patch it with several new API needed by the module * upgrade to latest 3.3 SNAPSHOT pros 3.3 * more simple for me * we can probably quickly come back to the current 3.1.1 if a blocking issue is found until it's fixed * I'm going to quickly update xwiki.org any time we find and fix a blocker issue cons 3.3 * snapshot version on production There is some things I'm not 100% sure: * is there any modification of to the DB introduced in 3.3 not compatible with 3.1.1 and not introduced in 3.2 ? I know id change has not been committed yet +1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there is not incompatible DB change -- Thomas Mortagne
On Nov 8, 2011, at 10:22 AM, Thomas Mortagne wrote:
Hi guys,
In order to finish convert extensions.xwiki.org into a valid XWiki Repository server (supported by Extension Manager) I need to put a upgrade xwiki.org and add a jar file (mostly about REST interface).
Thing is I need to put the latest 3.3 snapshot version of this REST module so I can see two solutions: * upgrade to 3.2 and patch it with several new API needed by the module * upgrade to latest 3.3 SNAPSHOT
pros 3.3 * more simple for me * we can probably quickly come back to the current 3.1.1 if a blocking issue is found until it's fixed * I'm going to quickly update xwiki.org any time we find and fix a blocker issue
cons 3.3 * snapshot version on production
There is some things I'm not 100% sure: * is there any modification of to the DB introduced in 3.3 not compatible with 3.1.1 and not introduced in 3.2 ? I know id change has not been committed yet
+1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there is not incompatible DB change
Same here +1 for 3.3SNAPSHOT. You could also install XE 3.2 as a fallback solution if 3.3SNAPSHOT is not stable enough. Thanks -Vincent
On Tue, Nov 8, 2011 at 10:33 AM, Vincent Massol <[email protected]> wrote:
On Nov 8, 2011, at 10:22 AM, Thomas Mortagne wrote:
Hi guys,
In order to finish convert extensions.xwiki.org into a valid XWiki Repository server (supported by Extension Manager) I need to put a upgrade xwiki.org and add a jar file (mostly about REST interface).
Thing is I need to put the latest 3.3 snapshot version of this REST module so I can see two solutions: * upgrade to 3.2 and patch it with several new API needed by the module * upgrade to latest 3.3 SNAPSHOT
pros 3.3 * more simple for me * we can probably quickly come back to the current 3.1.1 if a blocking issue is found until it's fixed * I'm going to quickly update xwiki.org any time we find and fix a blocker issue
cons 3.3 * snapshot version on production
There is some things I'm not 100% sure: * is there any modification of to the DB introduced in 3.3 not compatible with 3.1.1 and not introduced in 3.2 ? I know id change has not been committed yet
+1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there is not incompatible DB change
Same here +1 for 3.3SNAPSHOT.
You could also install XE 3.2 as a fallback solution if 3.3SNAPSHOT is not stable enough.
Sure but If I can avoid doing two upgrades instead of one that would be nice :)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 for 3.3-SNAPSHOT Thanks, Marius On Tue, Nov 8, 2011 at 11:40 AM, Thomas Mortagne <[email protected]> wrote:
On Tue, Nov 8, 2011 at 10:33 AM, Vincent Massol <[email protected]> wrote:
On Nov 8, 2011, at 10:22 AM, Thomas Mortagne wrote:
Hi guys,
In order to finish convert extensions.xwiki.org into a valid XWiki Repository server (supported by Extension Manager) I need to put a upgrade xwiki.org and add a jar file (mostly about REST interface).
Thing is I need to put the latest 3.3 snapshot version of this REST module so I can see two solutions: * upgrade to 3.2 and patch it with several new API needed by the module * upgrade to latest 3.3 SNAPSHOT
pros 3.3 * more simple for me * we can probably quickly come back to the current 3.1.1 if a blocking issue is found until it's fixed * I'm going to quickly update xwiki.org any time we find and fix a blocker issue
cons 3.3 * snapshot version on production
There is some things I'm not 100% sure: * is there any modification of to the DB introduced in 3.3 not compatible with 3.1.1 and not introduced in 3.2 ? I know id change has not been committed yet
+1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there is not incompatible DB change
Same here +1 for 3.3SNAPSHOT.
You could also install XE 3.2 as a fallback solution if 3.3SNAPSHOT is not stable enough.
Sure but If I can avoid doing two upgrades instead of one that would be nice :)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 for 3.3-SNAPSHOT Thanks, Eduard On Tue, Nov 8, 2011 at 2:12 PM, Marius Dumitru Florea < [email protected]> wrote:
+1 for 3.3-SNAPSHOT
Thanks, Marius
On Tue, Nov 8, 2011 at 11:40 AM, Thomas Mortagne <[email protected]> wrote:
On Tue, Nov 8, 2011 at 10:33 AM, Vincent Massol <[email protected]> wrote:
On Nov 8, 2011, at 10:22 AM, Thomas Mortagne wrote:
Hi guys,
In order to finish convert extensions.xwiki.org into a valid XWiki Repository server (supported by Extension Manager) I need to put a upgrade xwiki.org and add a jar file (mostly about REST interface).
Thing is I need to put the latest 3.3 snapshot version of this REST module so I can see two solutions: * upgrade to 3.2 and patch it with several new API needed by the module * upgrade to latest 3.3 SNAPSHOT
pros 3.3 * more simple for me * we can probably quickly come back to the current 3.1.1 if a blocking issue is found until it's fixed * I'm going to quickly update xwiki.org any time we find and fix a
blocker issue
cons 3.3 * snapshot version on production
There is some things I'm not 100% sure: * is there any modification of to the DB introduced in 3.3 not compatible with 3.1.1 and not introduced in 3.2 ? I know id change has not been committed yet
+1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there is not incompatible DB change
Same here +1 for 3.3SNAPSHOT.
You could also install XE 3.2 as a fallback solution if 3.3SNAPSHOT is not stable enough.
Sure but If I can avoid doing two upgrades instead of one that would be nice :)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 for 3.3-SNAPSHOT Jerome On Tue, Nov 8, 2011 at 1:31 PM, Eduard Moraru <[email protected]> wrote:
+1 for 3.3-SNAPSHOT
Thanks, Eduard
On Tue, Nov 8, 2011 at 2:12 PM, Marius Dumitru Florea < [email protected]> wrote:
+1 for 3.3-SNAPSHOT
Thanks, Marius
On Tue, Nov 8, 2011 at 11:40 AM, Thomas Mortagne <[email protected]> wrote:
On Tue, Nov 8, 2011 at 10:33 AM, Vincent Massol <[email protected]> wrote:
On Nov 8, 2011, at 10:22 AM, Thomas Mortagne wrote:
Hi guys,
In order to finish convert extensions.xwiki.org into a valid XWiki Repository server (supported by Extension Manager) I need to put a upgrade xwiki.org and add a jar file (mostly about REST interface).
Thing is I need to put the latest 3.3 snapshot version of this REST module so I can see two solutions: * upgrade to 3.2 and patch it with several new API needed by the module * upgrade to latest 3.3 SNAPSHOT
pros 3.3 * more simple for me * we can probably quickly come back to the current 3.1.1 if a blocking issue is found until it's fixed * I'm going to quickly update xwiki.org any time we find and fix a
blocker issue
cons 3.3 * snapshot version on production
There is some things I'm not 100% sure: * is there any modification of to the DB introduced in 3.3 not compatible with 3.1.1 and not introduced in 3.2 ? I know id change has not been committed yet
+1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there is not incompatible DB change
Same here +1 for 3.3SNAPSHOT.
You could also install XE 3.2 as a fallback solution if 3.3SNAPSHOT is not stable enough.
Sure but If I can avoid doing two upgrades instead of one that would be nice :)
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jérôme Velociter Winesquare http://www.winesquare.net/
On 11/08/2011 04:22 AM, Thomas Mortagne wrote:
Hi guys,
In order to finish convert extensions.xwiki.org into a valid XWiki Repository server (supported by Extension Manager) I need to put a upgrade xwiki.org and add a jar file (mostly about REST interface).
Thing is I need to put the latest 3.3 snapshot version of this REST module so I can see two solutions: * upgrade to 3.2 and patch it with several new API needed by the module * upgrade to latest 3.3 SNAPSHOT
pros 3.3 * more simple for me * we can probably quickly come back to the current 3.1.1 if a blocking issue is found until it's fixed * I'm going to quickly update xwiki.org any time we find and fix a blocker issue
cons 3.3 * snapshot version on production
There is some things I'm not 100% sure: * is there any modification of to the DB introduced in 3.3 not compatible with 3.1.1 and not introduced in 3.2 ? I know id change has not been committed yet
+1 for 3.3 SNAPSHOT (ok the pros/cons is a bit oriented ;)) if there is not incompatible DB change
+1 for 3.3S. Extra care must be taken with the resulting duplicate indexes. -- Sergiu Dumitriu http://purl.org/net/sergiu/
participants (6)
-
Eduard Moraru -
Jerome Velociter -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol