0.16.0 Release Plan
See original GitHub issueI just released 0.15.0 🎉 Thanks again to everyone contributing!
This issue will be used to track any overarching discussion and work related to 0.16.0
.
Scope
As always, everything discussed in this issue is subject to sudden change at my sole discretion. No promises or hard commitments 😃
All related issues will be tagged with the 0.16.0 Milestone.
Here’s a few things I’ve been thinking about (most don’t have an associated issue) as potential areas to work on next.
- Consider moving gitlint under PyCQA. Still not sure at this point (#134)
- Add
--commit
flag: #141 - Don’t have both
requirements.txt
and dependencies insetup.py
, deduplicate - User-defined
OutputFormatter
classes to allow users to specify the format of the output. Would allow us to easily implement #45 and #53.OutputFormatter
classes would just be found in the--extra-path
-
GitContext.config(name, default=None, use_cache=True)
method for easy access to git config (that is also cached). Optionally also provide a mechanism for easy fallback. E.g.default
can be a string and/or a lambda that implements more complex logic like returning from environment config. - New Rule: ConfigRule:
git config
commands- This can just be implemented as a commit rule that just runs a
_git
command (orGitContext.config
- see above) to pull the value and then compare it to a given regex. By using named rules, users can implement multiple of such rules.
- This can just be implemented as a commit rule that just runs a
- Respect git config
core.editor
for commit msg editing instead of only falling back tovim
if$EDITOR
isn’t set - gitlint github action
- Attempt to fix coveralls.io integration with Github Actions (see .github/workflows/checks.yml#L60-L66)
- Windows: work a bit on fixing existing issues
- Move to Poetry for packaging/building?
- Unit Tests: fix running on Windows, try again 😃
Timeline
As always, no specific timeline, but probably in the new year (2021).
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
0.16 Development and Release Plan · crawl/crawl Wiki · GitHub
This page is for managing short and middle term development planning. Not everything that's on here is going to get into 0.16, or...
Read more >Eclipse OpenJ9™ 0.16.0
Milestone plan · Release notes. Compatibility: The aim is to provide a fully featured VM compatible with the Java Platform, Standard Edition for...
Read more >Vector v0.16.0 release notes
The Vector team is pleased to announce version 0.16.0! Be sure to check out the upgrade guide for breaking changes in this release....
Read more >0.16 Release Plan - Elasticsearch - Discuss the Elastic Stack
Heya, 0.16 is just around the corner. Basically, master is pretty much feature complete, so, if you have time, take it for a...
Read more >Release 0.16.0 - TaskTrain
system-Subscription Expiration: Completes billing logic for expiring subscription and improves plan listing with descriptions and layout enhancements ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just released 0.15.1 🎉
@harens FYI, if you’re up for updating homebrew and macports (no pressure, super thanks!)
All done on my side. Thank you @jorisroovers for maintaining this amazing project! ⭐ Your work is greatly appreciated.
🍎 MacPorts: https://github.com/macports/macports-ports/commit/85f8bb5e31d4e0ac1d047ed8909e7d8bee26ef15 🍺 Homebrew: https://github.com/Homebrew/homebrew-core/pull/86892