Skip to content

[ci skip] Update release process #11873

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

saundefined
Copy link
Member

ref #11868

@saundefined saundefined added the Category: Documentation This is for documentation inside php-src, not on php.net label Aug 4, 2023
@saundefined saundefined requested review from ramsey and adoy August 5, 2023 12:12
@adoy
Copy link
Member

adoy commented Aug 7, 2023

Thanks for the modification. I am still considering whether we should keep this section. If we need to retag a working tag should we delete and force push ? Should we create a new tag with pl and announce this one ? I can understand that this might be confusing for some users that do not follow PHP dev.

@TimWolla
Copy link
Member

TimWolla commented Aug 7, 2023

If we need to retag a working tag should we delete and force push ?

No. deleting and changing a tag should never happen. Whether to retag as x.y.z-1, x.y.z-pl.1 or x.y.(z+1) (i.e. skipping a version) is up to your choice - you'll need to find an agreement amongst the RMs. My personal recommendation would be skipping a version entirely, version numbers are cheap.

@bukka
Copy link
Member

bukka commented Aug 24, 2023

I agree we should rather skip the version. It would be good to create news entry on the website if such situation happens explaining why the tag is being skipped. That would prevent some confusion between users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Documentation This is for documentation inside php-src, not on php.net Waiting on RM
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants