Skip to content

Commit

Permalink
Release version 2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
@raxod502
raxod502 committed Jul 18, 2020
1 parent 0a069e9 commit 51b75f4
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 4 deletions.
3 changes: 2 additions & 1 deletion CHANGELOG.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog].

## Unreleased
## 2.0 (released 2020-07-18)
### Breaking changes
* The way to dynamically generate the candidate list has changed.
Instead of rebinding `selectrum-preprocess-candidates-function` and
Expand Down Expand Up @@ -167,6 +167,7 @@ The format is based on [Keep a Changelog].
[#42]: https://github.com/raxod502/selectrum/issues/42
[#44]: https://github.com/raxod502/selectrum/pull/44
[#49]: https://github.com/raxod502/selectrum/issues/49
[#50]: https://github.com/raxod502/selectrum/pull/50
[#52]: https://github.com/raxod502/selectrum/issues/52
[#53]: https://github.com/raxod502/selectrum/issues/53
[#54]: https://github.com/raxod502/selectrum/pull/54
Expand Down
4 changes: 2 additions & 2 deletions selectrum-helm.el
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@
;; Created: 15 Apr 2020
;; Homepage: https://github.com/raxod502/selectrum
;; Keywords: extensions
;; Package-Requires: ((emacs "25.1") (helm "3.6.1") (selectrum "1.0"))
;; Package-Requires: ((emacs "25.1") (helm "3.6.1") (selectrum "2.0"))
;; SPDX-License-Identifier: MIT
;; Version: 1.0
;; Version: 2.0

;;; Commentary:

Expand Down
2 changes: 1 addition & 1 deletion selectrum.el
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
;; Keywords: extensions
;; Package-Requires: ((emacs "25.1"))
;; SPDX-License-Identifier: MIT
;; Version: 1.0
;; Version: 2.0

;;; Commentary:

Expand Down

5 comments on commit 51b75f4

@raxod502
Copy link
Member Author

Choose a reason for hiding this comment

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

@clemera I have released version 2.0. I try to make releases of all of my packages approximately once every three months, and the time was up. My strategy is typically to start by including every commit older than a month since the last release, and then backport any critical bugfixes since then, although I may deviate from this procedure according to the situation. The goal is to produce snapshots that have a high probability of not having any major (new) bugs, on a relatively timely basis. I fixed up the changelog on master so that the changes which were not included in the release are now in the "Unreleased" section, and published on the releases page. Let me know if you have any questions :)

@clemera
Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks, I haven't dealt with Github releases yet and I learn from your explanations! Do you copy the changelog over to the release page or is that somehow automated?

@raxod502
Copy link
Member Author

Choose a reason for hiding this comment

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

Unfortunately, the release process is not automated. It's pretty straightforward, though, because the CHANGELOG is already formatted the same as the release page is supposed to be. The main annoyance is that on the release page, like in GitHub comments, line breaks are treated as hard, so I have to un-fill all of the paragraphs. I use atomic-chrome to do that in Emacs.

Glad I can be helpful!

@clemera
Copy link
Collaborator

Choose a reason for hiding this comment

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

I read that one can trigger releases via the command line so automating this from within Emacs should be possible.

@raxod502
Copy link
Member Author

Choose a reason for hiding this comment

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

That would be pretty cool. Maybe someday it will end up in Forge...

Please sign in to comment.