RE: New version, release candidate for 1.4
Rob Hagopian <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <F4A736AE282FD511BC28009027CC7C59065B11DC@gopostal> |
I haven't because I'm a bit concerned about having to change all the clients again... The instrs below seem straightforward except that I don't have build boxes for all the redhat versions... Is there a good way to seamlessly upgrade to 1.3.90 - that is, no change in server cert or port numbers? Please feel free to tell me to RTFM since I haven't :-) -Rob -----Original Message----- From: Hunter Matthews To: Current Server Mailing List Sent: 9/16/2002 5:50 PM Subject: Re: [Current-server] New version, release candidate for 1.4 Is this safe to put up on freshmeat? Anyone looked at it yet? On Sun, 2002-09-15 at 17:57, Hunter Matthews wrote: > Ok folks, here it is. > > 1.4 > > Just kidding. Its 1.3.90, however, that big 90 means its a release > candidate. I've got it running as my production server here in biology, > and quick, basic testing indicates its a go. There was a last minute > quibble with update, but thats taken care of. > > Big changes from 1.3.11? Bug fixes. These covered the world, but the > important parts were that the database changed again (subtly) and the > config file changed again. (Not so subtly). > > Please please test this one. It works here, but thats been a poor test > many times. If you have a dirty tree, multiple versions or WHATEVER, > please - see if Current with a 2.7 client gives you what you expect. > > The RELEASE-NOTES on the ftp site include all the things you should be > concerned about (it says 1.3.12, but I didn't want to re-roll the tar > ball). For deeper knowledge, the CHANGELOG will show you what John and I > have been up to. > > If no one shows any bugs in a few days (thursday maybe?), then this will > be 1.4. A _really_ scalable server for up2date. > > I'm working on a transition guide (simple text file) for those who want > ot migrate a bunch of hosts from 1.0.5 to 1.4. Basically, you just need > to reroll your client packages, and run your apache process on 80 & > 8080,443 & 8081 for a night or two to let everything upgrade itself. > > Please let me know if other doc improvements are needed. > > -- > Hunter Matthews Unix / Network Administrator > Office: BioScience 145/244 Duke Univ. Biology Department > Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 > Never take candy from strangers. Especially on the internet. > > _______________________________________________ > Current-server mailing list > [email protected] > http://lists.dulug.duke.edu/mailman/listinfo/current-server > > -- Hunter Matthews Unix / Network Administrator Office: BioScience 145/244 Duke Univ. Biology Department Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 Never take candy from strangers. Especially on the internet.