On Sun, Sep 23, 2012 at 6:13 AM, Gustavo Sverzut Barbieri <barbi...@profusion.mobi> wrote: > 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
I have been wondering about this subject for the weekend. Maybe we could do a packager preview or something like that. I don't like the idea of doing a 1.7.1 based on current trunk (1.7.1 should in my opinion only come from branch) and I don't really like the idea of doing a 1.8.0 so soon after 1.7. A packager preview would fit the biggest change we have done, force people to update their build script and seems reasonable. So it would a 1.8.0-preview or something like that. -- Cedric BAIL ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
