Re: New release manager needed.
From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-07-02 22:44:14 CEST
pll@lanminds.com writes:
> >>>>> On 2 Jul 2003, "Ben" == Ben Collins-Sussman wrote:
It's good that you can summarize each change in one line. Nice job!
But I think you need to clamp down your filter just a wee bit. It
It looks like you tried to create a bullet for each revision... or
A general note: there's no need to *force* a prefix to the front of
> User-visible changes:
Start with the most important stuff first... the stuff most incredibly
For example, I'd imagine that completely new commands ('svnadmin
> * changed - cvs2svn usage() Excessively long output.
As another poster said, "not interesting to the general public". :-)
> * fixed - copyright messages
Huh? Either not interesting, or not explanatory enough.
> * fixed - memory bug seen with svn switch
* fixed - 'svn switch' memory bug
> * fixed - parent-into-child copies provided they are not WC-to-WC. (r6348)
The "fixed -" prefix obfuscates the description. Try something
> * fixed - svn mkdir URL URL/subdir no longer dumps core (r6338)
* fixed - 'svn mkdir' coredump.
No need to describe the exact recipe, unless it's really interesting.
> * removed - bogus python package
Huh? Why was it bogus? Too little information.
> Developer-visible changes:
> * changed - paths array is now a constant (r6301)
These things aren't very interesting, even to developers. Screen them out.
> * fixed - copied subtree problem (r6365)
Huh? I read this and have no idea what you're talking about. I
* many cvs2svn.py changes:
Notice that we have subsections in earlier CHANGES entries.
> * new - XFail test (r6333)
Test for *what*? Don't make me look up the revision.
> * updated - vcproj generator now works (r6316)
Another "category" here. A zillion changes were made to the win32
> * poem - "Dinner is served" by cmpilato (r6313)
Funny. :-)
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.