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

[decouple] First run wizard 1.2.0 #97

Closed
18 of 23 tasks
PVince81 opened this issue Apr 2, 2019 · 6 comments · Fixed by #103
Closed
18 of 23 tasks

[decouple] First run wizard 1.2.0 #97

PVince81 opened this issue Apr 2, 2019 · 6 comments · Fixed by #103
Assignees
Labels
Milestone

Comments

@PVince81
Copy link
Contributor

PVince81 commented Apr 2, 2019

When taking care of a task (and marking as done), please add your name to the task!

Reason

QA

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

Documentation

  • Changes in the docs needed?

Marketing

  • Ping RocketChat channel #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)
  • Update CHANGELOG.md - Change CHANGELOG.md 'Unreleased' to '$version' (final release date unknown)

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 => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

Final

  • Create github tag for final 'v${version}' on release branch
  • Build and sign final tarball from github tag 'v${version}' (see
    handbook for how to build)
  • Upload as Github release using changelog entries
  • Smoke test tarball (at least install + enable)

Publishing

  • Send mail to release-coordination with link to this ticket and to the changelog

Post-release

  • Rename QA milestone to '$version'
  • Add a new 'Unreleased' section in CHANGELOG.md and add release 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: Release 1.2.0 #103
@PVince81 PVince81 added the orga label Apr 2, 2019
@PVince81 PVince81 added this to the development milestone Apr 2, 2019
@PVince81 PVince81 self-assigned this Apr 2, 2019
@PVince81 PVince81 modified the milestones: development, QA Apr 2, 2019
@PVince81
Copy link
Contributor Author

PVince81 commented Apr 2, 2019

@PVince81 PVince81 added this to Dev done, ready for QA in Releases Apr 2, 2019
@PVince81
Copy link
Contributor Author

PVince81 commented Apr 2, 2019

Note: the RC is NOT signed

  • TODO: generate signing key before rebuilding final tarball

@PVince81
Copy link
Contributor Author

PVince81 commented Apr 4, 2019

stable10 to master diff is close, low risk. locking stable10 now, we'll use master for future

@PVince81
Copy link
Contributor Author

PVince81 commented Apr 5, 2019

assigned @dpakach for regression testing

@dpakach
Copy link
Contributor

dpakach commented Apr 12, 2019

Firstrunwizard testplan for 1.2.0RC1
Issue - #102
Test plan in QA repo - owncloud/QA#616

@PVince81
Copy link
Contributor Author

@PVince81 PVince81 mentioned this issue Apr 16, 2019
@PVince81 PVince81 moved this from Dev done, ready for QA to QA ready, Release in progress in Releases Apr 16, 2019
Releases automation moved this from QA ready, Release in progress to Release done 🎉 Apr 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants