Skip to content
This repository was archived by the owner on Jul 14, 2026. It is now read-only.

Add docs for releasing Phoenix assets - #3186

Merged
PVince81 merged 2 commits into
masterfrom
add-release-docs
Jul 13, 2020
Merged

Add docs for releasing Phoenix assets#3186
PVince81 merged 2 commits into
masterfrom
add-release-docs

Conversation

@micbar

@micbar micbar commented Mar 16, 2020

Copy link
Copy Markdown
Contributor

Description

Related Issue

  • Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

  • test environment:
  • test case 1:
  • test case 2:
  • ...

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:

Open tasks:

  • ...

@micbar
micbar requested review from LukasHirt and PVince81 March 16, 2020 16:41
@micbar
micbar requested a review from DeepDiver1975 as a code owner March 16, 2020 16:41
@micbar micbar self-assigned this Mar 16, 2020
@update-docs

update-docs Bot commented Mar 16, 2020

Copy link
Copy Markdown

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

@micbar
micbar force-pushed the add-release-docs branch from a6c42fc to af5cf92 Compare March 16, 2020 16:43
Comment thread docs/releasing.md Outdated
4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> .
5. Update the phoenix asset in the Makefile.
6. Run `go generate`.
7. Create Changelog item for the Update in the `$major.$minor.$patchVersion_YYYY-MM-DD` folder.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make generate

@micbar

micbar commented Apr 20, 2020

Copy link
Copy Markdown
Contributor Author

@PVince81 @LukasHirt This is laying around some time now.

Can you give Feedback?

@LukasHirt

Copy link
Copy Markdown
Collaborator

Looks nice, just thinking though if the docs is the right place for this. Since the releases will be anyway done by the team and it's more a process then maybe would handbook be a better location?

^ Not saying it should be like that, just asking 😉

Comment thread docs/releasing.md Outdated
3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder.
4. Commit your changes.
5. After merging, wait for the CI to run on the merge commit.
6. Go to "Releases" in GH click "Draft a new Release".

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing "and" before click?

Comment thread docs/releasing.md Outdated
2. Create a Folder in `changelog` for the release version and date `mkdir $major.$minor.$patchVersion_YYYY-MM-DD`.
3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder.
4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> .
5. Update the phoenix asset in the Makefile.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how ?

Comment thread docs/releasing.md Outdated
1. Create a branch `release-$version`. in <https://github.com/owncloud/ocis-phoenix>
2. Create a Folder in `changelog` for the release version and date `mkdir $major.$minor.$patchVersion_YYYY-MM-DD`.
3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder.
4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> .

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how ? add the command directly

@PVince81

Copy link
Copy Markdown
Contributor

@micbar can we move this to the repo ocis-phoenix ? we could still link to that page from here

I can take care if you agree

@PVince81

Copy link
Copy Markdown
Contributor

to clarify: we keep the Phoenix repo related docs here in this PR but move the ocis-phoenix ones to the other repo and link them together

Comment thread docs/releasing.md Outdated
@PVince81

Copy link
Copy Markdown
Contributor

I've extracted the ocis-phoenix bit into owncloud/ocis-phoenix#71

next up: reducing this PR to the minimum needed for a Phoenix release

@PVince81 PVince81 changed the title [WIP] Add docs for releasing in oCIS Add docs for releasing in oCIS Jul 10, 2020
@PVince81 PVince81 changed the title Add docs for releasing in oCIS Add docs for releasing Phoenix assets Jul 10, 2020
@PVince81

Copy link
Copy Markdown
Contributor

rebased and adjusted, please review

@LukasHirt LukasHirt left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PVince81
PVince81 merged commit 18852c1 into master Jul 13, 2020
@delete-merged-branch
delete-merged-branch Bot deleted the add-release-docs branch July 13, 2020 11:48
ownclouders pushed a commit that referenced this pull request Jul 13, 2020
Merge: 5d5e261 a0ccb3c
Author: Vincent Petry <pvince81@owncloud.com>
Date:   Mon Jul 13 13:48:14 2020 +0200

    Merge pull request #3186 from owncloud/add-release-docs

    Add docs for releasing Phoenix assets
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants