On 09/10/2016 08:07 AM, Andrew Williams wrote: > Hi. > > The schedule sounds fine - you're right there is plenty to do. > But. I feel after the Eo API is still not stable after 1.18 that maybe the > release milestones should be a feature / API / completeness commitment > rather than time? Honestly right now I want to avoid another release that > may not be a stable API, it's kind of painful continually tracking master - > every time there is a release then 2 days later we have breaking changes. > I know that's the deal with a beta API - but a plan for delivering all that > remains here would be very reassuring. > > Thanks, > Andrew
I think that the time based releases have worked well in most cases. The only times when they haven't really is when there has been massive changes across the API and that doesn't happen often, there was 1.8 then 1.18/1.19 I think its got to the point where for 1.19 it really shouldn't be released until the eo interfaces are done from a distro point of view there are a number of apps that I can't provide stable packages for because there using eo api and I can't guarantee everything will stay in sync. Having said that after those major changes I'd expect releases to become more normal again and moving back to the time based schedule makes sense (There could be one further slightly longer or slightly shorter release to get everything back in sync time wise). That is probably until someone pulls the plug and decides its time for efl 2.0 which should probably also be feature released rather then time based. Cheers > > On Fri, 9 Sep 2016 at 09:25 Stefan Schmidt <ste...@osg.samsung.com> wrote: > >> Hello. >> >> On 05/09/16 16:20, Stefan Schmidt wrote: >>> Hello. >>> >>> 1.18 is out for almost a month now. Time to start thinking about the >>> schedule for 1.19. >>> >>> Personally I would like that we get back to our original 3 months >>> schedule as soon as possible. Reality is that we had to postpone some >>> work on interfaces towards 1.19 so I want to gather some input here what >>> timelines people have in mind for this. >>> >>> Doing 1.19 in a 3 months rhythm already seems a bit unrealistic. >>> Especially as one month is already over which would result in beginning >>> of November for the release. Is 4 months and a release early December >>> more realistic? Not sure if dragging it out further would really help as >>> end of December and early January are holiday season for a lot of people >>> here. >>> >>> 2016-08-11 Merge window for 1.19 opens >>> 2016-11-07 Merge window is over. >>> * Only bug fixes from this point >>> * Alpha release tarball >>> * One month stabilization phase starts >>> 2016-11-14 Beta1 release tarball >>> * Only critical fixes from this point >>> 2016-11-21 Beta2 release tarball >>> 2016-11-28 Beta3 release tarball >>> 2016-12-05 EFL 1.19 is out (First Monday in December) >>> >>> This is just a suggestion. I would like to get some input here. >> >> Comments anyone? >> >> regards >> Stefan Schmidt >> -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
