Skip to content

Upgrade from prerelease to prerelease should not require --pre flag #1554

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.

Sign up for GitHub

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

Jump to bottom
Closed
techtonik opened this issue Feb 11, 2014 · 3 comments
Closed

Upgrade from prerelease to prerelease should not require --pre flag #1554

techtonik opened this issue Feb 11, 2014 · 3 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@techtonik
Copy link
Contributor

..but it may show message to user that upgrade is made between prereleases.
@msmhrt
Copy link

msmhrt commented Feb 13, 2014

I think that upgrade from 1.0beta1 to 2.0beta1 should require --pre flag after 1.0 release.

Please see #1545 for details.

@dstufft
Copy link
Member

dstufft commented Feb 20, 2014

Upgrading from one pre-release to another will require a --pre flag and I don't believe that should change. Possibly something in the exact same series (e.g. a 1.0a1 to a 1.0b1) but that feels too much like a special case not being special enough to break the rules.

@dstufft dstufft closed this as completed Feb 20, 2014
@techtonik
Copy link
Contributor Author

Yes. For the exact same series.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dstufft @msmhrt @techtonik