[wp-trac] [WordPress Trac] #51585: Make beta & RC releases available in Github

[WordPress Trac]

#51585: Make beta & RC releases available in Github
-----------------------------+------------------------------
 Reporter:  malthert         |       Owner:  (none)
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by malthert):

 @om4csaba this is exactly our use case too.

 Replying to [comment:12 dd32]:
 >
 > For automated testing, testing against trunk would be better IMHO,
 knowing it's broken in Beta1 isn't super useful IMHO if it was fixed the
 next day in trunk.

 Would be better, and this is the way we did it before. Unfortunately, if a
 new bug is added in trunk, it means it takes more than double the time to
 identify the source of the bug: we suddenly have changed 2 things (our
 code we test in CI) and the commits in WP core - so we have to debug
 double the things, to check whether the bug came from our changes or from
 the changes in trunk.
 If you only have one/few branches/plugins you test, that might not be an
 issue, but when you have to check 20 plugins and have multiple developers,
 we are suddenly wasting a lot of time.


 > However, I would also suggest that using GIT/SVN to fetch pre-release
 releases is probably not ideal (although I understand part of your current
 workflow), I would suggest something like `wp core download
 --version=beta` would be better (unfortunately wp-cli only seems to
 support stable/nightlies right now, not beta/rc). But you could also do
 `wp core download https://wordpress.org/wordpress-5.8.2-RC1.zip`, or just
 replace your `git clone` with a `curl $url | unzip` command.

 That's basically what I do atm. The issue here is that I have to manually
 look up what is the latest Beta/RC first and then download that (sounds
 ridiculous I know...)

 Advantage of git tags would be that I can automatically get the latest
 beta/rc/release to use in CI.
 Instead of having a calendar reminder every week to download the latest WP
 beta/RC in the weeks leading up to a new WP release, it could be fully
 automated with git tags.
 Saving me, and probably everybody else with CI, 2 days a year.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/51585#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform