search

oceanprotocol / pm

Zenhub needs each issue associated with one repo. This repo is a workaround, to mark issues that span >1 repos.
4 stars 0 forks source link

optimize the release process #79

Closed ssallam closed 2 years ago

ssallam commented 3 years ago

The goal of this task is to make the release process as short as possible without manual steps. Ideally starting a script will do the perform all of the steps.

Do this for all major py repos:

calina-c commented 3 years ago

I moved this to the "PM to discuss" column, since I understand there is still disagreement on how we release versions of our software. We should probably have a call and make some decisions together.

calina-c commented 3 years ago

Please note that the Aquarius readme should be updated with the final release process, since that section/linked README does not exist in Aquarius yet.

calina-c commented 3 years ago

@trentmc @alexcos20 @AnaLoznianu Do you guys think we can discuss this one during our grooming meeting today?

mihaisc commented 3 years ago

Also for aquarius/provider/subgraph i would suggest to partially automatize the release a bit. What had in mind is something like : when a release is made an issue is automatically created with the one who made the release (or the whole team from that repo) , Marian and someone from the market (maybe me and/or Matthias ). On that issue we need to figure out if there are breaking changes in the new release and sync the deployment of the new release with the market.

Example flow for aqua release :

The purpose of the issue is to just have a common place to track all these and not forget deployments.

trentmc commented 3 years ago

We talked about this issue in BE mtg today. We're not going to fully automate, the brittelness isn't worth the effort.

I believe we decided on (a) close this issue (b) have a specific issue for aqua (c) have a specific issue for provider.

Did I remember that correctly?