<a class="${css.text} mr-1" target="__blank" href="https://medium.com/remix-ide/migrating-files-to-workspaces-8e34737c751c?source=friends_link&sk=b75cfd9093aa23c78be13cce49e4a5e8">Guide </a>for migrating the old File System
modalDialogCustom.alert(yo`<div>There was an error migrating your files:${err.message} <div>Please use the ‘Download all Files' action, clear the local storage and re-import your files manually or use the 'Restore files' action.</div></div>`)
Release managers are responsible for the release management lifecycle, focusing on coordinating various aspects of production and projects into one integrated solution. They are responsible for ensuring that resources, timelines, and the overall quality of the process are all considered and accounted for.
# Steps of Release Management
## Release planning:
In this stage, release manager will elaborate a plan for the coming release.
Together with the team, the release manager will form a list of issues and PRs that should be addressed during the release.
More generally and a non negligeable part of the planning is to properly ensure that bugs, issues that weren't totally identified in the roadmap, and the roadmap issues are still being processed as they should.
## Configuring releases:
Release managers will oversee the various aspects of a project before it is due to be deployed, ensuring everyone is on track and meeting the agreed timeline.
## Quality checks:
The quality of the release needs to be reviewed before a project is officially launched.
The release manager is in charge of ensuring manual testing is properly planned and done.
Also that unit testing and e2e for new feaures have been included.
## Deployment:
After being quality checked, the project is ready to be deployed.
The release manager is still responsible for ensuring a project is rolled out smoothly and efficiently.
# Responsibilities
- Planning release windows and the overall release lifecycle.
- Managing risks that may affect release scope.
- Measure and monitor progress.
- Ensure releases are delivered within requirements.
- Manage relationships and coordinate projects.
# Miscellaneous
- Regular check for new filed issues, identify those that requires to be published (included in the release)
- In some really specific situation, it could be required to deploy intermediate releases (e.g critical bug fixes).
- Planning, refinement, retrospective meetings have to be organized by the release manager and any other required meetings.
- Release manager should feel free to implement new techniques and put their own finger print to their release, this could potentially benefit upcoming releases.
Release managers are responsible for the release management lifecycle, focusing on coordinating various aspects of production and projects into one integrated solution. They are responsible for ensuring that resources, timelines, and the overall quality of the process are all considered and accounted for.
This document includes:
- how to publish remix libs to NPM
- how to update remix.ethereum.org
- how to update remix-alpha.ethereum.org
- how to update remix-beta.ethereum.org
- how to release remix IDE
# Steps of Release Management
## Remix libs release
- git fetch origin master
- git checkout origin/master
- git checkout -b bumpLibsVersion
- npm run publish:libs (this command uses lerna)
- commit
## Release planning:
## Remix IDE release Part 1. First push master to beta. Feature Freeze
In this stage, release manager will elaborate a plan for the coming release.
- git co -b remix_beta origin/remix_beta
Together with the team, the release manager will form a list of issues and PRs that should be addressed during the release.
- git reset --hard -master-commit-hash-
More generally and a non negligeable part of the planning is to properly ensure that bugs, issues that weren't totally identified in the roadmap, and the roadmap issues are still being processed as they should.
- git push -f origin remix_beta
## Configuring releases:
## Testing phase
Release managers will oversee the various aspects of a project before it is due to be deployed, ensuring everyone is on track and meeting the agreed timeline.
## In case of fixing bugs push PR's also to beta to include in Release
## Quality Checks:
## Remix IDE release Part 2. Bump the version in beta and release
The quality of the release needs to be reviewed before a project is officially launched.
The release manager is in charge of ensuring manual testing is properly planned and done.
Also that unit testing and e2e for new feaures have been included.
## Deployment:
- git fetch origin remix_beta
After being quality checked, the project is ready to be deployed.
- git checkout origin/remix_beta
The release manager is still responsible for ensuring a project is rolled out smoothly and efficiently.
- git checkout -b bumpVersion
- update package.json version
- remove package-lock.json version and generate a new one with `npm install`
- Planning, refinement, retrospective meetings have to be organized by the release manager and any other required meetings.
- git push -f origin remix_live
- Release manager should feel free to implement new techniques and put their own finger print to their release, this could potentially benefit upcoming releases.
CircleCI will build automaticaly and remix.ethereum.org will be updated
# Release Management Role
## Remix IDE release Part 5. Update Zip in release
- after remix_live is updated, drop the zip (from https://github.com/ethereum/remix-live/) to the release.
Aniket, Liana, David, Rob, Filip
## Remix-ide beta release
- git fetch origin master
- git checkout origin/master
- git checkout -b bumpVersion
- update package.json version to the new version "vx.x.x-beta.1"
- remove package-lock/json version and generate a new one with `npm install`
- merge PR
- git fetch origin master
- git checkout origin/master
- git tag v(version-number) (with "vx.x.x-beta.1")
