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

Fully automated release process #93

Closed
1 of 9 tasks
aslakhellesoy opened this issue Nov 23, 2016 · 3 comments
Closed
1 of 9 tasks

Fully automated release process #93

aslakhellesoy opened this issue Nov 23, 2016 · 3 comments
Labels
⌛ stale Will soon be closed by stalebot unless there is activity 🔧 build Related to build / release process

Comments

@aslakhellesoy
Copy link
Contributor

aslakhellesoy commented Nov 23, 2016

The scripts/release script does a whole deal, but there is still room for improvement:

  • Tag manyrepos with tag vX.Y.Z
  • Tag monorepo with tag lib-vX.Y.Z
  • Run each lib release from scripts/release
  • Verify that each lib has an uptodate CHANGELOG
  • Add scripts/update-changelog lib based on git-release-notes
  • Document commit message format for release notes
  • Automate maven promotion - see this gist
  • Copy and Include a general Release.mk file in each manyrepo (languages-specific)
  • Add script to bump the version in misc build files.
@aslakhellesoy aslakhellesoy added the 🔧 build Related to build / release process label Nov 23, 2016
@stale
Copy link

stale bot commented Nov 8, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the ⌛ stale Will soon be closed by stalebot unless there is activity label Nov 8, 2017
@stale
Copy link

stale bot commented Nov 15, 2017

This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective.

@stale stale bot closed this as completed Nov 15, 2017
@lock
Copy link

lock bot commented Nov 15, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
⌛ stale Will soon be closed by stalebot unless there is activity 🔧 build Related to build / release process
Projects
None yet
Development

No branches or pull requests

1 participant