[Kolab-devel] Bugzilla

Thomas Arendsen Hein thomas at intevation.de
Thu May 5 17:47:18 CEST 2011


* Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com> [20110416 09:48]:
> It had not yet been definitively set in stone how and when the switch to 
> Bugzilla would happen.
> 
> Aside from that, bugzilla at lists.kolabsys.com[1] is a list that does receive 
> notifications for all changes to all entries in bugzilla.
> 
> We can create additional lists per topic / (category of) component(s) should 
> the need arise, such as has been the case for packaging-bugs at lists.ks.c 
> already.
> 
> I would like to use kolab-devel as a nice, clean discussion list without 
> "support" or "issue" noise, if you will.

My wishes for the Bugzilla migration:
- a hostname below kolab.org
- old issues should be converted and issues.kolab.org/issue123
  should redirect to the new location, ideally the issue numbers
  of converted issues stay the same. New issues (or tickets or
  whatever the name will be) will start at a higher number, e.g.
  at 10000, to be easily distinguished.
- similar with merges, but since there are only few merges and the
  numbers will probably clash with issues (unless we add a second
  class of issues to bugzilla, too), using something like 8012 for
  merge12 might be needed.

Completely migrating the old user database would be nice, but is not
that important for me, but in that case the information about who
reported or commented issues should be stored in a different way.

Jeroen, I started a small script to export roundup's database as XML
in February, but before continuing with it I'd like to hear if the
output format is useful for you. You can check the current state by
using ssh roundup at issues.kolab.org and executing
./ks-export kolab

Known missing features are:
- exporting files
- exporting user data
- exporting all issue attributes (only a small sample is currently exported)
- should the messages be base64 encoded to preserve every detail?
  (currently it is not, this makes preserving indentation harder)
- export more than the three hardcoded three sample issues

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110505/473a53f9/attachment.sig>


More information about the devel mailing list