info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Feature Version 1.12.11 Released!


From: Derek Robert Price
Subject: Re: CVS Feature Version 1.12.11 Released!
Date: Tue, 14 Dec 2004 16:53:20 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Bohn wrote:

> The news link below references:
>
> * Date handling has been improved slightly.
> * Miscellaneous bug fixes.
>
> Can you give any more details on these?  I didn't see any cvs issues
closed, so I don't think the fixes were tracked by issues, and without
more info, I don't have any way of knowing if any of these changes
impact how we use cvs.  I looked in the ChangeLog and src/ChangeLog in
the repository, but I still didn't get a feel for what all was fixed,
especially related to date handling.  I think a more detailed list of
what fixes were made is better in general so people know what they are
getting and can test those things if needed/desired/required (e.g., by
company standards).

Generally, if one of the CVS developers lumps a fix under
Miscellaneous bug fixes", they are minor issues.  If they are not
closed issues in the DB, you might get some clue by browsing the
mailing lists.  For instance, the date parsing issue is discussed
here:
<http://lists.gnu.org/archive/html/bug-cvs/2004-10/msg00400.html>.
Basically, we wanted the 30 minute timezones to be handled correctly,
but we imported an entire new getdate module from GNULIB , which
incorporates a lot of new features and bug fixes which I could barely
begin to expound on.  I would guess that most of them are not very
important to CVS users, or we probably would have heard about them on
bug-cvs.

You should be able to remain fairly confident that if the issue was
serious (i.e. involving security, data loss, core dumps, or the like),
it would be mentioned in NEWS.  Any issue that changes the "output" of
CVS will also be mentioned in NEWS, so that users will have some
warning that wrappers and the like might break.  API changes (which,
as far as we have been able to within the parameters of requirments,
have always been done in a backwards compatible way), including new or
removed commands and options, will also always be mentioned in NEWS.

It would be very nice if we could track all the issues in the database
on cvshome.org, or even get to all the issues that are tracked, but we
don't have the manpower.  If you'd like to volunteer to assist?  :)

Derek
- --
                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBv2DPLD1OTBfyMaQRAt+YAKCwp1wT8MAUXsA+dHC2FSQGdU2z7wCfcbgT
MYX7cfF8wcWZIGaGZMFIGlQ=
=PCRF
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]