Hi all, my two cents:
1) Rolling is fine but in longterm it can cause anoyances to users and developers (changing things too frequently, api breakouts in minor releases, etc) 2) I suggest stable branch 17.x for fixes, and minor enhancements (like new view to efm, new function for possible keybinding, etc) 3) Develop most things in new branch 18.0 and only backport sometimes to 17.x (like: I fix some memleak and fix it in 18 then test it and see the leak is also in 17, so backport) 4) Better testing can be done with release upgrade, many things can happen like config format update. 5) User experience may suffer from more often changes in using style and rules. 6) And finally, from marketing point of view you will have more news in new relase :) So it seems like more cents. Robert. On Sat, 22 Dec 2012 15:47:16 +0100 Bruno <[email protected]> wrote: > On Sat, 22 December 2012 Gustavo Sverzut Barbieri > <[email protected]> wrote: > > On Saturday, December 22, 2012, Thanatermesis wrote: > > > > > I would like to open this thread for know/discuss/talk about the > > > plans of the future status of E17 (not E18), because this is a > > > very waited and wanted release, we need to provide a good example > > > of quality result. > > > > > > For example, like in any other software, what are the plans for > > > update the existing release with more bugs fixed ? and in the > > > same way, the new commits to e17, like improvings or minor fixes > > > can be good to have it also to the actual release and not only in > > > the svn, how we can manage that ? > > > > > > This is the first commit after the release: > > > > > > http://git.enlightenment.fr/cgit.cgi/svn/e.git/commit/?id=42bdecd16029b779bb1d52febbb3fa502d67ed2a > > > and it looks like a fix, how we can work in "2 branches mode" in > > > order to be able to commit for dev, for stable, or for both ? > > > > > > I don't know if anything is planned, talked, discussed, maybe > > > there's people working on a new structure in the server based on > > > git for the future development ? so... comments ? thoughts ? > > > ideas ? > > > > > > I'd say we must make E17 a rolling release and never ever assign so > > much expectation to a number or release as we did. We should go > > like chrome or Firefox and release often, a single branch. > > > > As for the actual number we can go 18 or 17.1, that's mostly > > irrelevant. > > Maybe go for 17.x and switch to 18.x once a bigger feature gets in > (like support for Wayland) > > Bruno > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add > services Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
