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

Cut a January 2019 Release #212

Merged
merged 1 commit into from
Jan 30, 2019
Merged

Cut a January 2019 Release #212

merged 1 commit into from
Jan 30, 2019

Conversation

fffej
Copy link
Contributor

@fffej fffej commented Jan 29, 2019

Resolves #211

  • Are you happy for the content of this change to be publicly visible?
  • Are all new or updated entries marked as isNew = true? (not applicable as cutting a release)
  • Does radar.csv render correctly when viewed on Github?
  • Does the updated tech radar display as you expect?

@fffej fffej added the question Further information is requested label Jan 29, 2019
@fffej
Copy link
Contributor Author

fffej commented Jan 29, 2019

I've created a short link (http://bit.ly/RedgateJan2019) as something memorable.

I was planning to do a blog post on the Info site, mentioning the link, create a PDF and tag it in releases.

Anything else I might have forgotten?

@garethbragg
Copy link
Contributor

Seems reasonable to me 👍 I can't immediately think of anything missing.

For future releases I imagine we'll keep stuff marked as isNew until after cutting the release, so the especially interesting parts are more obvious to viewers. For v1 it's entirely academic.

@garethbragg garethbragg merged commit 6290f85 into master Jan 30, 2019
@garethbragg garethbragg deleted the january-2019 branch January 30, 2019 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants