[wp-meta] [Making WordPress.org] #1218: Create new build (continuous/latest) that updates after each commit

Making WordPress.org noreply at wordpress.org
Wed Jan 27 03:05:07 UTC 2016


#1218: Create new build (continuous/latest) that updates after each commit
--------------------------+-------------------------------
  Reporter:  ryan         |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Component:  General
Resolution:               |   Keywords:  beta-testing-flow
--------------------------+-------------------------------

Comment (by dd32):

 Just voicing my opinion - I don't think there needs to be a nightly AND a
 latest zip.

 Assuming that there's been a commit since a site last performed a
 background update:
 * Someone who updates to a '''nightly zip''' does it once a day at present
 * Someone who were to update using the proposed '''latest zip''' would do
 it twice a day
 If they weren't using background updates, it'd be on-demand for both
 groups.
 In the event there hasn't been a commit, neither of those background
 update scenario's would get updated, and only the on-demand manual updates
 kick in.

 The cross-over between those two groups is large enough that catering to
 both isn't useful and only makes things more complex.
 If someone doesn't want to be able to update to trunk continuously, or
 doesn't want the autoupdate running twice a day, can easily be solved
 using a technical solution such as "Only update every 24hrs" within a
 plugin.

 In other words:
  * I think we should just increase how many times a day we build the
 nightly builds.
  * We should just rename "nightly" to something else if we really want to
 be specific as to the content of the file.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1218#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list