Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <00de01c10550$daffbc00$0300a8c0@ufo> From: "Trevor Forbes" To: "cygwin-developers" References: Subject: Re: vacation plans Date: Thu, 5 Jul 2001 22:18:55 +0930 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 I think you should just release the dll as a test release, it works fine for me but who knows..... As for setup, maybe just release it also as "test" package (no source) - "setup updating setup" ie not for beginners.... Regards Trevor ----- Original Message ----- From: "Robert Collins" To: Sent: Thursday, July 05, 2001 2:22 PM Subject: RE: vacation plans Bus. Bus! BUS! Seriously... I'd hold off on the .dll, but I see no reason not to release setup.exe. Theres ~ 3-4 folk now who understand whats happening in there, and if someone at redhat can cooperate if we need to put a new version up.... we should be able to hold the fort. Rob > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Thursday, July 05, 2001 2:45 PM > To: cygwin-developers AT cygwin DOT com > Subject: vacation plans > > > I'm going to be going on vacation on Saturday. So, I'm wondering if I > should release new versions of the DLL and setup.exe. > > I have mixed feelings about this since I probably won't be > reading email > much, if at all (if that is possible). > > I am somewhat reluctant to release the DLL because Corinna is > on vacation > now and may have some opinions about the DLL. > > I'm reluctant to release setup.exe because it has a lot of > new code in it > and people are certain to find some kind of show-stopping problem. > > However, maybe this would be a good test of the "What happens if cgf > gets hit by a bus" scenario. > > Any thoughts? > > cgf >