You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if having both the JIRA and github issue trackers is a good idea. It might create confusion, make it more work to follow developments, and might make historic investigations harder/impossible.
Issues should only be reported in JIRA and not on github. The GitHub repo is a mirror and only a service for some GitHub users, not for other project related services.
I am not sure if having both the JIRA and github issue trackers will be a good idea. It might create confusion, make it more work to follow developments, and might historic investigations harder.
—
Reply to this email directly or view it on GitHub.
@FonsRademakers you can disable the wiki and issue tracker here by clicking on "settings" in the right column, then under "Features" uncheck "Wikis" and "Issues".
New issues are now reported only on GitHub. We keep Jira open for existing issues. We will close Jira issue submission to the public in about a year; until then there's a message telling people to go to GitHub instead.
Reacted by Oksana Shadura, Anirudh Dagar and Martin Storø Nyfløtt
Activity
FonsRademakers commentedon Jun 29, 2013
Hi,
Issues should only be reported in JIRA and not on github. The GitHub repo is a mirror and only a service for some GitHub users, not for other project related services.
Cheers, Fons.
On 30 Jun 2013, at 00:37, Benjamin Bannier notifications@github.com wrote:
bbannier commentedon Jul 5, 2013
You can enforce the should by disabling issues and the wiki here.
ndawe commentedon Sep 11, 2013
@FonsRademakers you can disable the wiki and issue tracker here by clicking on "settings" in the right column, then under "Features" uncheck "Wikis" and "Issues".
Axel-Naumann commentedon Sep 9, 2020
New issues are now reported only on GitHub. We keep Jira open for existing issues. We will close Jira issue submission to the public in about a year; until then there's a message telling people to go to GitHub instead.
AnirudhDagar commentedon Sep 9, 2020
This is great, will definitely help with open source contributions.
Thanks!
[cling] Lifetime of MetaParser is that of its input:
[RF] Use local message level changes in stressRooFit to silence tests
[RF] Use local message level changes in stressRooFit to silence tests
Work around cling failure with gcc12 headers.
Work around cling failure with gcc12 headers.
Work around cling failure with gcc12 headers.
Work around cling failure with gcc12 headers.
Work around cling failure with gcc12 headers.
11 remaining items
[df] Delete allocated node before throwing error
[tree] Avoid heap-use-after-free in BulkApiSillyStruct test
[tree] Avoid heap-use-after-free in BulkApiVarLength test
[tree] Avoid heap-use-after-free in BulkApiSillyStruct test
[tree] Avoid heap-use-after-free in BulkApiVarLength test
[df] Delete allocated node before throwing error
[tree] Avoid heap-use-after-free in BulkApiSillyStruct test
[tree] Avoid heap-use-after-free in BulkApiVarLength test
graph: update test/stressGraphics_builtinzlib.ref for el9
[treeplayer] Fix memory management of C-style array branches in test
[tree] Always inform index formulas about changed tree in friend chain
ACLiC TThreadedObjectAutoMemManagement on linux32 due to llvm-jit ABI…
graph: update test/stressGraphics_builtinzlib.ref for el9
graph: update test/stressGraphics_builtinzlib.ref for el9
graph: update test/stressGraphics_builtinzlib.ref for el9