On Sat, Sep 22, 2012 at 6:11 PM, Tom Hacohen <t...@stosb.com> wrote: > On 23/09/12 00:10, Gustavo Sverzut Barbieri wrote: >> On Sat, Sep 22, 2012 at 5:46 PM, Tom Hacohen <t...@stosb.com> wrote: >>> On 22/09/12 17:05, Gustavo Sverzut Barbieri wrote: >>>> Isn't better to wait merge, release, then add eo? >>> >>> Hm... what? I don't quite get it. We just released, we waited until >>> after the release just for that, why not upstream our changes that add Eo? >> >> we wouldn't know if the breakage is due merge or eo. >> >> IMO: release merge, add eo and release again >> >> > > It'll break the layout of the libraries and thus will make merging very > annoying. Also, breakages should be different, i.e the change of layout > shouldn't cause any runtime issues.
it shouldn't, but it always do :-( we don't need major releases, but at least minor we should -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
