[wp-meta] [Making WordPress.org] #5954: Make beta & RC releases available in Github
Making WordPress.org
noreply at wordpress.org
Wed Nov 17 01:36:57 UTC 2021
#5954: Make beta & RC releases available in Github
-----------------------------+---------------------
Reporter: malthert | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Version Control | Resolution:
Keywords: |
-----------------------------+---------------------
Comment (by dd32):
Replying to [comment:1 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)
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5954#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list