Skip to content
This repository has been archived by the owner on Jul 21, 2019. It is now read-only.

Release Checklist #49

Closed
24 tasks done
mattstratton opened this issue Dec 8, 2016 · 5 comments
Closed
24 tasks done

Release Checklist #49

mattstratton opened this issue Dec 8, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@mattstratton
Copy link
Member

mattstratton commented Dec 8, 2016

This is a meta-issue where we can track all the operational items needed prior to go-live with the new theme.

Items needed in devopsdays-web should be created as a separate branch and pull request on that repo.

To do some time before go-time:

To do immediately before go-time:

To do at go-time:

To do after cutover:

@bridgetkromhout
Copy link
Contributor

I've got a PR in flight that covers a number of these: #248

@mattstratton
Copy link
Member Author

I do believe it's possible for me to install the new theme in advance in the devopsdays-web repo, but we will not point to it.

I can create a test.devopsdays.org URL with Netlify which will build using that theme, so if anyone makes any changes it should update both URLs and we can regression test that way.

@mattstratton
Copy link
Member Author

OK, so I have updated the latest version in there, and it's backwards-compatible; so any builds to master on devopsdays-web will be visible in the new theme at https://test.devopsdays.org.

Internal links go back to www though, so that's not great.

@bridgetkromhout
Copy link
Contributor

The only thing left on this checklist is the regression check; unsure of its status.

@mattstratton
Copy link
Member Author

Updated!

@ghost ghost removed the ready label Mar 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants