What I said in IRC: In my POV, we should ditch the NEWS file entirely and change the way we handle the Changelog.
Honestly, NEWS file was for the time before people tweeted, blogged, and what not. It's not really relevant anymore, not in the way we use it anyway. Changelog: we should add one entry per release that says "We added new API and deprecated old API. Check doxygen for details". As we use the @deprecated and @since doxygen flags anyway... As for other types of changelog entries: we should keep doing those (important notices). For example, we should write changelog entries when we add completely new and needed features, like group inheritance in edje, or possibly a new and cool elm widget. In conclusion, emphasize what we want to emphasize. I hate the fact that I have to copy almost all of my commit logs to Changelog (format and rephrase it a bit) and NEWS file (format and rephrase it a lot). I feel like an idiot, and it drives me nuts. I really don't see the purpose of updating those files... Vincent: I have nothing but respect to you and as I said in IRC I'm probably your #1 supporter on most topics, but I don't think doing so much work for getting something we can get otherwise is worth it. -- 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
