Bruce Dubbs wrote: > > If you are referring to the latest comment by Ag in the Changelog, then > I can agree with your policy there too. We might just want to place a > link to the ticket in the changelog.
In the discussion on a blog entry on maintenance programming recently on Techrepublic, I made a comment about changelog entries. "The main one that helps track the code is the changelog. if it is more than just a fixed bug #x by $user on $date log. While bugtracking like bugzilla can be used to search for closed bugs, a description of the bug in the changelog saves time." Naturally, TRAC could be substituted for bugzilla in this context, the idea remains the same, keeping those actively working on the project as fully informed of the current state as possible should be detailed into the project specifications. While the LFS projects aren't programming, as in writing new applications, the project steps are the same, development, maintainence, bug fixing .. etc. The blog entry: http://blogs.techrepublic.com.com/programming-and-development/?p=610 Jaqui -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
