-
Notifications
You must be signed in to change notification settings - Fork 313
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
Jim is away for a week =) #813
Comments
hi @jimsalterjrs, the following PR are reviewed/tested and can be merged right away if you like: |
should be safe too: #746 |
If one of these PRs involves the
I just put 2.1.0 on a new machine and confirm that Should I submit a PR? Thanks! |
@jimsalterjrs rebased #809, will rebase #622 after merge of the former because this will trigger an conflict. |
@phreaker0 #809 merged. |
@jimsalterjrs thanks, I rebased #622 |
#622 Merged. |
Thank you for merging all of these PRs @phreaker0 @jimsalterjrs Will there be an upcoming tag cut as well? |
#625 has also just been rebased by @0xFelix the author. any chance of a merge @phreaker0 ? |
@jimsalterjrs are you also planning to create a new release? the last one on github was 2 years ago, on April 1, 2021. |
Generally speaking, tends to be safe as kittens. @phreaker0 and I are the only ones with commit/merge privileges, and we have the explicit goal of keeping master as safe as we can between releases. Occasionally, one of us has merged a PR with a bug we didn't catch first... But I explicitly do all of my (pretty frequent) personal sanoid installations from master, so I generally catch any significant bugs in master pretty quickly when they appear. Btw, we released v2.2.0 today. :) |
Hi contributors and other folks!
We're pretty overdue for a great big merge party soon, but I'll be out of town for the next week (8th-15th). Anybody who's got a PR in (and @phreaker0 ), can we maybe set up a merge day sometime the week of the 16th-23rd? We'll want PR authors on hand to rebase patches as needed; sometimes accepting one PR invalidates another until rebase.
Thanks!
The text was updated successfully, but these errors were encountered: