Skip to content

Commit

Permalink
version 3.11
Browse files Browse the repository at this point in the history
  • Loading branch information
@ultrabug
ultrabug committed Jul 7, 2018
1 parent e4125c8 commit e3a189b
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 1 deletion.
14 changes: 14 additions & 0 deletions CHANGELOG
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,20 @@
version 3.11 (2018-07-05)
* py3.notify_user: add support for title and icon parameters to tune notifications, by @cyrinux
* new gitlab module: to powerfully manage your gitlab notifs/todos, by @lasers
* new wwan network manager module, by @cyrinux
* arch_updates module: update documentation to include the pacman-contrib requirement by @markrileybot
* diskdata module: fix stats computation, fixes #1373 by @scotte
* file_status module: add support for several paths with new format options, by @cyrinux
* hddtemp module: workaround for hddtemp byte bug, by @lasers
* net_rate module: handle non-existent interfaces better, fixes #1377, by @scotte
* sysdata module: use py3.format_units, by @simon04
* whatismyip module: replace freegeoip.net which has move and now require an api key, by @cyrinux


version 3.10 (2018-05-21)
* fix pip installation reported on #1351 by @lainiwa


version 3.9 (2018-05-14)
* added --disable_click_events (-m) option to disable all click events, by @jamethy
* allow executing shell code in the config using shell(), by @girst
Expand Down
2 changes: 1 addition & 1 deletion py3status/version.py
View file
Original file line number Diff line number Diff line change
@@ -1 +1 @@
version = '3.11_rc0'
version = '3.11'

3 comments on commit e3a189b

@lasers
Copy link
Contributor

@lasers lasers commented on e3a189b Jul 8, 2018 •
edited
Loading

Choose a reason for hiding this comment

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

@ultrabug Greeting, I have a solution. Ugly, but speedy. Hear me out.

Let me do what I want for py3status version 3.12. I aim to close many issues and pull requests as I can for a day.

Some things won't be merged since I request a feedback from your friend.
Some things would be new, but I do not expect any problems with merging.
Some things would be rage-inducing, but would close an issue or two.
Some things we could merge and let users report bugs.
Some things I would like to go through again... Those won't be merged.

Some configs will be dropped because of transference between formats, missed backward compatibility, or conflicts. However, this would simplify things more because we would have fewer issues, pull requests and bugs. Users would be exposed with new changes... eg, more colors, more configs, more things to customize, and even the new modules too.

After py3status version 3.12, you can delist me from collaborators. And when my pull requests gets zeroed out (definitely not in 3.12), you can block me for contributing too much to this project. I think it would make your friend happy. Ecstatic, even. 😁

This should happen soon so we can release 3.12 next day... as to skip out on having to deprecate (missed) plural path/paths inconsistency and for me to clear out things I'm finished with, but sometimes still perform idle tweaks on. Caveats: Post-reviews and not reverting.

TL;DR: Can I haz 3.12? Collaborator for a day?

@maximbaz
Copy link
Contributor

Choose a reason for hiding this comment

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

@ultrabug & @tobes, given how much value @lasers has already brought to py3status, I think you should really consider giving him permanent collaborator permissions and letting him cleanup the PRs backlog. It feels sad seeing the amount of open issues and PRs, and @lasers since has time and energy to actively maintain the project, I believe we should give him the opportunity.

This is a responsibility, but I think @lasers can handle it, he is already familiar with all the concepts and style guides used in py3status.

Finally, I simply prefer using projects with active development and frequent updates. Even if you (or anyone) spot an issue in a PR that was merged a week ago, it's very easy to improve upon it in a new PR, or in a worst case revert the offending commit, and release a new version.

@ultrabug
Copy link
Owner Author

Choose a reason for hiding this comment

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

Hello guys, sorry for the late reply. I released 3.11 just before going for a bit of vacation.

@lasers I trust and value you very much even if my response time is not the best, once again I apologize for this. I hear what you say @maximbaz and for full disclosure @cyrinux has told me something similar.

I will not do collaborator status for a day, either you have the rights or you don't. This is a relationship that needs to be discussed directly as we did with @tobes before he became collaborator.

That's why I think github is not the place for this conversation to happen. IRC is, and I will be very pleased to have a chat with you there.

Please try to be around and ping me there @lasers we'll sort this very quickly. We just need to "meet and commit together" 👍

Kindly

Please sign in to comment.