public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: On the road to 4.2
Date: Mon, 28 Mar 2005 19:17:00 -0000	[thread overview]
Message-ID: <20050328162740.GC31057@wookimus.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2737 bytes --]

Now that we've had a few weeks to get used to 4.1, it's time to start
looking at the road to 4.2.  Implicit in each release are on-going
bug-fixes, compilation cleanup, and security fixes; I think it's time to
start taking a serious look at the GNATS bug database.

I'm going to continue to lobby to get it running on the GNU server
instead of my slow sparc.

Today is the 28th of March, 2005.  Let's target the release of 4.2 for
October 1, 2005 or sooner.  Some of the items listed here already have
code written for them.  The PAM patch, for example, and Mel's mail-based
commands and database abstraction work.  As you can see, we have
tentative targets for incorporating them into GNATS.  These can be moved
around as we start making commits to the repository.  For example, I'm
willing to move the PAM patches to 4.2, although it has been noted that
GNUTLS should probably be in place first.

We could probably take another look at gnulib to provide things like
getdate.y or portability functions we don't want to explicitly maintain.
Obviously, automake/autoconf cleanups top the list of relatively simple,
yet needed things.

Currently, this is what the TODO list looks like::

    GNATS General TODO List
  2.Release 4.2: New Features
      1.Cleanup build infrastructure w/automake and autoconf
      2.Mail handling enhancements
          1.Mail-based manipulation of GNATS database (Mel)
          2.Trigger-based mail format replies (Mel)
          3.Add "To:" header parsing for PR# (prnumber@host.domain.tld) in queue-pr
  3.Release 5.0: New Features, Major Changes to DB Layer, RDBMS
      1.Database Enhancements
          1.DB Abstraction Layer (Mel)
            (Finished but not rolled into GNATS CVS 5.0 branch)
          2.Oracle RDBMS Backend (Mel)
            (Finished but not rolled in to GNATS CVS 5.0 branch)
          3.PostgreSQL RDBMS Backend (Mel)
      2.Account enhancements
          1.PAM Authentication (Pankaj)
            (Patch submitted 2004-06-20.)
  4.Release 5.x: New Features
      1.Security Enhancements
          1.TLS integration via gnutls
      2.Mail handling enhancements
          1.MIME Handling
              1.Detach files appropriately for GNATS DB format
              2.Convert HTML to TXT?
      3.Database Enhancements
          1.mbox Backend
              1.Maintain mbox archive of all emails
              2.Fake Audit trail entries as emails and append to mbox archive
              3.Continue to use existing PR datafile for logging events, keywords, and
                metadata

-- 
Chad Walstrom <chewie@wookimus.net>           http://www.wookimus.net/
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

             reply	other threads:[~2005-03-28 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 19:17 Chad Walstrom [this message]
2005-03-28 22:48 ` Chad Walstrom

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=20050328162740.GC31057@wookimus.net \
    --to=chewie@wookimus.net \
    --cc=help-gnats@gnu.org \
    /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).