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

Cut a 1.0 Alpha 1 release #148

Merged
merged 1 commit into from
Apr 13, 2019
Merged

Cut a 1.0 Alpha 1 release #148

merged 1 commit into from
Apr 13, 2019

Conversation

AstraLuma
Copy link
Member

Getting a pre-release onto PyPI allows us to unblock PPB and more easily get feedback from any testers.

Note that this is not expected to be final, and there are clearly issues we want to resolve before 1.0 final.

However, the basic API seems to have stabilized, so other projects (PPB) can move forward against this API.

Copy link
Collaborator

@pathunstrom pathunstrom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm okay with this.

Want me to cut this, or would you like to do it?

@AstraLuma
Copy link
Member Author

I can do it.

bors r+

bors bot added a commit that referenced this pull request Apr 12, 2019
148: Cut a 1.0 Alpha 1 release r=astronouth7303 a=astronouth7303

Getting a pre-release onto PyPI allows us to unblock PPB and more easily get feedback from any testers.

Note that this is not expected to be final, and there are clearly issues we want to resolve before 1.0 final.

However, the basic API seems to have stabilized, so other projects (PPB) can move forward against this API.

Co-authored-by: Jamie Bliss <jamie@ivyleav.es>
@bors
Copy link
Contributor

bors bot commented Apr 13, 2019

Timed out

@AstraLuma
Copy link
Member Author

bors retry

bors bot added a commit that referenced this pull request Apr 13, 2019
148: Cut a 1.0 Alpha 1 release r=astronouth7303 a=astronouth7303

Getting a pre-release onto PyPI allows us to unblock PPB and more easily get feedback from any testers.

Note that this is not expected to be final, and there are clearly issues we want to resolve before 1.0 final.

However, the basic API seems to have stabilized, so other projects (PPB) can move forward against this API.

Co-authored-by: Jamie Bliss <jamie@ivyleav.es>
@bors
Copy link
Contributor

bors bot commented Apr 13, 2019

Build succeeded

  • docs
  • FreeBSD PYTHON:3.6
  • FreeBSD PYTHON:3.7
  • lint
  • Linux container:python:3.6-slim
  • Linux container:python:3.7-slim
  • macOS PYTHON:3.6.8
  • macOS PYTHON:3.7.2
  • Windows container:python:3.6-windowsservercore-1809
  • Windows container:python:3.7-windowsservercore-1809

@bors bors bot merged commit c29604e into master Apr 13, 2019
@nbraud nbraud deleted the release-1.0a1 branch April 14, 2019 20:49
@nbraud
Copy link
Collaborator

nbraud commented Apr 14, 2019

@astronouth7303 FWIW, I think it's weird to claim API stabilisation when we have a bunch of severe API-impacting bugs that aren't resolved yet:

That said, I don't think this should hold off an alpha release, esp. since this is blocking for ppb itself.

@AstraLuma
Copy link
Member Author

I meant the core usage stuff.

@pathunstrom
Copy link
Collaborator

Yeah, the only big change to the external API is the immutability, and I don't see that external API changing much going forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants