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
aspectj-users@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/aspectj-users
