[Tracker-discuss] schema ideas

[Brett Cannon]

On 11/14/06, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>
> Erik Forsberg schrieb:
> > How do we find out which features/changes are so important that we
> > _must_ implement them before going live, and what features/changes can
> > wait until later?
>
> I'm fine with the process you are proposing. I have a specific answer
> to this question, though: Changes that would force a re-import of all
> data (because of data-loss, or data-garbling) need to be detected before
> the new infrastructure goes life. Anything else can probably wait until
> later.


Ditto from me.  We can try to figure things out ahead of time before we do
the final SF pull, but if it is easy to change the schema later on then it
is not such a priority.

But we do need to heed what Neal Norwitz and Anthony Baxter want since they
handle releases.  And then people who do a lot of triaging (Martin v. Löwis
and Georg Brandl) should also be listened to.  I am not saying everyone else
should be ignored, but these people have to deal with the tracker the most
in the end.

Some of the other thing should get high priority to be implemented
> before the new tracker goes life: those features that are currently
> available in the SF tracker and heavily used. For these, I see
> - email notifications
> - SF redirector
> - weekly summary


I agree with the first two.  I don't know if the weekly summary Kurt sends
out is that critical.  It's nice to keep an eye on the number of current
bugs, but I don't see it as a show-stopper.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061114/75a42f61/attachment.html