I didn't dive into the details with the webmaster (yet) - he simply offered archiving our bugzilla or continuing to use bugzilla - no migration mentioned but I wouldn't want a full migration anyway, there is too much old irrelevant stuff in there. I haven't spoken to him about possible forwarding options either. If I could coordinate 'open bugzillas updated in the last 1-2 years' or something like that for a migration, I'd possibly try that.
My current plan (obviously the laziest option) is just to continue with both and gradually folks will stop using bugzilla, it doesn't get a ton of traffic anyway. Github issues are the future from my point of view. The README on the project should indicate that and anywhere else I can mention it should also get updated to indicate that. cheers, Andy On Fri, 31 Jul 2020 at 20:17, Alexander Kriegisch <[email protected]> wrote: > This is good news indeed, Andy. Thank you and everyone involved for > this. > > For now there are no existing issues there, so I would like to know if > in the future there will be two issue tracking systems or if there is > any plan to migrate the Bugzilla issues to GitHub too. Or maybe Bugzilla > will stay the leading system? Bugzilla contains lots of historical, but > still relevant information, release notes, mailing list discussions and > StackOverflow comments/answers are pointing there etc. But it is ugly, > difficult to use, there is no text formatting etc. So migrating > everything to GitHub in a batch process and automatically adding links > (even if only as comments) from the Bugzilla issue to the corresponding > GitHub issue would be a good thing to do. Automatic redirection would be > even better, but probably difficult technically. In any case Bugzilla > could stay active in a read-only mode. > > Having said that and reading it again, it sounds way more difficult than > just migrating the Git repo. > > Best regards > -- > Alexander Kriegisch > https://scrum-master.de > > > Andy Clement schrieb am 31.07.2020 22:23 (GMT +07:00): > > > > > > Up until yesterday what was on Github was a mirror for AspectJ. This > meant > > you couldn't raise issues against it (you had to go back to bugzilla), > > also any PRs that were submitted were very difficult to handle because > > project committers couldn't process them easily. > > > > > > Today, the copy of aspectj at > > https://github.com/eclipse/org.aspectj should be a full > > proper, Github repo! Woohoo! The issues tab is alive and PRs should work > > properly. > > > > > > cheers, > > > > Andy > > > > > > _______________________________________________ > aspectj-users mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/aspectj-users
