Skip to content
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

Changelog for 1.3.5 seems to be missing #1730

Closed
jayfk opened this issue Mar 20, 2017 · 13 comments
Closed

Changelog for 1.3.5 seems to be missing #1730

jayfk opened this issue Mar 20, 2017 · 13 comments
Labels

Comments

@jayfk
Copy link

jayfk commented Mar 20, 2017

Long story short

The latest release in https://github.com/aio-libs/aiohttp/blob/master/HISTORY.rst is 1.3.4 and https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst begins at 2.0.0rc1.

Expected behaviour

Have a changelog for 1.3.5.

Actual behaviour

No changelog for 1.3.5.

Steps to reproduce

Open

CTRL/CMD + F

screen shot 2017-03-20 at 11 03 42

@jayfk
Copy link
Author

jayfk commented Mar 20, 2017

Looks like the release page on PyPi has it: https://pypi.python.org/pypi/aiohttp

Forgot to commit and push CHANGES.rst?

@fafhrd91
Copy link
Member

@samuelcolvin
Copy link
Member

We shouldn't have HISTORY.rst and CHANGES.rst, it's confusing for both users and pyup.

@samuelcolvin samuelcolvin reopened this Mar 20, 2017
@fafhrd91
Copy link
Member

Changes.rst contains only last release changes. Otherwise changes.rst would be huge

@samuelcolvin
Copy link
Member

Well whatever we do it should work with pyup as that description of changes in PRs is extremely useful. I see no problem with a huge changelog.

@jayfk
Copy link
Author

jayfk commented Mar 20, 2017

We shouldn't have HISTORY.rst and CHANGES.rst, it's confusing for both users and pyup.

While I agree that this is confusing, it isn't a problem for pyup to parse the changelog. The underlying issue is that the 1.3.5 changelog wasn't merged back into master and seems to only appear on the 1.3 branch.

I can understand why that's been done, but I think that's even more confusing. As a user (and tool author) I'd expect to see the full changelog of all available releases on the master branch.

@fafhrd91
Copy link
Member

I do not this it is problem in general. It is just current situation with 2.0, usually it takes much less time and amount of changes to make new release

@fafhrd91
Copy link
Member

Help is welcome

@samuelcolvin
Copy link
Member

I'm still not clear what the problem would be with just HISTORY.rst which contains all changes back to the beginning of time?

That would be clear for users and afaik would work with pyup/changelog.

If that's an acceptable solution I'll happily submit a PR.

@fafhrd91
Copy link
Member

ok

@fafhrd91
Copy link
Member

I fixed history

@jayfk
Copy link
Author

jayfk commented Mar 20, 2017

thanks 👍🏼

@lock
Copy link

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants