Skip to content

Release 'api_core-1.6.0a2'? or 'api_core-1.5.1'? #6326

Closed

Description

@tswast

I'd like to use the changes from #6310 in the library I'm working on.

Not sure about the version number for that one, since:

Activity

  1. tseaver commented on Oct 29, 2018

    @tseaver
    Contributor

    @tswast I believe @lukesneeringer is the one who can answer your question about PR #6267 and the api_core-1.6.0a1 release.

    My take: given that we follow the "keep master releasable at all times" development practice, I believe that we should move the changes from #6267 off onto a branch (or even just revert it and re-merge later) to allow for making an api_core-1.5.1 release from master, including your bugfix from #6310.

    As an alternative, we could make an api_core-1.5-maint branch from 7527a4e (the last commit on master touching api_core/ before #6267), and cherry pick e368317 into it from #6310 in order to make the api_core-1.5.1 release you need.

  2. changed the title [-]Release api_core 1.6.0a2[/-] [+]Release 'api_core-1.6.0a2'? or 'api_core-1.5.1'?[/+] on Oct 29, 2018
  3. added a commit that references this issue on Nov 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: corepackagingtype: processA process-related concern. May include testing, release, or the like.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions