Perform v0.2.0 release (Jun)

[hyunsik-yoon]

Let's perform release v0.2.0

• Jun release master: @struss
• Please make a checklist.

Ref: https://github.com/Samsung/ONE-vscode/issues/571

[struss]

Checklist

Release workflow Issue https://github.com/Samsung/ONE-vscode/issues/890

Release Action

• [x] Release Note : #859
  • copy from this Issue (#712)
• [x] Update version before branch out and Code Freeze : update version to 0.2.0
• [x] After Branch out : make tag on 0.2.0 #889
  • [X] ~Update Release Note on home directory~
  • [x] ~Release Draft Issue : Dispatch from github-action~
  • [ ] master branch version up

Release Package

• [ ] ONE-vscode visx package

Release Criteria -> Not this Release.

• [ ] CQM
  • [ ] TypeScript
  • [ ] JavaScript
• [ ] TCM
  • [ ] TypeScript
• [ ] SAM
  • [ ] JavaScript
• [ ] License Verification

Miscellaneous

Final Release

• [x] Release Issue : Issue

#

If any step missed, please add on this.

[jyoungyun]

Before branch-out for release, we need to update the main branch files:

• release_notes.md
• version in package.json

And we didn't release v0.2.0 due to missing release in May. Therefore, this release version should be v0.2.0.

[struss]

And we didn't release v0.2.0 due to missing release in May. Therefore, this release version should be v0.2.0.

um....I think then, I will update this issue and some other issue

• https://github.com/Samsung/ONE-vscode/pull/859

[struss]

And we didn't release v0.2.0 due to missing release in May. Therefore, this release version should be v0.2.0.

@hyunsik-yoon what about changing version into v0.2.0?

[struss]

How to release?

1. Create Issue for Release Check List
2. Create Issue for Release Note
   • Notify all member to write about each change.
   • Create PR on change infra/release/release-note.md
3. Create PR to make stable version
   • Currently version is not updated to unstable up-to-date, so we will update this.
4. Code Freeze
   • Run Release Criteria on this branch ( Not in this release)
5. Branch out
6. Version up to next unstable on Master -> on this, should we clean up infra/release/release-note.md on this PR??
7. Update Release Note on new Branch -> This could be omitted if we overwrite release-note.md.....??
8. Run workflow to release

WIP

[struss]

Check List For Release version

Release Issues

• [ ] Release Note Issue :
• [ ] Release Workflow Issue :

Release PR

• [ ] Release Note PR :
• [ ] Version Up PR :

Release Criteria

• [ ] CQM
  • [ ] TypeScript
  • [ ] JavaScript
• [ ] TCM
  • [ ] TypeScript
• [ ] SAM
  • [ ] JavaScript
• [ ] License Verification

Miscellaneous