-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Updated version number for 0.1.0 release #4639
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
Conversation
|
@jbolinger You need to update Context: see #4633, where I added the |
|
Thanks for the heads up. It looks good now since you've already changed it, but let me know if I've missed anything else.
|
I mean that if you want to cut the release, you need to drop the |
|
@jbolinger Also I just realized you pushed to the |
|
@dhermes - got it, thanks. It looks like some of the other releases outside dataproc still have the suffix hence the confusion. |
|
@jbolinger A "release" here just refers to the specific point in the history where we add the tag. For example, at the setup(
name='google-cloud-pubsub',
version='0.30.0',
...
)but I immediately followed up that release with #4624 to revert the version to "dev mode" / "not release mode". So all of our packages should have the suffix in a "normal" state: ( |
|
Yup, I got it. I'll add some notes to the release doc so that this convention is clear. |
Thanks a lot! This blog post is the original motivation for that practice (if people are wondering when reading the release doc). |
|
Oops, I said I would document some of this last week, didn't I? Sorry, been swamped with pre-Christmas App Engine stuff (and still swamped unfortunately). |
|
@duggelz No worries! |
|
I have checked over this and am about to actually cut this release. |
This step was also straightforward.
Maybe put a template in the doc for how to format the releases.rst if it can't be generated? I copied/modified from another api.