On Fri, 27 Aug 2010, Cedric BAIL wrote:
> Hi, > > So we are in Alpha now. This raised a question, how and when do we > fill ChangeLog ? > Do we start to fill them now or after the first release ? > What do we put in them ? For Eet, I add entry in the ChangeLog > every time I add a feature or fix a bug present in an older release. I > don't add entry for indenting, typo or bug introduced during the > development cycle. As the ChangeLog is targeting distro and end user > that don't really follow our svn commit, I think that Eet ChangeLog is > relevant to them without too much noise. Maybe I am wrong, so I want > to know your opinion guys about this question, so that we have a clear > policy in the futur. I have already mentioned that: there is a very good tool named moap [1] which can be used to commit and update ChangeLog very easily. I used it for the projects I'm the owner. Here are the steps i do when I commit: 1) do the change in the svn repo 2) moap cl prep 3) modify the ChangeLog 4) moap cl ci This way, we will have a consistent ChangeLog. This tool can even do more interesting things (just read the description). Vincent [1] https://thomas.apestaart.org/moap/trac/ ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
