This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
Allow parallel work on "next" release after current release branch is created, but not yet finalized. #997
Comments
|
I think we may already have a ticket similar to this. I suggest a search in the backlog to verify and close the duplicate ticket if necessary. |
tst-kfreiheit
added a commit
to tst-kfreiheit/earthenterprise
that referenced
this issue
Sep 28, 2018
…allel development of current verison on release branch, and next release on master
tst-kfreiheit
added a commit
to tst-kfreiheit/earthenterprise
that referenced
this issue
Sep 28, 2018
…allel development of current verison on release branch, and next release on master
tst-kfreiheit
added a commit
that referenced
this issue
Sep 28, 2018
…development of current verison on release branch, and next release on master (#1029)
husf-dsheremata
added a commit
to husf-dsheremata/earthenterprise
that referenced
this issue
Jan 11, 2019
* 'master' of https://github.com/google/earthenterprise: google#997: Allowing alpha version tag on master branch to enable parallel development of current verison on release branch, and next release on master (google#1029) Fixes google#1004: don't read version file for tasks that don't need to read it (google#1005) google#788 Add flags for poi search, update documentation. (google#1010)
|
Closing because we no longer use "alpha", "beta", etc in version numbers. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As an OpenGEE developer, I want to control the build version number with a git tag so I can begin work on the 'next' release while the current release's release branch is being finalized.
The version numbering logic depends on the version.final tag in the git repo (i.e. 5.2.2-2.final == next version ==> 5.2.3-0.alpha). Proposal is to detect .alpha tags in the repo (currently only .final and .beta tags are used) to allow building the 'future' version of OpenGEE while the current build is finalized.
The text was updated successfully, but these errors were encountered: