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

docs(semantic-release): implement an automated changelog #139

Merged
merged 1 commit into from
Apr 24, 2019

Conversation

daks
Copy link
Member

@daks daks commented Apr 18, 2019

I think that all files are present. Please let me know if something is missing.
Also I don't know if there is some configuration to be done on the repo itself.


Updates by @myii and @n-rodriguez, moved from the comment below so that it shows up in the GitHub front-end.

Still a few remaining tasks to complete this properly (put these as issues?):

  • Merge the Changelog files into one (and maybe fill in more of the history?).
  • Update states list in documentation.
  • Use this content as the entry for release v1.0.0 (the one before semantic-release).
  • Upgrade the CI matrix to use the pre-salted images -- the current run takes over 20 minutes (over 45 minutes of total time).

@daks daks marked this pull request as ready for review April 18, 2019 10:16
@myii myii self-assigned this Apr 18, 2019
@myii myii requested a review from n-rodriguez April 21, 2019 03:04
@myii
Copy link
Member

myii commented Apr 21, 2019

Couple of things for now (which are related by release version number):

  1. This will need a FORMULA file added.
  2. Also need to decide the version number to "start" from.
    1. According to the spreadsheet, the comparative maturity of this formula is v0.16.0.
    2. However, there's already a CHANGELOG, which is indicating v1.1.0 or thereabouts -- there is a big jump in there, though -- and it hasn't been updated for years.

@n-rodriguez I hope you don't mind me requesting that you review this PR. We've already implemented semantic-release on a couple of formulas (mainly the template-formula) and it is working really well. However, it does require specific commit message formatting, so your input will be valuable.

@myii
Copy link
Member

myii commented Apr 21, 2019

@n-rodriguez Just to be clear, I'm not expecting you to go through the actual code changes as such, although you're welcome to comment on that as well. The main reason is to request your approval/disapproval regarding implementing semantic-release into this formula.

@n-rodriguez
Copy link
Member

@n-rodriguez I hope you don't mind me requesting that you review this PR.

no problem 👍

I'm not against the idea of semantic versioning and the semantic-release package.

About the version to start from, I'm not against a "reset' to 1.0.0 : the current changelog is meaningless, the formula is globally stable although it needs more documentation.

Some states are not documented and the pillar.example may need some more examples. I don't know about the tests, but it would worth to check them before we could release a true 1.0.0 version.

@n-rodriguez
Copy link
Member

About the release process : how does it work?

@myii
Copy link
Member

myii commented Apr 21, 2019

@n-rodriguez If you can join the #formulas channel in Slack, I can explain it to you in conversation. Otherwise, you can get the general gist starting from here: https://github.com/saltstack-formulas/template-formula/blob/master/docs/CONTRIBUTING.rst#commit-message-formatting.

@aboe76 aboe76 requested a review from myii April 22, 2019 06:34
Copy link
Member

@myii myii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the moment, the points made in this comment above will need to be resolved first. I've also noticed a couple of minor issues, which can be discussed when we start testing this in a separate fork.

@daks
Copy link
Member Author

daks commented Apr 23, 2019

Hi,

about the FORMULA file, isn't it auto-generated by the versioning script? How do we maintain the version number inside?
About the version number to publish, I have no idea what's the best: are actual numbers valid and used? If we don't want to mess with that, create a 2.0 can also be possible. Or a 1.2.

@myii
Copy link
Member

myii commented Apr 23, 2019

Just copying this over from our discussion on Slack:

@daks About the FORMULA file, the basic arrangement needs to be provided. Just borrow the one in template-formula and modify accordingly. Only the version number is updated automatically during the release process.
As for the version number to start from, then the spreadsheet suggests v0.1.6. However, the out-of-date Changelog suggests v1.1.0. Just put either for now and we can sort it out when finalising this PR.

@daks
Copy link
Member Author

daks commented Apr 23, 2019

FORMULA file added

FORMULA Outdated
version: 1.0rc
release: 1
minimum_version: 2016.11
summary: Template formula
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not Template formula.

BREAKING CHANGE: With the removal of all of the `.sls` files under
`template package`, this formula no longer supports the installation of
packages.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the whole Documentation section below.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As in, all the way to the end of the file. We're not setting up ReadTheDocs for this yet.

@@ -0,0 +1,21 @@
/*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this file.

docs/conf.py Outdated
@@ -0,0 +1,173 @@
# -*- coding: utf-8 -*-
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this file.

docs/index.rst Outdated
@@ -0,0 +1,20 @@
.. _index:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this file.

@daks daks force-pushed the semantic-changelog branch 3 times, most recently from 78c48e2 to 706f581 Compare April 23, 2019 17:30
@myii
Copy link
Member

myii commented Apr 23, 2019

@daks Thanks for all of your work with this. Great job!

@daks daks changed the title chore: implement an automated changelog and semantic versioning docs(semantic-release): implement an automated changelog Apr 24, 2019
@myii myii merged commit 9a97fe9 into saltstack-formulas:master Apr 24, 2019
@myii
Copy link
Member

myii commented Apr 24, 2019

@daks Merged, finally! The new release should be delivered in the next few minutes...

@saltstack-formulas-travis

🎉 This PR is included in version 1.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@daks
Copy link
Member Author

daks commented Apr 24, 2019

@myii thanks for your assistance

@myii
Copy link
Member

myii commented Apr 24, 2019

@daks You're welcome.

(Moved the rest of this comment to the very top comment in order to show the checklist items in the GitHub front-end).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants