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.

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

Continues Delivery #143

Open
5 tasks
Siemienik opened this issue Jan 19, 2021 · 0 comments
Open
5 tasks

Continues Delivery #143

Siemienik opened this issue Jan 19, 2021 · 0 comments
Labels
accepted It is accepted to do

Comments

@Siemienik
Copy link
Owner

Siemienik commented Jan 19, 2021

Continues Delivery

Currently, all packages have their own versions system. This discrepancy creates many problematic situations in the cases of reporting issues and managing their versions. I'm curious to improve this process and made it automatic and uniform for all packages. That would be wonderful :)

TODO:

  • At first, uniform versions. All packages should have introduced uniform versions, same for all packages. That will be much easier to manage. Also, on the client user's (developer's) side, using packages in the same version guaranty all work perfectly together.
  • Secondly, one for all. One script should work for all. It should be placed in the main package.json. Then run npm version & npm publish for all packages. That makes publishing a new version much more convenient. Probably the workspace feature will work great for that point.
  • Then, develop branch. As this script will run automatically, it is required to introduce the develop, because I want to release new versions too often (that will be annoying for developers using our packages). So, all changes go into feature branches, then merged into the develop. Then not often than once a week, I will create PR into master, merge and release a new version.
  • Workflow: PR into master, a workflow scheduled once a week to check and create a PR from developing into master, and earlier bumping a version. To consider how to detect the level of the incremented version (patch or minor).
  • Workflow: publish version, workflow started when pushed into the master branch. Publish version into npm, and (proposal:) report it in social media (fi. twitter/linkedin/fb/dev.to/hn)
@Siemienik Siemienik added not ready yet Needs precision important Do it first labels Jan 19, 2021
@Siemienik Siemienik added accepted It is accepted to do and removed not ready yet Needs precision labels Jan 24, 2021
@Siemienik Siemienik changed the title [DRAFT] Introduce Continues Delivery Continues Delivery Jan 24, 2021
@Siemienik Siemienik removed the important Do it first label Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted It is accepted to do
Projects
Status: Accepted
Development

No branches or pull requests

1 participant