From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9504 invoked by alias); 9 Apr 2008 15:04:50 -0000 Received: (qmail 9490 invoked by uid 22791); 9 Apr 2008 15:04:49 -0000 X-Spam-Check-By: sourceware.org Received: from out4.smtp.messagingengine.com (HELO out4.smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 Apr 2008 15:04:32 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 4558CEB69F for ; Wed, 9 Apr 2008 11:04:30 -0400 (EDT) Received: from web6.messagingengine.com ([10.202.2.215]) by compute1.internal (MEProxy); Wed, 09 Apr 2008 11:04:30 -0400 Received: by web6.messagingengine.com (Postfix, from userid 99) id 1B1A85CFBD; Wed, 9 Apr 2008 11:04:30 -0400 (EDT) Message-Id: <1207753470.10517.1246955047@webmail.messagingengine.com> From: "Charles Wilson" To: cygwin-apps@cygwin.com Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Date: Wed, 09 Apr 2008 15:04:00 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00117.txt.bz2 On Wed, 9 Apr 2008 10:31:39 -0400, Christopher Faylor wrote: >On Wed, Apr 09, 2008 at 06:09:46AM -0700, Brian Dessent wrote: >>Corinna Vinschen wrote: >>>My favorite would be release-2. It has nothing to do with the DLL >> >>Sounds fine to me as well. > >It's ok. Works for me. One question: the old plan was, as outlined by Brian, that we would eventually have: release_legacy <<-- renamed from existing 'release' directory release <<-- new 1.7 stuff, once it is "gold". (and somewhere we would have a temp release-1.7/-2008/whatever thing, which would get renamed to 'release') Is the new plan: release <<-- stays exactly as is, forever and ever. (OK, maybe some pkg updates...) release-2 <<-- "temp" with custom setup.exe during development, but eventually becomes "actual" when (a) we decide that 1.7 and associated pkgs are ready to go (b) and we release a "new" setup.exe with the special "are you Win9x"-->release (NOT release_legacy), else -->release-2 That is, no directory renaming at all (which would make the mirrors happy) -- we "activate" by releasing a new setup? ? -- Chuck