Ok, digging this out again.
Provide LTS versions of the Semantic Bundle.
On 5 December 2012 22:39, James HK <firstname.lastname@example.org> wrote:
> # What would LTS mean in connection with SMW ?
This would mean:
* to branch off versions* of SMW
* to include updated versions of extensions in the Semantic Bundle as
long as they support the relevant SMW version
* to branch off versions of these extensions once they stop supporting
the relevant SMW version
* to clearly state extensions contained in the bundle including their versions
* to clearly state compatibility of the bundle to MW versions
* to apply patches to contained extensions if somebody provides them
* Considered versions of SMW would be the last minor versions before
the release of a new major version of SMW, i.e. 1.5.6, 1.6.1, 1.7.1,
Of these only take one per year and support it for two(?) years. This
would mean 1.6.1 (2011), 1.8 (2012), and 1.10 (2013).
Extension developers should anounce new versions of their extensions
> # Which implications would LTS have on future developments ?
stating compatibility of their extension to MW and SMW. They should
tag release versions of their extensions in git.
They should also think about if a bug or feature is important enough
to be backported.
Availability of stable Semantic Bundles on older MWs, giving people
> # Why would SMW need/want to support a LTS infrastructure ? What would
> be the benefit ?
more time to plan their updates and allow them to do updates less
I would do the administration work incl. applying patches. I would in
> # Who will do LTS for SMW and what infrastructure is needed to support
> LTS (own branch etc.)
general not do backporting.
I would propose to keep download versions on Google Code along with
the regular packages and document the contents on
semantic-mediawiki.org and/or mediawiki.org, e.g. as subpages of the
See above. Basically freeze for SMW and extensions that don't support
> # Would LTS mean a freeze release or do features from a development
> branch are back ported to a LTS?
the frozen SMW anymore. Patches applied if provided.
What do you think?
Maybe think about that again. SMW 1.6 to 1.8 all supported up to two
> # SMW 1.8 supports MW 1.17/1.18+
> # SMW 1.9 is planned to support MW 1.19/1.20/1.21 / PHP 5.3 or greater
> # SMW 1.10 is planned to support MW 1.20 (or 1.21 pending on the release date)
year old MW versions. With the roadmap as it is this would drop to one
year for 1.9.
SMW -> MW: Delay
1.6 (30/07/2011) -> 1.15 (25/03/2009): 2.3 years
1.6.1 (20/08/2011) -> 1.15 (25/03/2009): 2.4 years
1.7 (01/01/2012) -> 1.16 (22/02/2010): 1.9 years
1.7.1 (05/03/2012) -> 1.16 (22/02/2010) 2.0 years
1.8 (02/12/2012) -> 1.17 (07/12/2010): 2.0 years
1.9 (15/03/2013) -> 1.19 (09/02/2012): 1.1 years
1.10 (15/08/2013) -> 1.19 (09/02/2012): 1.5 years
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
Semediawiki-devel mailing list