New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RF] Remove RooFit banner from reference files #840
[RF] Remove RooFit banner from reference files #840
Conversation
Starting build on |
Build failed on mac11/cxx17. Errors:
|
Build failed on mac1015/python3. Failing tests: |
Build failed on windows10/cxx14. Failing tests: |
@guitargeek, as this missed release |
Poke me if anything need to be done, I was under the impression it was ready. |
Hi, thanks for the ping! Sorry for coming back to this so late. I forgot to let you know that it was decided that the banner removal will not be done in the 6.26 branch. So unfortunately, I have to close this PR. At least in the upcoming 6.26 release, the banner is gone for good! I hope this compromise is acceptable for you. |
Thanks for this information. Out of curiosity, is the discussion for the decision to wait till release 6.28 public? |
Hi! No the discussion was not public. The main argument is that patch releases are only for bugfixes, not to introduce behavior change. By removing the RooFit banner, we might cause hickups in user workflows just like here in |
Thanks for clarifying. This is what I assumed. I'm not going to argue as you have more relevant things to do and you've already helped a lot in just getting this in (thank you for that!), but testing frameworks are not users and users should be using APIs not banners to extract information. While I appreciate that ROOT might want to be better about following SemVer then it has been in the past, it is hard to see this as a breaking change (but maybe it is sadly). |
Matching root-project/root#9999 - backport of #834.