On Tue, 29 Mar 2016 12:34:11 +1030 Simon Lees <[email protected]> said: > Hi All, > > Now that I have slightly more time on my hands and to make the next > enlightenment release easier to manage I am proposing to volunteer to > maintain efl 1.18 as a LTS as it will be less effort then backporting > patches 1 by 1 into our build system. > > Why 1.18? It aligns best with our release cycle, which feature freezes > in September and releases in the first week of November. Based on the > success of this I will probably consider doing similar for every August > efl release.
chances are this will actually need long term support anyway for other reasons too - similar to yours. i think 1.18 is going tobe rough and need fixing/patching over time but that simply means backporting those fixes from continued devel. > I would expect to maintain the release for 18-24 months from the initial > release date taking over from the 1.18.X release when or soon after 1.19 > is released. I am not planning to backport every possible fix, generally > only issues reported by users or that manifest either in enlightenment > or another efl based app, As such it would be a rare occurrence where I > backported a fix that didn't have an associated bug report, the author > of the fix would probably have to contact me directly. A example of > something I probably would backport is > 4d6a8a7fce51b5654404226668a27d52d1e30eb3 - T3348, This example has a bug > report containing nice info such as someone has seen the crash and this > commit will fix it. Examples of things i'm less likely to backport > include commits with comments such as "while working on blah I noticed > xxx it was probably wrong and broken and fixed it." or "Potential fix > noitced by coverty its likely know one will ever see this issue". To > further make this easier it would be nice if fixes include the version > the bug was introduced in if its easy to figure out or a more general > this bug has been around for few years or was introduced in the last > release. > > The other reason for writing this now is to gauge interest from other > projects about collaborating / working together on this. There is also a > chance that I'll do something similar with enlightenment releases but > that will probably depend on the timing of releases and which release I > decide to include in the next openSUSE release. Feel free to raise any > concerns or issues here or on IRC. i think this is going to be useful in general - if we cherrypick/backport to the 1.18 stable branch this should make your life easy as you can just toss out packages based off tagged releases from that branch. :) > Cheers > > -- > > Simon Lees (Simotek) http://simotek.net > > Emergency Update Team keybase.io/simotek > SUSE Linux Adeliade Australia, UTC+10:30 > GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
