1 Apr
2016
1 Apr
'16
12:28 p.m.
Hi,
Depends what support means. If we are talking about what the committers can
support than this is agree and is the LTS (Long Term Support version). As
Thomas says this is a Nested Spaces version, so we shouldn't support the
Pre NS, still we should make it as smooth as possible for community members
to provide bugfixes on those versions.
Now since extensions don't share the same versioning scheme, telling what
LTS means for them is hard. Still I don't think we should try to add new
features to PreNS versions, since we shouldn't encourage deprecated
concepts. All extensions should try to provide code as new as possible.
So first of all, I would clearly document what is the version when NS
changes are done and what is the last version for PreNS. This way anyone
could add bugfixes on a tag branch, but if they want new features they
would be encouraged to upgrade.
So my answer is a mix of 2. and 3., mostly 3. but with allowance of 2. for
community members.
Thanks,
Caty
On Fri, Apr 1, 2016 at 12:53 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com>
wrote:
The current LTS is now 7.4.x and it support Nested
Space so +1 for 3)
On Fri, Apr 1, 2016 at 8:48 AM, Alexandru Cotiuga
<alexandru.cotiuga(a)xwiki.com> wrote:
Hello devs,
Since I already experimented the Nested Spaces behaviour on the Forum
application and there are other applications that might need it also, I
think it's time to start discussing this topic and to decide what
strategy
should be implemented on contrib applications.
What I have done in the Forum app was to handle both Pre NS and NS
versions
of XWiki, writing specific code for each case
(wrapped in if-else
statements), which proved to be the most complex and hard to maintain
way,
without much benefit. Sooner or later, everybody
will have a NS Xwiki
version and then all the support for Pre NS would become useless and then
the code should be cleaned, which would be a lot of work again.
Besides this already tried strategy, there are some others to be
discused:
1: Support both Pre NS and NS versions but in different branches.
2: Move to NS, but keep fixing bugs for Pre NS in a separate branch.
(This
is what I'm proposing)
3: Move to NS without any maintance on Pre NS.
4: Others?
In all the cases, a data migration should be performed.
What we decide to do?
Thanks,
Alex
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs