On Wed, Mar 20, 2002 at 04:01:18PM -0600, William Harold Newman wrote:
> On Wed, Mar 20, 2002 at 07:32:17PM +0000, Christophe Rhodes wrote:
> > On a related subject (which Bill's already alluded to), how are we to
> > manage editing top-level files such as BUGS, NEWS, TODO, and so on?
> > I would suggest, if Bill's OK with this, that we say that we (Dan and
> > I, and other such types as may spring into being in the future) just
> > don't touch those files, but send prospective text / diffs through
> > sbcl-devel, and let Bill merge them at his leisure (since they're
> > unlikely to be terribly urgent changes :-)
> > Does that make sense?
> It makes sense to me. If someday one or more breaks down, e.g. because
> of increased activity, we can find some other way of linearizing them,
> or make a real bug database like many projects do, but right now this
> should work fine.
Thinking about it some more, I'll add that other developers writing
into NEWS would be fine. NEWS is a rough draft until a release
happens. When I remember, I put reminders in there as I make
NEWSworthy changes. If other committers do this, even with very
telegraphic placeholder entries, e.g.
-- CSR -- SPARC port dynamically linkable now (0.7.1.46)
[more *DEFAULT-PATHNAME-DEFAULTS* fixes, esp. in OPEN -- DB]
it'll probably be helpful. It's not vital, since at release time I try
to review the ChangeLog for NEWSworthy changes. But if it does occur
to you at checkin time to flag a suitable entry in NEWS, it'll help
keep me from overlooking something that should be advertised.
William Harold Newman <william.newman@...>
"Now it's a couple of guys sitting in a living room with laptops. (And
jeans turn out not to be the last word in informality.)"
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C