Making WordPress.org

Opened 2 months ago

Closed 2 months ago

#5954 closed enhancement (reported-upstream)

Make beta & RC releases available in Github

Reported by: malthert Owned by:
Milestone: Priority: normal
Component: Version Control Keywords:


It would be awesome if WP beta & RC releases/tags would also be available on https://github.com/WordPress/WordPress

e.g. WooCommerce does it too:

see WP trac https://core.trac.wordpress.org/ticket/51585 who sent me here

Change History (4)

#1 follow-up: @dd32
2 months ago

  • Component changed from General to Version Control

Is this a request to make use of GitHub Releases, or just to have Beta/RCs available as tags?

#2 in reply to: ↑ 1 ; follow-up: @dd32
2 months ago

Replying to dd32:

Is this a request to make use of GitHub Releases, or just to have Beta/RCs available as tags?

To Clarify, if it's just to make Beta/RCs available as tags via GitHub, then we can throw this back to the Core Team and it's up to them to add tagging Beta/RC releases in SVN to the release documentation (ie. on https://develop.svn.wordpress.org/ which will then be reflected in https://core.svn.wordpress.org/, which then they would both be reflected onto git://{develop,core}.git.wordpress.org/ and ultimately in https://github.com/WordPress/{wordpress,wordpress-develop}/). There'd be some work that needs doing on the meta side to make sure they get listed correctly on the w.org release archive though.

If it's to start making use of GitHub releases, then that's a whole other thing and probably a lot more work than it's reasonably worth it to the project, since we don't use GitHub as a primary development location at present. It'd likely also have to be almost a manual process for someone with GitHub access, as while it can be automated via the GitHub API, there'd be some shortcomings trying to make it work with our existing release scripts (that are not at all git aware, and we don't store any SVN rev => Git revision data on w.org either)

#3 in reply to: ↑ 2 @malthert
2 months ago

Replying to dd32:

it's just to make Beta/RCs available as tags via GitHub

Yes, just as tags is sufficient.

#4 @dd32
2 months ago

  • Resolution set to reported-upstream
  • Status changed from new to closed

I've commented on the core ticket, as mentioned above, this is purely up to the core team to decide if it provides any benefit to adding an additional step to the release processes.


Note: See TracTickets for help on using tickets.