public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Milan Zamazal <pdm@zamazal.org>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: <gnats-devel@sources.redhat.com>
Subject: Re: Compatibility between GNATS 3.x and 4.x? gnatsweb?
Date: Mon, 12 Feb 2001 13:23:00 -0000	[thread overview]
Message-ID: <87wvaviq3x.fsf@zamazal.org> (raw)
In-Reply-To: <Pine.BSF.4.33.0102120224340.83060-100000@deneb.dbai.tuwien.ac.at>

>>>>> "GP" == Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
        
    GP> On 11 Feb 2001, Milan Zamazal wrote:

    >> - I don't consider a backward compatibility being a serious issue
    >> here, because I suppose most installed interfaces are tight to
    >> their server and are supposed to be upgraded together with the
    >> server.

    GP> Hmm, not necessarily. For example, I would have liked to use the
    GP> current CVS version of gnatsweb on gcc.gnu.org, first to do some
    GP> testing by myself, and then also in production use. This I could
    GP> do easily, but having the entire GNATS installation updated,
    GP> would be quite more involved.

If I understand you well, you mean that new Gnatsweb should still allow
work with GNATS 3?  This would be nice but it is solely a matter of
Gnatsweb.  If Gnatsweb is designed well enough, the backward
compatibility shouldn't be a big problem.  (As for my gnats2w hack,
there's no problem with retaining the backward compatibility with
GNATS 3, there is a problem with supporting the full flexibility of
GNATS 4 instead -- gnats2w wasn't designed with a big functional
extensions of the server in mind.)

    GP> (I hope the upgrade path from GNAT 3.x to 4.x will be simple and
    GP> well documented, so that one can easily migrated his databases?
    GP> Then it'll be less of a problem for most regular sites.)

Yes, moving databases should be easy -- actually I use a copy of GNATS
bug database from sources.redhat.com (running with GNATS 3 there) on my
machine with GNATS 4.  All I had to do was to add the `dbconfig' file
and to customize it a little.  Of course, I plan to document the upgrade
process appropriately.

Regards,

Milan Zamazal

-- 
"Having GNU Emacs is like having a dragon's cave of treasures."
                                                Robert J. Chassell

      reply	other threads:[~2001-02-12 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08  3:44 Gerald Pfeifer
2001-02-12 13:22 ` Milan Zamazal
2001-02-11 17:30   ` Gerald Pfeifer
2001-02-12 13:23     ` Milan Zamazal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wvaviq3x.fsf@zamazal.org \
    --to=pdm@zamazal.org \
    --cc=gnats-devel@sources.redhat.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).