On Fri, 13 Jul 2018 09:46:14 -0400 Stefan Schmidt <[email protected]> said:
> Hello. > > On 13.07.2018 03:20, Jonathan Aquilina wrote: > > Some food for thought wouldn’t it be better to do more frequent point > > releases? > > If you look at the releases before 1.20 you will see that we did quite a > few. I aimed for a one stable update per months schedule. Sometimes > being faster or slower depending on how critical the backports have been. > > With 1.20 and now 1.21 the schedules are all messed up. I would agree > that coming back to more frequent stable updates make sense. doing less in a release will help. Less in terms of amount of new/changed code going in per release, and even streamlining the process. TBH the right thing would be for it to be scripts that are in the efl repo itself like: ./rel/alpha.sh ./rel/beta.sh ./rel/final.sh and alpha.beta take a parameter (2, 3, 4, 5) if multiple are needed. scripts do a make distcheck and makes sure things pass. It generates all needed files (changelog etc.), appropriately update README and any other files so correct versions are there, upload tarball, add a news article to the www content git repo, spew out the content of a mail to copy & paste into a mail client(that could be automated too ...) etc. ... Not everything can be automated - like manual addition of docs like new configure options or deprecated ones, new dependencies etc. ... these should have been fixed already at the time they were changed, but double-checking here is manual. Perhaps the scripts can echo out a list of files to review the content of? But in the end there should be a simple "press this button" to release. The rest is simply QA - nuking bugs, testing, etc. which can't be really automated. > regards > Stefan Schmidt > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - [email protected] ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
