WordPress.org

Resolved Brian Hogg
(@brianhogg)

1 week, 3 days ago
Is there no way to use the plugin to test the 4.8 Release Candidate without activating the ‘bleeding edge’ code? If not, perhaps we could add an additional option to test the next version beta/RC without calling it bleeding edge? (but still warn that you shouldn’t do this on a live site unless you know what you’re doing)

Thanks!
- This topic was modified 1 week, 3 days ago by Brian Hogg.

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Author Andy Fragen
(@afragen)

1 week, 3 days ago

Bleeding edge is trunk.
Point release nightly is development code based on current release.

Given those definitions, any release candidate is based on trunk and therefore bleeding edge needs to be checked. It’s clearly implied that a Release Candidate is more stable than an alpha.

Brian Hogg
(@brianhogg)

1 week, 3 days ago

@afragen makes sense, but was still thinking the actual release candidate tag could be an additional option unless the RC1 zip here is actually re-generated off of trunk daily?

If it’s not possible, we could at least add a note that bleeding edge == trunk == new version beta / release candidate for those who aren’t aware.
Plugin Author Andy Fragen
(@afragen)

1 week, 3 days ago
Release candidates have a stable URL as on the main WordPress.org page but are also updated in trunk such that the stable URL isn’t exactly the same code as trunk within a short period of time. Granted there are fewer code changes during the release candidate phase, but he number is not zero.

I’ll see about adding some better statement that bleeding edge === trunk.
- This reply was modified 1 week, 3 days ago by Andy Fragen.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

About this Plugin

In: Plugins and Hacks
3 replies
2 participants
Last reply from: Andy Fragen
Last activity: 1 week, 3 days ago
4.7.5
Status: resolved

Views