RE: [PHP-DEV] We Want Quality

One solution used in other Open Source development projects is that you lay down a CVS tag on all files at the point code freeze happens. Then others can continue to develop at will. Accepted fixes for the release have the release tag moved forward to include the committed file. This is easier to do w/ CVS branches, but can be done without that. - Troy > -----Original Message----- > From: Sascha Schumann [mailto:sascha@schumann.cx] > Sent: Thursday, June 29, 2000 2:22 PM > To: Zeev Suraski > Cc: php-dev@lists.php.net > Subject: Re: [PHP-DEV] We Want Quality > > > > Well then, don't be surprised if what you say ends up > sounding very > > different than what you meant, if you omit 'needless' > words. The words > > you probably refer to as needless are the words that > usually set the > > atmosphere of your statements, and even though they may > not affect what > > you're actually saying, they make all the difference in the world. > > Following up: A discussion of communication models, > perception and intention. > > Well, sure. If you want to read these rules as being > oppressive and inpolite, you can do so, because they are > context free. Many words do not transfer any information. In > easily memorizable rules, such words are omitted. > > > > Extending the release process to reach a larger > audience will > > > help. Reviving the php-beta list where people commit to test > > > basic functionality on their platform is a good start. > > > > Yes, that would be a good idea. php-beta@ was simply > never quite a > > success story, I think it had about 15 people at its > peak. We can try to > > advertise it more though. > > Agreed. > > > > I don't see it that way. The contributors are interested in > > > improving PHP, not in destabilizing it. Closing the CVS tree > > > for a week will not stop them from developing new stuff. It > > > will only delay inclusion to the official PHP CVS tree. > > > > Considering branches don't work too nicely with CVS, > halting development > > for long periods of time (1-2 weeks) would, de-facto, > hurt the development > > of PHP. We should definitely implement a feature freeze, > but a code > > freeze is simply not possible IMO. > > You are assuming > > Developing equals being able to commit. > > While it makes collaborating with other people harder > (assuming they have no tools like email, diff, patch), I > think it is an acceptable trade-off. > > - Sascha > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: > php-list-admin@lists.php.net >