Review nightly builds usage and workflow

Open
#790 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php, wordpress
Domain
release

Research direction

Start with the WordPress Handbook section linked in the issue and compare the existing Beta/RC and bleeding-edge nightly publishing paths across Roots' packages. Investigate how point-release nightlies could follow the documented branch-development API and determine what automation is needed for 6.2.x-style branches; done means point release nightlies are published and consumable consistently.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

As described in the WordPress Handbook, three different nightly builds are available:

  • Point release nightlies. The current release is 6.2.2. Selecting this will put you on the track for 6.2.x development.
    (e.g., https://wordpress.org/nightly-builds/wordpress-6.2-latest.zip, API call)
  • Bleeding edge nightlies. Selecting this will put you on the track for 6.3 development.
    (e.g., https://wordpress.org/nightly-builds/wordpress-latest.zip, API call)
  • Beta/RC. Selecting this will update to the next released beta or RC on whichever branch you are currently running.
    (e.g., https://downloads.wordpress.org/release/wordpress-6.3-rc2.zip)

Currently, the following has been implemented and is available across Roots' packages:

  • Beta/RC. 👌 Well tagged and correctly published. Nothing to do.
  • Bleeding edge nightlies. 🙂 Published on main branches.
    • Their constraints (like PHP version) might be suitable to automation, but all good so far.
  • Point release nightlies. ☹️ Not handled yet.
    • Could be done via 6.2-dev-ish tags (not allowed) 6.2.x-ish branches but requires automation.
Dominant language
PHP
Stars
43
Forks
8
Avg merge
1m
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from roots/wordpress-packager

All issues in roots/wordpress-packager

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.