[Tracker-discuss] Ready for Prime Time?

[Erik Forsberg]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

With the list of showstoppers in the meta database reduced to two
issues, both of which are of the type which can't be closed until
we've gone into production, I think it's time to start thinking about
going live. 

Some thoughts;

* Do we need a public beta period to allow people not on this list to
  test the tracker?

  In my opinion, we should avoid this as I'm afraid it will to lots of
  issues that are seen as showstoppers by people. Better handle these
  problems as they come - after all, this tracker is supposed to be
  much better than the current tracker, so we should start using it
  ASAP.

* What kind of documentation needs to be written? And who volunteers
  to do it? :-)

* In what steps, and when, do we run the final conversion? The
  conversion process looks something like this:

  0. (Only in final conversion) Lock sf tracker down, if possible. 

  1. Get a fresh copy of the xml backup from sf.net. Takes 10-15 minutes.

  2. Transfer to psf. 5 minutes.

  3. Run conversion. Takes about an hour.

  4. Done. 

  Some hostname fiddling somewhere inbetween, or before, to get
  bugs.python.org to point to the right IP.

  I'm willing to do the conversion work. You python-dev people will
  have to come with some feedback on when and how to do it.

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFFvkWHrJurFAusidkRApw3AKDewp7H8Z+vvr3A4aaXJ+HgPZ7cuwCgvghs
WHrutANjnV4l+0oHAZTtLRc=
=7QM2
-----END PGP SIGNATURE-----