-
Notifications
You must be signed in to change notification settings - Fork 130
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
releasenotes-builder: missed new feature #206
Comments
…sues, should be fixed by checkstyle/contribution#206
one more problem - checkstyle/checkstyle#3329 does not have label and build is not failed |
…sues, should be fixed by checkstyle/contribution#206
problem is even bigger:
|
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
It was done intentionally.
Can you give me the exact command that you used to generate release notes? |
yes I know, it is not a problem - it is expected behavior, looks like @rnveach made this comment. But here was update for jgit , that might be a reason of problem:
|
This looks like the issue. Binary search returns With this change, I get the following error when running: |
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
Fix is merged |
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
…sues, should be fixed by checkstyle/contribution#206
issue checkstyle/checkstyle#3437
one more : checkstyle/checkstyle#3892
has label "new feature" but it is not present in releasenotes after 7.6, that forced me to create 7.6.1 release instead of 7.7 .
Release notes skip information for update for all our plugins. That might result in wave of problems.
TODO: investigate a reason of missed "new feature" group in release notes of 7.6.1 - checkstyle.sourceforge.net/releasenotes.html#Release_7.6.1
link to all closed "new feature" issues - https://github.com/checkstyle/checkstyle/issues?q=is%3Aissue+label%3A%22new+feature%22+is%3Aclosed+sort%3Aupdated-desc
The text was updated successfully, but these errors were encountered: