Login | Register
My pages Projects Community openCollabNet

Discussions > cvs > CVS update [release-1_4_x-branch]: /current

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Discussion topic

Back to topic list

CVS update [release-1_4_x-branch]: /current

Reply

Author hunterm
Full name Hunter Matthews
Date 2003-06-11 15:44:50 PDT
Message Tag: release-1_4_x-branch
User: hunterm
Date: 03/06/11 15:44:50

Modified
 /current
  Makefile, README, RELEASE-NOTES

Log
 Updated CHANGELOG, RELEASE-NOTES, and README for 1.4.4 release.

File Changes:

Directory: /current/
====================

File [changed]: Makefile
Url: http://current.tigri​s.org/source/browse/​current/Makefile.dif​f?r1=1.2.4.5&r2=​1.2.4.6
Delta lines: +1 -1
-------------------
--- Makefile 15 Feb 2003 20:49:06 -0000 1.2.4.5
+++ Makefile 11 Jun 2003 22:44:50 -0000 1.2.4.6
@@ -7,7 +7,7 @@
 
 # Things that change from build to build
 PROJECT = current
-VERSION = 1.4.3
+VERSION = 1.4.4
 PYTHON_BIN = /usr/bin/python
 PREFIX = /usr
 INSTALL_ROOT =

File [changed]: README
Url: http://current.tigri​s.org/source/browse/​current/README.diff?​r1=1.1.4.4&r2=1.​1.4.5
Delta lines: +18 -14
---------------------
--- README 20 Feb 2003 20:55:54 -0000 1.1.4.4
+++ README 11 Jun 2003 22:44:50 -0000 1.1.4.5
@@ -14,8 +14,8 @@
 
 Basically, the functionality of 1.0 is enough to get a small network (20-30
 clients) updated with basic security patches. 1.4 is scalable enough to
-take this basic, anonymous only functionality to several hundred hosts
-(500 or so seems to be a good point)
+take this basic, anonymous only functionality to hundreds of hosts
+(500 or so seems to be a good point).
 
 There is a freshmeat entry and a website, mailing lists, cvs repository, etc
 at http://current.tigris.org. If you will be using current in a production
@@ -23,7 +23,7 @@
 you should definately join the annouce list.
 
 Comments to the mailing list please. Bug reports should contain enough
-detail to help me see what the problem is. Patches always cheerfully looked
+detail to help us see what the problem is. Patches always cheerfully looked
 at.
 
   NOTE: !WARNING! ACHTUNG- This server should be carefully tested and
@@ -36,12 +36,14 @@
     
     server itself:
         Please note that Current is only tested and claimed to work on
- RHL 7.2, 7.3, and 8.0. Your server should run all original Red
+ RHL 7.2, 7.3, 8.0 and 9. It is reported to work on the 2.1
+ enterprise releases. Your server should run all original Red
         Hat packages (and should itself be fully up to date with errata).
 
- The single exception is on a RHL 8.0 machine, you need a newer
- mod_python (3.0.1) to deal with bugs in that package. A suitable
- mod_python package and src package are provided.
+ The single exception is that on a RHL 8.0 server, you need a newer
+ mod_python (3.0.1 at least) to deal with bugs in that package. A
+ suitable mod_python package and src package are provided on the
+ web site.
     
     rhn_register:
         Current can handle rhn_register versions of 1.3.x through at least
@@ -55,9 +57,9 @@
         consumed by the up2date package itself.
         
     up2date:
- Working 2.7.x and 2.8.x for all simple cases (it works here).
- Versions prior to 2.7 will not be supported. 3.0.x mostly works,
- and will be improved in a future current release.
+ Current can handle up2date versions from 2.7.x up to 3.1.x for all
+ simple cases (it works here). Versions prior to 2.7 will not be
+ supported.
 
         Both the GUI and text interfaces are supported. (the gui has
         one extra call it can make, which is implemented in a limited way).
@@ -65,11 +67,12 @@
         Due to bugs in up2date itself, I HIGHLY recommend 2.7.63 or higher
         if you are using clients in the 2.7 range. 2.7.83 has proved stable
         for just about everyone - if you're sticking with 2.7.x for the time
- being, run 2.7.83. (There are two killers, and neither can be
- fixed well by the server).
+ being, run 2.7.83. (There are two serious bugs in earlier versions,
+ and neither can be fixed by the server).
 
     rhn_check / rhnsd:
- Not working. (rhnsd just calls rhn_check).
+ Not working. (rhnsd just calls rhn_check). The calls are stubbed
+ out in current v1.4.4, and should not produce an error.
 
     rhn-applet:
         Not working yet.
@@ -82,6 +85,7 @@
 
 Contributors:
 Ivan Martinez Bug fixes
+Scott Schmit Bug fixes
 Toby D. Reeves SQL work
 Barry K. Nathan Debugging help
 Sam Bingner Debugging help

File [changed]: RELEASE-NOTES
Url: http://current.tigri​s.org/source/browse/​current/RELEASE-NOTE​S.diff?r1=1.1.4.2​&r2=1.1.4.3
Delta lines: +20 -0
--------------------
--- RELEASE-NOTES 17 Feb 2003 19:52:00 -0000 1.1.4.2
+++ RELEASE-NOTES 11 Jun 2003 22:44:50 -0000 1.1.4.3
@@ -1,5 +1,25 @@
 These are the user visible changes in Current from release to release.
 
+v1.4.4
+- Current is now compatible with the new rpm API introduced in rpm v4.1,
+ so current should work on any _server_ from RHL 7.2 to 9.
+- Due to documentation building dependancies, it may only build on 7.3 or
+ later, but I know of no reason it won't work on 7.2 (or maybe 7.1...)
+- Current is now fully compatible with all client releases from 2.7 to
+ 3.1. Please report any trouble with this...
+- I _HIGHLY_ recommend you upgrade to the latest errata of up2date for
+ whatever release of Red Hat Linux you are running - several client bugs
+ can either cause system problems or cause current to behave in bizzare
+ fashions.
+- cadmin with no args now does something sane.
+- Improved some log messages. 1.5.x is where the major log cleanups are
+ going to occur.
+- Scott Schmit submited a bug patch for our error reporting. YAY SCOTT.
+ This should make diagnosing server problems much easier.
+- There are no config file, apache or database changes in this release.
+ Upgrades from 1.4.3 should be clean, and do NOT require a database
+ rebuild.
+
 v1.4.3
 - Current is now proudly hosted at current.tigris.org. If you are
   subscribed to the dulug mailing list, please move to the




--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: cvs-unsubscribe@curr​ent.tigris.org
For additional commands, e-mail: cvs-help at current dot tigris dot org

« Previous message in topic | 1 of 1 | Next message in topic »

Messages

Show all messages in topic

CVS update [release-1_4_x-branch]: /current hunterm Hunter Matthews 2003-06-11 15:44:50 PDT
Messages per page: