On 09/12/11 03:33, David Seikel wrote: > All the information should still stay with the source code. Making > people chase info all over the web wont help.
Copy the blog into the NEWS file then, making the developers copy paste all over the place isn't nice either. Furthermore, you gotta ask yourself about the habits of your users anyawy... > > If there should be separate files, then their goals should be > different. We already have commit messages, don't think that is going > away any time soon. That covers the nitty gritty details of what > changes, in a form that is suitable for developers. Then there is the > NEWS file, which really should be a summary of the major changes for > every one to look at. > > The changelog could be somewhere between the two. Though on some > projects, the changelog is just the commit messages automatically > derived from the source repo by some script or such. In which case > it's just redundant information, but it's in the source files (as > opposed to being only in the repo database) so that's important to, but > a script could do that. > > NEWS and changelog probably should be in binary releases to. For the > same reason, so people don't have to hunt down tweets or blogs or > whatever, it's all there in front of them. But the quest is, should we update them all the time, or just generate them from doxygen + commit logs when we release? I'm sick and tired with updating manually... -- Tom. ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
