Hello. On Tue, 2014-02-25 at 10:37, Martin Jansa wrote: > On Tue, Feb 25, 2014 at 09:57:49AM +0100, Stefan Schmidt wrote: > > Hello. > > > > On Tue, 2014-02-25 at 09:17, Adrien Nader wrote: > > > > > > I don't expect, nor intend, to delay the release of 1.9. I only want to > > > record my belief as a packager that the release cycles are too short and > > > that the stabilization phases are _way_ too short (let's face it, no > > > packager does continuous integration/packaging). > > > > Is that a guts feeling or do you have concrete examples or problems > > you see with the curent state of 1.9? > > > > You are the first packager that complains about this so far. What > > distro are you packging for? What is the release cycle of this distro? > > > > I personally think that three months are not that bad. I agree on the > > short stabilizatiopn phase at the end tho. For 1.10 we will shift it a > > bit to have three weeks at the end. > > > > The problem with stabilization phases in such an active project is how > > long can you bind the focus of the developers on stibilization. I > > believe it would not help if we make a 8 weeks stabilization phase > > while all the devs are working on new features already and nobody is > > looking into the bugs. > > > > It would be great and pefect if we can release without any bugs but > > reality tells us that is not the case. We try to deal withg this by > > providing stable updates for all the fixes we do after the release. I > > had the feeling that worked pretty well for 1.8 already but I'm biased > > so I'm happy to hear about concrete problems. > > From my perspective (as meta-efl maintainer) it's OK as long as you > aren't expecting to do zero-day updates for major versions (which > doesn't make much sense anyway).
Not expecting it. :) I realise it takes soem zime depending on priorities, distro type, etc. > I would prefer to stay closer with upstream versions, but especially > with upgrade from 1.7 to 1.8 there was quite a lot of work from > packaging side, so even when I started with some experiments in my spare > time around 1.8 beta I was confident enough to push it to > meta-efl/master only couple days ago with 1.8.5.. 1.9 should be way easier from a packaging view. No big merge, etc. There will be some caveats tho. First of all efl's new dep on gstreamer 1.x and luajit (you can switch to luo old to keep the old dep if needed) Another thign packagers will notice is the very long I-know-what-I-do configure flag when using not standard configure options. Besides that I hope the update will work well. regards Stefan Schmidt
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
