[Tracker-discuss] What *has* to be done for the tracker switch-over?

[Brett Cannon]

On 8/7/07, Erik Forsberg <forsberg at efod.se> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> "Brett Cannon" <brett at python.org> writes:
>
> > Let's see if we can't get things pulled together for a switchover no
> > later than the end of this month (early if possible).  With the
> > fallback of having Martin generate the dump, the only thing truly
> > holding us up is making sure all loose ends to tied up.
> >
> > The meta tracker has two critical issues
>
> I closed one of them yesterday. The one remaining is:
>
> 110: Showstopper: sf.net is generating invalid XML
>
>      - Basically done, but I would appreciate if somebody who is not
>        me did check the output, i.e. what is now on bugs.python.org,
>        to make sure we catch any obvious bugs in the new importer.
>
>        A "public inspection" period as proposed by Martin is one way
>        to do it.
>

I think that is best.  Just distribute the work so we get a somewhat
random sampling of checks.

> >and three bugs open
>
> Actually, there are, uhm, were four of them:
>
>  36: Rewrite sf bug redirector at python.org
>
>      - This issue is, AFAIK, only there to remind us that this should
>        be done at switchover.
>
>        It needs to be done by someone with access to the webserver
>        serving python.org, and that someone is not me. On the other
>        hand, if doing this is delayed a day or so, that should be no
>        large problem (I think).
>

I don't have the proper access for this, but Martin was kind enough to
step forward on this.

>  95: Link to meta tracker. I just fixed that.
>
> 119: Tracker Documentation
>
>      - Should be no problem for someone on this list to fix.
>

I am hoping to do this, but help would obviously be great.

> 122: Remove test users
>
>      - A reminder for me to make sure I don't forget it when we do the
>        switchover.
>
> > After that I would assume choosing a date and time that work for
> > people would be next.  I am honestly not worried about shutting the
> > tracker down during business hours as SF has done that to us so many
> > times and I care about about convenience for the people involved.
>
> I would prefer doing it a weekday afternoon/evening. I'm on CEST which
> is GMT+2, and I'll be happiest if my part of the work is completed
> before 22:00 (10 in the evening for you AM/PM people).
>
> Downloading a new snapshot from sf (I can _finally_ do that now, after
> they have given me a free subscription) seems to take about 20
> minutes. Running the import takes 60-90 minutes.
>

So it sounds like a three hour process (using a margin to cover all
the other random steps).

> Reading http://wiki.python.org/moin/TrackerTransition, steps 1-5 are
> either done or better done by someone else. Step 6 I can do.
>
> I don't know if I have the privileges to do step 7, but I think so.
>
> Steps 8-11 I can do as well.
>
> Step 12 needs to be done with someone that has access to the python
> web servers. Not me. There's also the additional step of fixing the sf
> bug redirector.
>
> Step 13. Hmm.. :-).

Celebrate!

-Brett