Skip to content

release-process: update some confusing parts #18934

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

DanielEScherzer
Copy link
Member

Update based on my training with Pierrick

  • dates should correspond to when releases are released, not tagged
  • qa.php.net is no longer used
  • bugs.php.net is no longer used
  • multiple commits to web-php can be combined
Update based on my training with Pierrick
* dates should correspond to when releases are released, not tagged
* qa.php.net is no longer used
* bugs.php.net is no longer used
* multiple commits to web-php can be combined
Copy link
Member

@adoy adoy left a comment

Choose a reason for hiding this comment

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

Lgtm. Thanks

Comment on lines +422 to +428
> If you are going to base your language on one of these old announcements,
> remember that
> * `qa.php.net` has been replaced with https://www.php.net/release-candidates.php
> * `bugs.php.net` has been replaced with GitHub issues, use
> `https://github.com/php/php-src/issues/new?template=bug_report.yml`
> to link directly to the form for creating a new bug report.
> * Since 8.4 there have only been 4 release candidates for PHP X.Y.0, rather than 6.
Copy link
Member

Choose a reason for hiding this comment

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

Does it make sense to have a template for announcements in the document rather than referring to commits?

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