Date: Fri, 20 Feb 1998 23:20:00 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: grog@lemis.com (Greg Lehey) Cc: jkh@time.cdrom.com, jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: More breakage in -current as a result of header frobbing. Message-ID: <199802210420.XAA09121@dyson.iquest.net> In-Reply-To: <19980221143803.31160@freebie.lemis.com> from Greg Lehey at "Feb 21, 98 02:38:03 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lehey said: > > What I'm suggesting (finally!) is: > > Let's accept the fact that -CURRENT's stability fluctuates and try > to influence the rhythm. One possiblity might be to say: > > - The first weekend in each month is the correct time for commiting > big modifications that can potentially compromise stability for a > while to come. > > - Any Sunday is the correct time for commiting smaller modifications > that can potentially compromise stability for a few days. > > The advantage is that people can expect -CURRENT to be relatively > stable on a Friday, and particularly stable at the end of a month. > This is only a suggested implementation. I don't know how > inconvenient it might be. Another alternative is the "heads up" > approach--after a period of relative stability, somebody could say > "I'm going to commit some changes to the frobulator which > potentially impact stability. I'll do it tomorrow night unless I'm > shouted down". > > Clearly this needs discussion. Go for it. > I am not sure that I totally agree with *exactly* what you have said, but a certain "rhythm" would be a good idea. Sometimes when I commit changes, I am VERY concerned that I'll screw someone up. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802210420.XAA09121>