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.

Sign up for GitHub

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

Jump to bottom

Activity 2.5.1 #746

Closed
20 of 25 tasks
patrickjahns opened this issue Jul 3, 2019 · 4 comments · Fixed by #779
Closed
20 of 25 tasks

Activity 2.5.1 #746

patrickjahns opened this issue Jul 3, 2019 · 4 comments · Fixed by #779
Assignees
@micbar
Labels
4 - To release orga
Milestone
v2.5.1

Comments

@patrickjahns
Copy link
Contributor

patrickjahns commented Jul 3, 2019 •
edited by micbar
Loading

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 @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)
  • 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 @davitol v2.5.1 Testplan #780

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) @davitol

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
@patrickjahns patrickjahns added this to the development milestone Jul 3, 2019
@patrickjahns patrickjahns pinned this issue Jul 3, 2019
@davitol
Copy link
Contributor

davitol commented Aug 1, 2019 •
edited
Loading

Closing the ticket due to app was released Jun. 21th 2019

@davitol davitol closed this as completed Aug 1, 2019
@patrickjahns patrickjahns reopened this Aug 2, 2019
@patrickjahns
Copy link
Contributor Author

@davitol
you've reached the wrong one - 2.5.0 was released in June #739

2.5.1 is pending

@micbar micbar self-assigned this Sep 11, 2019
@micbar micbar modified the milestones: development, qa Sep 11, 2019
@individual-it
Copy link
Member

individual-it commented Oct 24, 2019 •
edited
Loading

issues found:

@davitol
Copy link
Contributor

davitol commented Oct 25, 2019

RC Tarball is QA-ready @micbar

@micbar micbar mentioned this issue Nov 6, 2019
Merged
@HanaGemela HanaGemela unpinned this issue Dec 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@micbar micbar

Labels
4 - To release orga
Projects
None yet
Milestone
v2.5.1
Development

Successfully merging a pull request may close this issue.

Release v2.5.1 owncloud/activity
4 participants
@individual-it @micbar @patrickjahns @davitol