Closed jchsublet closed 4 years ago
Thanks for the comment @jchsublet. You can see this information in the Release Notes.
The updates that are available in the different branches changes on a regular basis and would be challenging to keep that updated. We do invite a few people to test those branches—as you are well aware.
I just updated the releases for NJOY2016 to add 2016.56. I should have done that when we pulled in that fix from the start. My apologies for this delay.
I'll update the release notes as well.
The release notes already contain 2016.56. I must have done something right :-)
The release notes already contain 2016.56. I must have done something right :-)
Don't let this go to your head!
Apologies, I did not previously "see" the release notes. Having said that is there a way to flag the issues in that case #130 as done, achieved, checked ? as the issuer I'll happily do this now, in doing so recognising your impressive skill and commitment to serve a community that do not always let know how your efforts are appreciated
You can always go and look at the issue. At the top is an indication of the status of the issue. When a Pull Request is accepted that fixes an issue, we need to make sure to state that the issue has been resolved.
@jlconlin indeed, I could have should I have noticed the "38 open 40 closed" tabs !! which now I have !! Thank you
It would be of some use to let trusty user know which issues (bug or enhancement) has been solved in, by the latest master release, been as I wrote
character(8),public::vers='2016.56' character(8),public::vday='24Jan20'
And may be which branches are available for testing, or you want to keep that to the few