[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-dev] About using GitHub issues
|
I also think it would be good to move to github-issues, and agree that
recent issues or those that are likeley still be relevant should be
copied right now.
An alternative would be to simply add the note whenever there is a need
to touch a bugzilla issue.
Am 30.03.21 um 09:48 schrieb Aleksandar Kurtakov:
On Tue, Mar 30, 2021 at 10:45 AM Mickael Istria <mistria@xxxxxxxxxx
<mailto:mistria@xxxxxxxxxx>> wrote:
Hi all,
The move to GitHub source and PRs was IMO a success: it was simple
enough to carry on; and some new people have contributed since then.
We'll never know if the move to GitHub was a trigger for those new
contributions, but I have some belief it does.
So what about the next step: moving to GitHub issues?
I'd like to start this discussion to first know whether there is a
majority of committers who think going to GitHub issues would be
profitable (count me as one of them).
It is really unnatural going to bugzilla for github project so we should
do it.
And then, we need to find what the best implementation would be. One
proposal would be that we start opening GitHub issues right now and
start using it. we comment all open issues with "m2e has moved to
GitHub issue tracker. If this issue is still happening on latest
release and is still relevant to anyone, please create a new ticket
to https://github.com/eclipse-m2e/m2e-core/issues
<https://github.com/eclipse-m2e/m2e-core/issues> with title being
the title of this bug and description containing a link to this
bug"; and then we close them all and ask webmasters to make the
bugzilla component read-only.
What do you think?
I agree with the plan in general. It would be good if an m2e developer
goes through the bugzillas briefly and move these that are still worth it.
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/m2e-dev
<https://www.eclipse.org/mailman/listinfo/m2e-dev>
--
Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev