87 lines
4 KiB
Org Mode
87 lines
4 KiB
Org Mode
:PROPERTIES:
|
|
:ID: 6c7250d0-6871-4030-98f2-2a53c6ca5eb3
|
|
:END:
|
|
#+TITLE: Sites Releases
|
|
#+STARTUP: indent
|
|
|
|
Effective Monday, March 23rd 2020, changes in the sites repository will be
|
|
released regularly on Tuesdays and Thursdays at 11AM. These releases will
|
|
contain *all code in the master branch at that time*, and will be performed by
|
|
the Control Panel teammate on call. Notifications of the release will be sent
|
|
via email and Slack out one hour prior to the repository being tagged to provide
|
|
time for removing anything that has been merged that is not ready for production
|
|
deployment.
|
|
|
|
Sites changes may still be released outside of these windows in the cases of
|
|
expedites, etc., but those should be the exception rather than the rule.
|
|
|
|
* Release procedure
|
|
|
|
The following steps are to be taken by the Control Panel person on call each
|
|
Tuesday and Thursday.
|
|
|
|
** At 10AM
|
|
*** Identify the changes going out
|
|
|
|
In your local clone of sites, check out the master branch, and update it to
|
|
match what's currently in the upstream repository. You'll then want to check the
|
|
list of changes since the last tag.
|
|
|
|
To get the most recent tag, you can run the following command:
|
|
: git describe --tags --abbrev=0
|
|
|
|
A script is available to pull information on tickets from Jira which will work
|
|
handily with git logs piped to it. You can find that script [[https://gitlab.aweber.io/correlr/jira-cli-tool][here]].
|
|
|
|
Running a git log for changes since the last tag and piping it to the jira
|
|
utility script will give you a report of the unique jira issues found and their
|
|
relevant details:
|
|
|
|
: git log 1.212.0.. | jira -i
|
|
|
|
#+begin_example
|
|
Issue Status Summary
|
|
CC-5343 In Development As Molly I want to be able to add an EXISTING custom field to my signup form on my landing page so that I can get more specific customer info
|
|
CCPANEL-10176 Closed INVESTIGATE: "OR" search on tags | Backend
|
|
CCPANEL-10294 Testing Update character limits for subscribers for consistency
|
|
INT-4298 Testing Integrations JS App: Setup pages
|
|
#+end_example
|
|
*** Notify teams via email
|
|
Send an announcement to the development mailing list:
|
|
|
|
#+begin_src message
|
|
To: dev@aweber.net
|
|
From: "Your Name" <xxxxxxx@aweber.com>
|
|
Subject: Sites Release 2020-04-07
|
|
|
|
Sites is scheduled for release in one hour. The following tickets have commits
|
|
since the last tag:
|
|
|
|
| Issue | Status | Summary |
|
|
|---------------+----------------+-----------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| CC-5343 | In Development | As Molly I want to be able to add an EXISTING custom field to my signup form on my landing page so that I can get more specific customer info |
|
|
| CCPANEL-10176 | Closed | INVESTIGATE: "OR" search on tags - Backend |
|
|
| CCPANEL-10294 | Testing | Update character limits for subscribers for consistency |
|
|
| INT-4298 | Testing | Integrations JS App: Setup pages |
|
|
|
|
Please review your tickets and ensure that only code that is ready to release is
|
|
in the sites master branch. The master branch will be tagged and released at
|
|
11am.
|
|
#+end_src
|
|
*** Notify teams via Slack
|
|
|
|
Post a notice in the =#devel= room in Slack. Tag any teams that have changes in
|
|
the release:
|
|
|
|
#+begin_quote
|
|
Sites is scheduled to be released at 11:00 today. If you have any changes please make sure they're ready for release or are removed by then.
|
|
- CC-5343
|
|
- CCPANEL-10176
|
|
- CCPANEL-10294
|
|
- INT-4298
|
|
|
|
/cc @cc-team @cp-team @integrations-team
|
|
#+end_quote
|
|
** At 11AM
|
|
Tag the master branch on the sites repo and push the tag to the upstream
|
|
repository.
|