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

Release 4.4.0, 4.4.1 #9041

Closed
17 tasks done
unclecheese opened this issue Jun 4, 2019 · 4 comments
Closed
17 tasks done

Release 4.4.0, 4.4.1 #9041

unclecheese opened this issue Jun 4, 2019 · 4 comments

Comments

@unclecheese
Copy link

unclecheese commented Jun 4, 2019

Subtasks

  • Compile a list of known issues
  • Post CWP docs update with known issues
  • GraphQL security fix submitted
  • GraphQL security fix PR/Merge
  • Write 4.4.0 blog post
  • Write CWP 2.3.0 blog post
  • Document file migration limitations in 4.4.0 changelog (prefer 4.4.1)
  • Document GraphQL authentication options and CSRF protection
  • Add React 16 to changelog
  • Merge security fixes (framework, environment-check)
  • Let marketing know when release date/time is confirmed
  • Merge up 4.2, 4.3 branches
  • Do release
  • Ensure new minor release is visible on doc.silverstripe.org, userhelp.silverstripe.org
  • Forum post
  • Slack channel message
  • Disclose security fixes
@unclecheese unclecheese added this to the Recipe 4.4.1 milestone Jun 4, 2019
@unclecheese unclecheese self-assigned this Jun 4, 2019
@unclecheese
Copy link
Author

unclecheese commented Jun 4, 2019

@kinglozzer
Copy link
Member

Raised on Slack - there doesn’t appear to be a 4.4.1 changelog. Not a major issue as not much has changed of course, just thought I’d raise it here as I thought they were automatically generated as part of the release

@Juanitou
Copy link
Contributor

Juanitou commented Jun 10, 2019

A minor issue with the 4.4.0 changelog: The links to the security patch for SS-2018-022 are broken, and I have not found a valid one. The identifier 2018-22 is not found in the Security Releases page.

@michalkleiner
Copy link
Contributor

Yes, the Security Releases page doesn't have anchors based on titles, so it's not possible to link to a specific one. Looked at that yesterday.

@unclecheese unclecheese removed their assignment Jun 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants