Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <04d101c189d7$d0b4fa60$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <20011220095436 DOT A19634 AT cygbert DOT vinschen DOT de> <010201c18938$1c454480$0200a8c0 AT lifelesswks> <20011220105200 DOT I21898 AT cygbert DOT vinschen DOT de> <014601c1893c$2e969c70$0200a8c0 AT lifelesswks> <20011220110846 DOT K21898 AT cygbert DOT vinschen DOT de> <3C21DBCF DOT FE53C544 AT yahoo DOT com> <20011220190917 DOT GA2946 AT redhat DOT com> Subject: Re: Units Date: Fri, 21 Dec 2001 15:27:33 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 21 Dec 2001 04:28:05.0239 (UTC) FILETIME=[E265F070:01C189D7] ----- Original Message ----- From: "Christopher Faylor" > I don't see how that applies to the first release of a new package. I'd call it pretty basic risk management. If the package doesn't cause any havoc, then put it in current really quickly. I'm just nervous with the concept that any new package go directly into curr. remember that setup has prev/curr/test re-established and functional ( I still need feedback on whether the behaviour is intuitive, and to update upset to create prev and test automatically). Anyway, at the end of the day, this ain't my problem. Put stuff directly into curr. Good luck. Rob