[Tracker-discuss] schema ideas

Paul Dubois pfdubois at gmail.com
Tue Nov 14 23:24:14 CET 2006

FYI: I corresponded with Stefan and we decided that I will take the 'weekly
summary' job.

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.
> 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
> Regards,
> Martin
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061114/6f09f561/attachment.html 

More information about the Tracker-discuss mailing list