Hello. On Mon, 2013-09-23 at 22:01, Jorge Luis Zapata Muga wrote: > On Mon, Sep 23, 2013 at 9:56 PM, Eduardo Lima (Etrunko) > <ebl...@gmail.com>wrote: > > > Hi Turran, > > > > Since these patches are adding new API, shoudn't they be pushed to the > > 1.8 tree? We are holding ourselves from pushing any new features the > > 1.7 series, and should drop the support for them as soon as the new > > version is released (which I was told it should still happen this > > year). > > > > Hi, > I already asked about this in another thread (Legacy libraries and efl > repos) but I had no answer :-/ > Don't know what is the process here ... at the end this patches can go to > efl's tree one too
I would not go as far as saying we have a process for this. :) But as a rule of thumb: 1) All patches (fixes, features, etc) should go into master (for 1.8) first. Only exception would be fixes that are only valid for the 1.7.x branch. Feature on the other hand should never have any exception. 2) Once they are in master and don't cause trouble fixes can be backported to the legacy branches. (Its a bit annoying right now as we can't cherry-pick due to the efl merge but that will be better for the 1.8 and 1.9 cycle) Backports of features, which is want you want here, is a bit more unclear. Personally I feel not really comfortable with still backporting features into the 1.7 cycle but people still do it. And have plenty of good arguments to do so. I guess the best way for you would be to put your changes into master, wait for people to complain, fix up things if needed and once the storm tuned down backport it to eina legacy. :) regards Stefan Schmidt ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
