On Thu, Oct 20, 2011 at 5:35 PM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Thu, 20 Oct 2011 15:47:08 +0200 Cedric BAIL <cedric.b...@free.fr> said: >> Yeah, another release cycle ! >> >> On Thu, Oct 20, 2011 at 8:51 AM, Carsten Haitzler <ras...@rasterman.com> >> wrote: >> > Hey guys. time to talk of our next release cycle. this meant 1.1 of most >> > efl >> > libs (and 1.5 for eet). this means we have lots of bug fixes and new >> > features here. i'm currently talking about: >> > >> > eina >> > evas >> > ecore >> > embryo >> > edje >> > efreet >> > e_dbus >> > eeze >> >> My latest change are fine in ecore and evas. I will postpone adding >> cache to Edje for after the release then. >> >> > now coming AFTER this we want elementary to go 1.0 - so this is the last >> > change we have to "break api's" in elementary. >> > >> > e17 itself is an app so api is "not relevant" here, but we also want to >> > work >> > full steam ahead on e17 release too. >> > >> > what i am proposing is that everyone finish their "pending work" for >> > everything above in the first list and get all pending changes to elm >> > upstream asap as well. i want to call a "2 week merge window" for core efl >> > (above) and then 2 weeks of bug fixing, then release. merge window starts >> > next monday (24th of october). that means from the 7th to the 20th no new >> > features can be added to trunk, only bug fixes. >> > >> > i am opening the floor to anyone who thinks other libraries in svn should >> > also get the 1.0 treatment too - ethumb? epdf? emotion? >> >> I think that for both ethumb and emotion, it's a little bit to early, >> but we could have a goal to release them at the same time that we >> release Elementary. I would also like to add Eio. I don't know about >> epdf. > > ok. that seems reasonable. > >> > some notes: eina will not have any eina-object model enabled for 1.1. evas >> > will have all the evas-gl stuff disabled in build and install for 1.1 as >> > its not stable yet. any more notes people have to throw in? >> >> I have sitting on my disk an half done ecore_thread_loop_run, who >> basically provide a main loop but from another thread. It's a usefull >> addition to ecore thread API, I just wonder if I need to push it for >> 1.1 or wait for 1.2. > > 1.2
Ok. >> In the mean time of this 1.1 release, I would like to prepare a 1.0.2 >> that would be the latest update of the 1.0.x branch. If people could >> try to at least check that the ChangeLog of 1.1 branch is ok so I >> could spot easily the bug fixes in it. That would be nice ! > > i don;'t see that that is useful - if we have 2 weeks merge, 2 weeks debug - > when will we do 1.0.2? lets just do 1.1(1.5). Last time it tooks me 3 days to do it. I hope that due to the amount of new code and divergence many fix will not be relevant to 1.0.x branch. So I hope to do it in 2 days after we are done with 1.1. -- Cedric BAIL ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Ciosco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
