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

Incremented viewer version after release/2024.08-DeltaFPS branch creation #2369

Merged
merged 1 commit into from
Aug 22, 2024

Conversation

brad-linden
Copy link
Collaborator

I'm considering trying something new here for the new git-flow process. since release branches now try to avoid merging from main when a viewer is promoted (as they should already contain all the relevant changes by way of them being in develop as well). it seems that the right time to increment the viewer version is immediately after freezing a new release branch. that way nightly builds of develop will now have an incremented version number from that point onward.

@brad-linden brad-linden merged commit 9b0010b into develop Aug 22, 2024
13 checks passed
@brad-linden brad-linden deleted the brad/develop-versioning branch August 22, 2024 17:56
@github-actions github-actions bot locked and limited conversation to collaborators Aug 22, 2024
@nat-goodspeed
Copy link
Collaborator

the right time to increment the viewer version is immediately after freezing a new release branch

To make sure I understand: I think you mean right after creating a new release branch from develop? Or do you mean "freezing" in the sense of no additional changes, just before promoting? From context, I think the former.

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

Successfully merging this pull request may close these issues.

3 participants