From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5147 invoked from network); 6 Jun 2001 09:40:04 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Jun 2001 09:40:04 -0000 Received: (qmail 10176 invoked by alias); 6 Jun 2001 09:39:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14737 Received: (qmail 10157 invoked from network); 6 Jun 2001 09:39:38 -0000 Message-ID: To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Patch/integration policy In-reply-to: ""Andrej Borsenkow""'s message of "Wed, 06 Jun 2001 11:07:50 +0400." <001801c0ee57$65d8db10$21c9ca95@mow.siemens.ru> Date: Wed, 06 Jun 2001 10:39:21 +0100 From: Peter Stephenson "Andrej Borsenkow" wrote: > Now with forked CVS we have to decide > > - how patches are posted > - how patches are integrated. > > Posting - should patches be posted for both stable and development? We've done this before. They only need posting separately at all if they are designed for both versions and the same patch doesn't apply to both. Bart tended to submit altered versions for 3.0 where necessary, but we didn't have the archive then. I imagine people using 4.0 won't need up-to-the minute patches posted here unless they refer to a particular problem which has turned off. So we probably won't usually need to post 4.0 patches. > Integration - are patch authors responsible for applying them to both > branches? Or we designate some person(s) who will maintain stable version > and integrate patches fron HEAD while other will continue in HEAD as before? Preferably the original author can commit it to both branches if that's necessary, at least until the rate of fixes dies down. -- Peter Stephenson Software Engineer CSR Ltd., Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070 ********************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. **********************************************************************