Hi, On Wed, Sep 11, 2013 at 6:11 PM, Bertrand Jacquin <be...@meleeweb.net> wrote: > On 2013-09-11 17:03, Eduardo Lima (Etrunko) wrote: >> 2013/9/11 Bertrand Jacquin <be...@meleeweb.net>: >>> Hi, >>> >>> On 2013-09-11 00:36, Eduardo Lima (Etrunko) wrote: >>>> We now have tarballs up for testing in under the new pre-releases >>>> directory: >>>> >>>> http://download.enlightenment.org/pre-releases/efl-1.7.9/ >>>> http://download.enlightenment.org/pre-releases/enlightenment-0.17.5/ >>> >>> IMHO, it's bad to name tarball 'e_dbus-1.7.9.tar.bz2' (here for e_dbus >>> exemple). Think about google bot and other crawlers that will put in >>> the >>> first result 'e_dbus-1.7.9.tar.bz2' corresponding to the pre-release >>> directory, and this even when release will happenning, people will not >>> see pre-releases subdirectory at first. >>> >>> Also, it may lead to misunderstood from people that will already have >>> a >>> file named e_dbus-1.7.9.tar.bz2 in their directory. >>> >>> Naming them e_dbus-1.7.9_pre1.Tar.bz2 in preferable or anything else >>> that is not the final tarball name. >> >> It is already enough work to update configure.ac, ChangeLogs and NEWS >> for all 17 packages we ship, and I for myself am not doing it all over >> again only to remove a 'pre' tag. The idea is to move the tarballs to >> the release directory and remove the pre-release one whenever the >> packages are tested and good to go. > > This should not need any manual changes. You could for example add a > v1.7.9_pre1 tag on a commit, and then run a 'make dist' that does all > needed things for you. As almost all projects does.
I also think that it would be cool if we had that. But unfortunately I have to agree with Etrunko that it's a pain in the ass, at least the way that it is now, where EFL 1.7 is split across several packages. It's not "just make dist", but make dist on every package, at least twice (one for pre-release and another for the real release), adding/changing/removing the preN tag. And if we do that, would be even better to do it all correctly: update dependencies accordingly, NEWS, ChangeLog, etc, as Etrunko said. I don't think it's worth the effort for 1.7 yet, maybe we can do it after 1.8 release where it will be a lot easier (single tree for core efl, elementary and enlightenment). Just my 2 cents. -- Rafael Antognolli ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
