-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
How about a new release? #907
Comments
Indeed that would make a lot of relevant changes, especially for users that take the Appimages. |
I agree that there should be a new release soon |
Yeah, definitely a good idea to do one soon, especially with the fixes and features that have been added/updated since v2.2.2 EDIT: Maybe perhaps it could be v2.3, as it's not major enough to make it v3.0.0, but not small enough to count as a maintenance release. Just a thought though |
At the very least it will squash a ton of bug reports that only tested against 2.2.2 :) |
I will need to dig into diff at some point but I don't think there is actually any new "feature", which is what the middle number has been used for on this repo so far. I'll add a tasklist to this issue's desc so we can track what's needed before doing this. |
Done. If anyone wants to help out, especially with the build targets stuff... As for the changelog, I'll probably take a weekend off other projects and dig into it. I don't think the commit messages are sufficiently similar to automate this process - maybe i'll take the opportunity to install komit. |
ContributorsThanks to ~/dev/edex-ui$ git shortlog -sne v2.2.2..HEAD So after some cleaning to remove duplicates, here are the contributors by contributions: GitSquared, Surge, qsniyg, wrac4242, D4rkia, Bodo Graumann, Emir Sarı, Freddie Runnding, Ivan Torres Fally, Jabster28, Le Barde, Maxim Mazurok, Michael de Silva, Nikhil, Niklas Arndt, Val, shine, theunbound, timescam. And best contributor: Dependabot with 129 contributions :-) ChangelogThanks to git-changelog, I was able to generate a changelog. Here it is: changelog_edex.txt If I remove the bots' commits:
If that helps :-) |
Wish GitHub had a way to separate bots and human contributors in the lists...
It does, thanks a lot!! |
On the topic of changelogs, if we were to use a commit standard such as conventional commits. we'd be able to use packages such as standard-version or release-please to automate changelogs and what not for releases |
Indeed, I've been using conventional commits in more recent projects and even developed a commit message helper for it. I think we're going to transition this repo after this release, that'll be a good start for saner CI practices from now on. |
Oh, komit looks cool! Does it skip the prompt if you've already added a commit message? I don't think things like GitKraken or VSCode would work when committing otherwise. |
No but you can just ctrl-c. It's pretty barebones, there's a lot of cool feats I could add to it but didn't find the time to. I also use Vim and git on the CLI so... I unfortunately don't have much experience with modern GUI workflows. |
|
The release is ready but I'm waiting on more info about a security issue downstream, expected ETA tomorrow evening (CET). |
And we're gold! Thanks to everyone involved. Will cleanup some stuff and close this, release will be up in a few minutes at https://github.com/GitSquared/edex-ui/releases/tag/v2.2.3 |
@GitSquared is the homebrew repo updated automatically? it still says v2.2.2 for me... EDIT: No it isn't, I'll update it now. |
Thanks! Forgot about this one. Homebrew/homebrew-cask#93788 |
On May 19, 2019 I released v2.2.2, an emergency release branched out from what was already supposed to be v3, to patch a security issue.
Life happened, and I never got around to finishing the remote monitoring feature that was supposed to be the key change in v3... And now we're in this weird situation where the latest release is unsupported and everyone interested has to go run the thing from source. And the diff is only growing...
The situation as described in #769 hasn't changed, but, out of respect for the 20+ contributors who've contributed a patch since the latest release and the 30k unique monthly visitors to this repository... I'm starting to think I should release a v2.2.3.
Any thoughts on this?
(Pinging some recent contributors and active commenters: @Animus-Surge @wrac4242 @lebarde )
New release to-do list:
(check Big Sur compat...)Can't support apple silicon yet.v3.0.0-pre
The text was updated successfully, but these errors were encountered: