Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Option to Check for Latest Release Candidate (Beta) #352

Closed
raamdev opened this issue Oct 11, 2014 · 13 comments
Closed

Feature Request: Option to Check for Latest Release Candidate (Beta) #352

raamdev opened this issue Oct 11, 2014 · 13 comments

Comments

@raamdev
Copy link
Contributor

@raamdev raamdev commented Oct 11, 2014

It would be nice if a site owner could choose to always run the latest Release Candidate (if available). Whenever we publish a Release Candidate on GitHub, the software (LITE and Pro) could automatically update to that latest beta release if the site owner has this option enabled.

This would help with testing new releases, as a site owner would not need to manually download and install Release Candidates.

For Quick Cache LITE, this could work by monitoring the Quick Cache Releases on GitHub and looking for a new "vXXXXXX (Release Candidate *)" release and downloading and installing the zip file attached to that release.

For Quick Cache Pro, we could utilize the existing update mechanism but have it also look for quick-cache-pro.vXXXXXX.rc.zip when this option is enabled.


Related: #395 #394 #465 #289 #464 #352

@raamdev raamdev added this to the Future Release milestone Oct 11, 2014
@raamdev raamdev modified the milestones: Next Release, Future Release Nov 25, 2014
@raamdev raamdev modified the milestones: Next Release, Future Release Dec 27, 2014
@raamdev raamdev modified the milestones: Next Release, Future Release Jan 21, 2015
@raamdev raamdev modified the milestones: Next Release, Future Release Mar 13, 2015
@raamdev raamdev modified the milestones: Next Release, Future Release Apr 10, 2015
@raamdev raamdev changed the title Feature Request: Option to Check for Latest Release Candidate Feature Request: Option to Check for Latest Release Candidate (Beta) Apr 10, 2015
@raamdev raamdev modified the milestones: Future Release (Lite), Next Release (Lite) Sep 30, 2015
@jaswrks
Copy link

@jaswrks jaswrks commented Oct 7, 2015

Next Actions (Step 1 of 2)

  • New feature branch in the websharks/zencache-pro repo.

  • After this line add the following:

    'pro_update_check_stable',
  • After this line add the following:

    'pro_update_check_stable' => '1', // `0` for beta/RC checks; defaults to `1`
  • After this line add the following:

    'stable' => $this->plugin->options['pro_update_check_stable'],
  • Submit PR.


Referencing the Product API at ZenCache.com: https://github.com/websharks/zencache.com/blob/master/wp-content/mu-plugins/product.php#L606

@raamdev raamdev modified the milestones: Next Release (Pro), Next Release (Lite) Oct 7, 2015
@raamdev raamdev modified the milestones: Next Release (Pro), Future Release (Pro) Oct 29, 2015
@jaswrks
Copy link

@jaswrks jaswrks commented Nov 12, 2015

Next Actions (Step 2 of 2)

  • New feature branch in the websharks/zencache-pro repo.

  • In this file add a new configurable option to the UI that controls the value of pro_update_check_stable, along with any additional details you'd like to add.

    For instance, a select menu that allows a site owner to enable beta and RC releases during an upgrade. If they want to be on the cutting edge at all times, and are willing to accept the risk, they can set pro_update_check_stable to a value of 0.

  • Submit PR.


Note: The above instructions for Step 2 are rather vague. If you're able, attempt step 2 right away. Otherwise, once step 1 is complete hit me on Slack for a more complete set of Step 2 instructions.

@jaswrks
Copy link

@jaswrks jaswrks commented Nov 12, 2015

Assigning this to @kristineds :-)

@kristineds
Copy link

@kristineds kristineds commented Nov 17, 2015

@jaswsinc @raamdev Submitting PRs for Step 1 and 2:

Note: Step 2 is a work in progress. It is missing a new icon for the menu header and I would probably need some help with the text description.:)

kristineds added a commit to wpsharks/comet-cache-pro that referenced this issue Nov 17, 2015
kristineds added a commit to wpsharks/comet-cache-pro that referenced this issue Nov 18, 2015
kristineds added a commit to wpsharks/comet-cache-pro that referenced this issue Nov 19, 2015
jaswrks pushed a commit to wpsharks/comet-cache-pro that referenced this issue Nov 24, 2015
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Nov 24, 2015

@jaswsinc One thing I just realized has not yet been addressed is the ability for the Lite version to also check for Beta Updates. I suppose that would require introducing the Pro Updater (minus the stable update portion) to the Lite version, correct? What sorts of challenges do you foresee there?

@jaswrks
Copy link

@jaswrks jaswrks commented Nov 24, 2015

require introducing the Pro Updater (minus the stable update portion) to the Lite version, correct?

Correct. I have not done this yet, so I'm not sure what challenges might exist. However, here are some things that come to mind.

  • A possible conflict between the WordPress update servers and our own. I think if beta testing is enabled in the lite version though, that will not matter. Probably not going to be an issue, because the behavior would be opt-in only.
  • Not sure what the WordPress update server would respond with it receives a version string that is above and beyond anything that has ever existed on the WordPress.org side; e.g., if you enable beta testing, get the latest/greatest copy, then disable beta testing, and WordPress.org is contacted by the API to compare your current version to the versions available at WordPress.org. Need to test this.
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Nov 24, 2015

Next Pro Release Changelog:

  • New Feature! It's now possible to configure the Pro Plugin Updater to check for Beta versions (Release Candidates) of the plugin. See ZenCache → Plugin Updater → Beta Testers. We publish Release Candidates a week or so before official releases to allow for additional testing and early preview of upcoming features and bug fixes. If you're not already on our Beta Testers mailing list, you can signup here. Props @kristineds. See Issue #352.
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Nov 24, 2015

I'm forking the work for the Lite version of this feature to a separate GitHub Issue: #621

@raamdev raamdev closed this Nov 24, 2015
@wpsharks wpsharks locked and limited conversation to collaborators Dec 21, 2015
@raamdev
Copy link
Contributor Author

@raamdev raamdev commented Dec 21, 2015

ZenCache Pro v151220 has been released and includes changes worked on as part of this GitHub Issue. See the release announcement for further details.


This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#352).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants