I also want to go for GitHub Issues. However, they disabled the Issues for the californium repo---no idea why we still
have them for californium.scandium.
So the only possible choice at the moment would be Bugzilla. Thus, I want to continue pushing forward on the bug Julien
sent, so that GitHub actually becomes a choice…
From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Hudalla Kai (INST/ESY)
Sent: Mittwoch, 11. März 2015 16:29
To: Californium (Cf) developer discussions
Subject: Re: [cf-dev] Bug reports
Julien,
Thanks for pointing me to this issue
J Nevertheless, I think we should limit ourselves to using either one of
the tools (Bugzille vs. GitHub Issues) in order to make our lives a little easier until a final decision has been made by the board of the eclipse foundation.
Personally, I’d go for GitHub Issues because of its much better usability. Any opinions?
Kai
On Wed, Mar 11, 2015 at 11:53 AM Hudalla Kai (INST/ESY) <Kai.Hudalla@xxxxxxxxxxxx> wrote:
Hi list,
I was wondering whether I am the only one who is a little confused regarding where we want to track bugs: on GitHub or on eclipse’s Bugzilla?
I think it would be much easier to keep track of progress and discussion on bugs if we could agree on only one bug tracker …
My guess though is that since this is now an eclipse project we have to use eclipse Bugzilla anyway, right?
Regards,
Kai
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
|