On Thu, 9 Feb 2017 10:16:12 +0100 Stefan Schmidt <ste...@osg.samsung.com> said:
> Hello.
>
> On 09/02/17 00:47, Carsten Haitzler (The Rasterman) wrote:
> > On Wed, 8 Feb 2017 15:12:56 +0100 Stefan Schmidt <ste...@osg.samsung.com>
> > said:
> >
> >> Hello.
> >>
> >> On 07/02/17 10:37, Carsten Haitzler (The Rasterman) wrote:
> >>> On Tue, 7 Feb 2017 18:25:58 +1030 Simon Lees <sfl...@suse.de> said:
> >>>
> >>>>
> >>>>
> >>>> On 02/06/2017 10:06 PM, Gustavo Sverzut Barbieri wrote:
> >>>>>
> >>>>> Time-based releases keep the expectations if they are followed. Once
> >>>>> we miss the frame, we start to have this feature-based releases ("oh,
> >>>>> waited so long, can wait a bit more") and when people work
> >>>>> independently, they always have some in-flux work that could get in...
> >>>>> so at some point these guys will want to delay a bit more so their
> >>>>> work gets in as well... endless wait -- AKA e17/efl-1.0
> >>>>>
> >>>>> IOW: just do it, and let's not miss the 3 month schedule next time. ;-)
> >>>>>
> >>>>>
> >>>>
> >>>> The problem is people (even some in Samsung) are writing software that
> >>>> depends on unstable eo, regardless of whether its wrong or right its
> >>>> happening. This means that every release there is an extra bunch of work
> >>>> for downstream projects to roll another release and then for distro's to
> >>>> package all theses changes.
> >>
> >> What are the offending packages you have to deal with here? As far as I
> >> know it neither Enlightenment nor Termonology nor Rage is using any EO
> >> based API.
> >>
> >> They only ones I know of are developer tools like Edi, Eventor and
> >> Efleete. Are these packaged in OpenSUSE?
> >
> > those are the ones. especially eflete and enventor.
>
> OK, and Simon confirmed that they are packaged but not part of the main
> distro due to the unstable interface.
>
> >>> that is a very good point. the reliance on eo anyway... and thus a 1.19
> >>> will mean everything that did (wrongly) rely on it has to update/rev and
> >>> release too.
> >>
> >> That was the case for various former releases as well. It is a pain for
> >> people like Simon I fully understand this, but it is nothing new for 1.19.
> >
> > it is indeed nothing new, BUT it is a factor. a pain factor. the question
> > is... is it enough of one to say "wait on release"?
> >
> > i'd REALLY like to keep our stabilization cycle as short as we can manage
> > so it doesn't impact finishing off interfaces.
>
> Agreed. See below for a shortened schedule.
>
> > yes we can argue that "that work can happen in branches" but that then
> > violates the whole idea of stabilization. the POINT is for everyone to stop
> > (well over a few days/week) their current work, go back over work they AND
> > others have done, and fix bugs. look at what coverity has to say. look at
> > any compiler warnings. look at bug tickets. look for bugs. test. run make
> > check... repeat until we are in "good shape". :) a release means asking
> > people to do this (and EXPECTING them to).
>
> I think we can cut off some time if more people look at it. Let's try
> this out.
>
> 2016-08-11 Merge window for 1.19 opens
> 2017-02-09 Merge window is over.
> * Only bug fixes from this point
> * Alpha release tarball
> * One month stabilization phase starts
> 2017-02-13 Beta1 release tarball
> * Only critical fixes from this point
> 2017-02-20 Beta2 release tarball
> 2017-02-27 EFL 1.19 is out
i'm not too concerned on how many beta's or alphas or when exactly.. but
multiple should come out... just the total time i do agree on. and of course
if bug tickets/reality would bite and force us to delay - that's life. :) a
qualitative decision to be made at the time
> I removed one week by leaving out beta3. This is doable if the bug
> tickets and code get enough attention from more people. I will cut the
> alpha tarball today and will also try to get the first API/ABI report
> out. I would love to see everybody having a look at it, at least for the
> areas they worked on a added new APIs.
>
> I realize that the alpha today will caught some people with their pants
> down for some features they wanted to push. Talk to me in this case. I'm
> willing to let some more things in when they are explained to me. This
> will stop after beta1 though (Monday).
actually it got me to rush some fixes and so on with env var safety fixes... :)
> regards
> Stefan Schmidt
>
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) ras...@rasterman.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
