cvs commit: src/contrib/dhcp-3.0 LICENSE README README.DELETED README.DRAGONFLY RELNOTES src/contrib/dhcp-3.0/client clparse.c dhclient-script.8 dhclient.8 dhclient.c dhclient.conf dhclient.conf.5 dhclient.leases.5 src/contrib/dhcp-3.0/client/scripts ...

Sascha Wildner saw at
Sat Aug 30 18:14:44 PDT 2008

Justin C. Sherrill schrieb:
Should we stick with UPDATING, or how about a CHANGELOG?  "UPDATING"
describes how to update, which is fine, but I'd prefer a separate file
that lists changes to the system that may have no effect on the updating
process.  (in this case, it does, but that's not always the case.)
This would be our 
release pages. I see no problem with starting (committing) one for 2.2 
now, adding to it over time and linking it when the release has come.

UPDATING would only be used for things which have an effect on running 
systems between upgrades (such as in this case).

The dhclient replacement would go into the first document and the dhcpd 
removal into both (maybe with a note in the first that dhcpd will be 
gone on upgraded systems but not on freshly installed ones).

Dunno what the others think, somebody will have to do the work, after 
all. :)



More information about the Commits mailing list