From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Jochen Kuepper Cc: egcs@cygnus.com Subject: Re: Date: Tue, 10 Feb 1998 10:30:00 -0000 Message-id: <15368.887135389@hurl.cygnus.com> References: <9802101122.AA29122@bacchus.pc1.uni-duesseldorf.de> X-SW-Source: 1998-02/msg00440.html In message < 9802101122.AA29122@bacchus.pc1.uni-duesseldorf.de >you write: > No, but following the mailing lists, there are coming in bug reports and > patches for fixes/enhancements of egcs-1.0.1 and of the current egcs > snapshots/cvs tree mixed altogether. Yup. > I was thinking it would be nice to have an archive of patches that can be > apllied to the last egcs-release, separated from all the patches that can > only be applied to the snapshots. Ah yes. Did you read the initial message about 1.0.2? It had this line: Right now these are only available on the cvs server; I'll bundle them up for ftp after I take care of a few more critical fixes. Which to be more explicit means we'll be providing (via ftp) patches folks can use to turn 1.0.1 into pre-release versions of 1.0.2. This is also how we handle the 1.0.1 release (look in the snapshots/1.0.1-prerelease dir). > I know that for you development guys the snapshots are more important to > move forward, but shouldn't we make the releases as 'bugfree' as possible. It's a nice goal, but at some point you have to say "critical fixes only", else we'd have to pull in most of the development tree, which unstabilizes things... That's why we don't try to fix every bug in minor releases... It is a tough decision to make, but necessary. > Or is all this even possible by just checking out the release tree from the > cvs-sources regularly ? Yes -- if you update your release tree via cvs you'll get whatever patches we've applied to to the release tree. That's precisely why we install the changes in the release branch -- so folks can get them them at any time. jeff