On Mon, Nov 22, 2004 at 06:45:39PM -0500, Albert Cahalan wrote: > So, this is including changes that are not user-visible? > You'll filter those out for the users?
I'll filter them out for announcements. But even things like the 'static' cleanup you did is worth mentioning in the changelog. Lots of users are also developers, or at least folks who'll be compiling from source. :^) > How is the docs/CHANGES.txt file different from a copy of > the CVS log data? (important, because there are ways to > dump out the CVS log data if that is all you need) Well, if there are CVS commits like this: * Added beige * Added tan * Changed lime to lemon * Changed lemon to neon green The CHANGES.txt would, by the time we actually release, look something like this: * Added some new colors (beige, tan) * Changed Lime to Neon Green No need to put EVERY bit of minutia<sp?> into the logfile. I do the same at work. I change something, and when I decide to commit, I'll note what I've changed. At the end of the day, or at some reasonable 'stop and test' point, I'll send off a build to my boss with only bullet points about what has changed. None of the "changed this to that", "but then changed that back to this" that might actually be in the CVS logs. Now, this is just the way _I_ do it. I'm not exactly 'trained' in the ways of using CVS. I think what I do is pretty reasonable, though, so little reason to change it. -bill! [EMAIL PROTECTED] New Breed Software http://www.newbreedsoftware.com/ Tux Paint 0.9.14 is out! _______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
