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

Files Primary S3 1.1.1 #305

Closed
27 of 32 tasks
HanaGemela opened this issue Jan 22, 2020 · 1 comment · Fixed by #307
Closed
27 of 32 tasks

Files Primary S3 1.1.1 #305

HanaGemela opened this issue Jan 22, 2020 · 1 comment · Fixed by #307

Comments

@HanaGemela
Copy link
Contributor

HanaGemela commented Jan 22, 2020

Reason

QA

  • Generate Changelog
  • Create QA Milestone and set the description to $version
  • Move items from development to qa
  • Create release branch with the format "release-$version"
  • Create "$version Testplan"

Documentation

  • Changes in the docs needed? If so create issue in owncloud/docs.

Marketing

  • Ping @owncloud/marketing
  • Check/adapt info.xml stuff
  • Check/adapt screenshot
  • Blog post or other communication if applicable

Build

All actions to be done on the release branch from here:

  • Bump version in info.xml (no version suffix)
  • Check php version dependency in info.xml
  • Check minimum ownCloud version dependency in info.xml
  • Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

Beta/RC

  • Create github tag for 'v${version}RC1' on release branch
  • Build and sign RC tarball from github tag 'v${version}RC1' (see
    handbook for how to build)
  • Upload as Github release using changelog entries
  • Test and document in testplan => @davitol Sanity tested + fix the issue Catch Mulipart execption when uploading large files #304 (Done in final tarball)

Final

  • Check that no documentation issues are pending
  • Rename last RC tarball to final
  • Create github tag for final 'v${version}' on release branch
  • Upload as Github release using changelog entries

Publishing

  • Upload tarball to marketplace (see handbook for details)
  • Publish tarball for customers (see handbook for details) - customer.owncloud.com and portal.owncloud.com
  • Send mail to release-coordination with link to this ticket and to the changelog
  • Copy email to rocket chat #updates channel

Post-release

  • Rename QA milestone to '$version'
  • Add a new 'Unreleased' section in CHANGELOG.md
  • Make sure, the current changelog section has a date '$version - $currentDate' (ex: 3.1.5 - 2018-08-01)
  • Create PR to merge changes back to the master branch with
    description "Closes #XYZ" with the release ticket number
  • Close the milestone
  • Ensure release template is up to date
@HanaGemela HanaGemela added this to the QA milestone Jan 23, 2020
@HanaGemela
Copy link
Contributor Author

@dtoledo https://github.com/owncloud/files_primary_s3/releases/tag/v1.1.1 final tarball is ready for a smoke test. We've skipped RC phase as this was already tested on PR. This is the official tarball with php 7.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants