Hi all,
Just like for sunsetting the Wiki¹, we came out with a plan at the Grenoble
minisprint to move our bugtracking from Bugzilla to Heptapod.
TL;DR: Bugzilla URLs will redirect to the same issues re-created in the
mercurial-devel Heptapod issue tracker², and Bugzilla will be no more.
Now for the longer version:
# Why move away from Bugzilla?
Here are some of the reasons, some which are very similar to the wiki:
- it's an extra log-in to keep track of and to check up on for
maintainers
- it requires an extra account for users and fragments our experience
- it uses extremely old software which is insecure and requires
insecure
dependencies
- it makes the project look old
- it is also attacked by spammers
- Heptapod issues are well integrated with the merge review system
we use
for review.
# How it will go
To this end, I've written up a plan. You can follow along in real-time
in the
mercurial-devel Heptapod task tracker³ (how very meta of me) for the
details.
Here are the most important points:
- [x] Verify that Heptapod allows for creating arbitrary issue IDs even
after bumping the sequence
- [x] Bump the ID sequence to 10000
- [x] Inform users that all new issues go to Heptapod (we're here)
- [x] Script to archive the bz data the way we want it to be done
- [ ] Make bz read-only (could involve killing URLs and/or HTTP
methods)
- [ ] Script to create an issue with all of its comments and
attachments,
keeping the bug id and possibly mapping active users to
Heptapod
- [ ] Mass test in a dummy project
- [ ] Create redirect rules to the new tickets, comments and
attachments
We chose not to use existing tools because they (rightly) warned that a lot
of hacking would be needed, and we figured that we could simply write it
faster
than trying to adapt old semi-bespoke migration code to new GitLab APIs.
# The future
After this mail is sent, our Bugzilla instance will be made read-only, and
trying to create a new bug though the UI will trigger a redirect to a page
that explains this migration.
All new bug reports (for all "products" in the Bugzilla sense) will
happen in the
mercurial-devel issue tracker³.
Thanks,
Raphaël
[1]
https://lists.mercurial-scm.org/pipermail/mercurial/2025-July/106680.html
[2] https://foss.heptapod.net/mercurial/mercurial-devel/-/issues
[3] https://foss.heptapod.net/mercurial/mercurial-devel/-/work_items/10003
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
