VIP release process & branches

Vanilla Forums
Vanilla Forums
edited June 2015 in Dev & Ops

Scheduling & Technical:

  • VIPs deploy on the last Tuesday of each month at 8am or 3pm (ET) depending on their preference.
  • We fork the release on Thurs (or Fri morning) before the VIP release (and deploy it to public clusters).
  • Release branches are named release/YYMM (e.g. this month's release will be release/1506).

Communicating with VIPs:

  • We provide release notes by the Friday before deploy (4 days prior). Aim for Thursday.
  • VIPs can delay their deploy a week (to 10am the following Tuesday), or a full month to the next release.
  • VIPs with QA requirements have Friday & Monday before deploy to evaluate the release.
  • Delay requests must be received by 4pm the day before release.

Patching VIPs:

  • Security patches go directly to the release/YYMM branches.
  • Any non-mandatory patch mid-month must go on client-specific branch. Append a hyphen & the cluster number to name the new branch. (e.g. release/1506-512).
  • Always announce patches to the VIP the day before.

Tracking VIP release states.

Comments

  • Unknown
    Unknown

    This kind of process is so nice to see. I remember my first major release at Vanilla. Every single custom theme broke and had to be fixed one by one.

Categories