public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jim Nasby <[email protected]>
To: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Feature freeze progress report
Date: Tue, 1 May 2007 13:27:40 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
Two more ideas for the manager, now that we seem to have consensus to
build one.
On Apr 30, 2007, at 6:04 PM, Josh Berkus wrote:
> -- We could save the patches by applied date and index them, and
> then have a
> place to point users when they ask: "When was X fixed? Do I *have* to
> upgrade to 8.1 or just 8.0?"
This should also make doing the release notes substantially easier,
though since there's probably some stuff that wouldn't go through the
patch queue we'd want commits from the patch queue to be marked
differently.
That brings up another idea for the patch management webapp...
presumably it could handle most/all of the process of actually
committing a patch. Granted, that's not a huge amount of work, but
it's silly to have committers do by hand that hich could be automated.
--
Jim Nasby [email protected]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
view thread (98+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Feature freeze progress report
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox