public inbox for
 help / color / mirror / Atom feed
From: Chad Walstrom <>
Subject: Re: Plans for 4.x... 5.x
Date: Tue, 22 Jun 2004 16:19:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Chad Walstrom wrote:
> I know I added some tasks to the 4.2 release that we do not have code
> for just yet, such as the MIME handling.  I'm inclined to wrap in
> those features being submitted by Pankaj and Mel first and worry about
> new, uncoded features for later 5.x releases.

Here's an example of what I'm thinking.  (This hasn't been updated to
the CVS yet.)

    GNATS General TODO List
  1.Release 4.1: Code cleanups, bug fixes, documentation updates
    (Mid to Late July 2004?)
    - 1.Prepend $(DESTDIR) to installation targets (Chad)
        (Committed to CVS.)
      2.Add missing manpages -- one manpage for each application (Chad)
        (getclose added.)
      3.Kill install-sid script and update documentation (Chad)
      4.Update Documentation: Set developer's policy.
  2.Release 4.2: New Features
    (September 2004?)
      1.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
    (December 2004?)
      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.Mail handling enhancements
          1.MIME Handling
              1.Detach files appropriately for GNATS DB format
              2.Convert HTML to TXT?
      2.Database Enhancements
          1.mbox Backend
              1.Maintain mbox archive of all emails
              2.Fake Audit trail entries as emails and append to mbox
              3.Continue to use existing PR datafile for logging events,
                keywords, and metadata

Chad Walstrom <> 
           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

      reply	other threads:[~2004-06-21 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 16:31 Chad Walstrom
2004-06-22 16:19 ` Chad Walstrom [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:

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

  git send-email \ \ \ \

* 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).