-
Notifications
You must be signed in to change notification settings - Fork 73
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
Release scheduling #440
Comments
Because #419 needs to be fixed before Nov. 20, we should roll-out a new CRAN release of styler. Currently, the draft of styler 1.1.0This release introduces new features and is fully backward-compatible. It also Major Changes
Minor Changes
|
@krlmlr current version number is 1.0.2. Should we go for 1.1.0 for the new release since we have quite a few new features? |
1.1.0 seems fine (and is on CRAN now?). |
@krlmlr what do you think should we go for another release soon? I think there are some substantial improvements according to NEWS.md and the last release was ~4 months ago. From 1.1.1 -> 1.2? I think it's a bit unfortunate but the caching feature #538 probably won't make it into that release because of a pending request to dependency R.cache. Maybe we need to resolve that otherwise though. styler devBreaking changes
New features
Minor improvements and fixes
|
I do like the caching idea a lot. We could merge, bearing in mind that we pay some cost for these empty files, and think about optimization later? I'd say 1.2.0. |
Well, I am not sure if it would cause some problems and edge cases when upgrading from the first to the second version (although the idea was to isolate the cache for each version of styler, see #538). |
If the change makes it into R.cache, it should be back-compatible anyway. But I agree to wait for a bit -- release to CRAN, then merge #538 so that it gains a tiny bit more exposure. |
We also have #541 which we should fix. |
Don't think we need this open anymore. |
In this issue, I plan to discuss future release scheduling of styler for every upcoming release. The template for checks:
The text was updated successfully, but these errors were encountered: