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

Impersonate 0.5.0 #139

Closed
20 of 26 tasks
PVince81 opened this issue Feb 12, 2019 · 4 comments
Closed
20 of 26 tasks

Impersonate 0.5.0 #139

PVince81 opened this issue Feb 12, 2019 · 4 comments
Assignees
Milestone

Comments

@PVince81
Copy link
Contributor

PVince81 commented Feb 12, 2019

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

Reason

QA

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: https://github.com/owncloud/impersonate/releases/tag/v0.5.0RC1
  • 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

  • Upload tarball to marketplace (see handbook for details)
  • Publish tarball for customers (see handbook for details)
  • 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 0.5.0 #143
@PVince81 PVince81 added the orga label Feb 12, 2019
@PVince81 PVince81 added this to the backlog milestone Feb 12, 2019
@PVince81 PVince81 self-assigned this Feb 12, 2019
@PVince81 PVince81 pinned this issue Feb 12, 2019
@PVince81
Copy link
Contributor Author

PVince81 commented Feb 12, 2019

@sharidas FYI

@PVince81 PVince81 modified the milestones: backlog, development, QA Feb 19, 2019
@PVince81 PVince81 assigned davitol and unassigned PVince81 Feb 19, 2019
@PVince81
Copy link
Contributor Author

@davitol
Copy link
Contributor

davitol commented Mar 1, 2019

@PVince81 Tarball is QA-ready

@PVince81 PVince81 assigned PVince81 and unassigned davitol Mar 5, 2019
@PVince81
Copy link
Contributor Author

PVince81 commented Mar 5, 2019

@PVince81 PVince81 mentioned this issue Mar 5, 2019
@JammingBen JammingBen unpinned this issue Nov 25, 2021
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

2 participants