Re: 1.4.0 released

Ok, specifically to address the bugs found in 1.4, 1.4.1 has been
released.

What bugs? Two types:

1) internally generated Faults, which are normal recoverable errors,
were not reported back to the client sanely.
  This was due to alien influence. I have documents.

2) Error messages having to do with the clients sysid and sysid
authentication were reported as having to do with the "certificate".
Which was bogus - current itself knows nothing of SSL anymore.

These have been fixed. There is no need to update/recreate your
databases: for once, we'll have a compatible bug fixing point release.

Yes, as soon as I get my hands on the actual 8.0, I'll start working on 
making sure that a) current on 7.2/7.3 can support 8.0 clients
                 b) current can run on 8.0 servers.

That is the order of priority. Assuming 1.4.1 doesn't blow up in my
face, that will be 1.4.2 or 1.4.3 (I don't anticipate any backwards
incompatible changes, except maybe needing a db rebuild).

Comments? Questions? Is anyone using 1.4 in production yet other than
me?


On Tue, 2002-09-24 at 14:35, Alex Kramarov wrote:
> > Could you reregister that client, and see if the error persists?
> 
> it does.
> _______________________________________________
> 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.