Hello. On 13.07.2018 10:23, Mike Blumenkrantz wrote: > Sure, I think the obvious area for automation would be in the release > notes. Moving this to use the Enlightenment release method seems like it > would save a huge amount of time here (ie. just running a script for ticket > refs and using git shortlog). If we start using the right project tags for > 'feature' patches then these can easily be found for release highlight > items, meaning that this part of doing a release is effectively removed > from the 'active' time requirement.
Besides a list generated phab or git log (which I think is fine for point releases) for major ones we should release notes which explain concepts and changes on a higher level with context added the basic commits to not offer. This is why I often poked folks to give me a short blurb of text on a feature they worked on during a given release. 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
