Hello, On Wed, Feb 19, 2014 at 10:45 PM, Stefan Schmidt <ste...@datenfreihafen.org> wrote: > Its time for release busy work. For the 1.9 cycle we decided to ditch > ChangeLog and NEWS updates during the development and fill it up at > the end. Thats what I'm starting right now. > > For evas generic loaders and emotion generic players I updated the > NEWS file to the current beta1 state and will update it when more > changes come in. I also added notices to the ChngeLog file that it is > out of date and that people should use git log for fine grained commit > messages. The NEWS file will stay for a high level overview of what > has changed in last release. > > Doing this for the above mentioned projects was plain and easy. If you > want you can have a look here and give Feedback. > http://git.enlightenment.org/core/emotion_generic_players.git/commit/?id=861b389b5e4dc0f314e157c4e6ba6c58529be4ba > http://git.enlightenment.org/core/evas_generic_loaders.git/commit/?id=a9e051d30df4f0c00bbdd31dd5cf04aee1fd6f1c > > It boils down to looking through the commit list, ignoring all trivial > changes, putting the others into the correct category and maybe > massage some messages. It was plain and easy for these two only > because they had so little commits. Commits between 1.8.0 and > 1.9.0-beta1: > > (Git hint for number of commits between two tags: > git rev-list v1.8.0..v1.9.0-beta1 --count) > > Emotion Generic Players: 12 > Evas Generic Loaders: 10 > Elementary: 532 > EFL: 725 > > The pure numbers show that it will be way more difficult for me but > that my problem. You problem might be that your fancy new feature > might not get the attention it deserves. Here is you chance to fix > this. If you or your team added a nice new features or improved > something or fix a serious bug you might want to write some lines > about it here: > https://phab.enlightenment.org/w/efl_and_elementary_1_9_release_announcement/ > > Bonus points for Stanluk and his team as they already did it! > > If I find good commit messages describing a bigger feature I will also > try to put them in the release notes. If your commits messages suck > your contribution might be only one line in the NEWS file instead a > nice reading in the release announcement. Your chance to fix this. :) > > Please also take some time to proof read the release notes wiki page > as well as the NEWS files once I have them ready and pushed. Its easy > to have mistakes comming in here.
I think we are also missing the update of the AUTHORS file. I think it should be pretty easy to update now that we use git, no ? -- Cedric BAIL ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
