On Fri, 4 Feb 2011 10:26:59 -0500 Mike Blumenkrantz <[email protected]> said:
> I don't think it's the best option, but we're a community so I'll go with > whatever the majority (aka raster) decides. hahahahahah! but seriously - i went over this. the POINT of the changelog is to document the changes made for the PURPOSE of providing a list/summary of what has changed since the last release they used. so fixing a typo in a comment doesnt deserve a changelog. if you work on something over several commits or days - the changelog at the END is needed. if you put it in first then are busy fixing the bugs or issues - no need for more changelogs. the first one covers the new code/feature anyway. there is no point in the changelog duplicating svn commit logs. just rememebr that when evas 1.1 or eina 1.1 etc. are released, the changelog will be used on the website as the list of what has been changed, added or improved so people know what to expect when they upgrade to it. this applies for released 1.0 things. to those still in 0.x... it doesn't. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
