-
-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Update request: furnace 0.6pre18 → 0.6 #259093
Comments
Sounds interesting, link? |
On-topic stuff:
r-ryantm update PRs don't happen instantly, I'm not sure if the exact timing is documented anywhere.
Still disagree with the idea. Our 23.11 release is starting to be planned, so that one will likely end up with a proper 0.6 release. If upstream doesn't do the same year-long, feature-packed pre-release hell again then I'd be fine with backporting patch releases with fixes onto 23.11. Off-topic stuff:
Read #41448 for past stances & discussions about this, and where future discussions about this are supposed to be done.
Only similar situation I can think of is volth, I'm not sure if that can be considered a false ban though? Unfortunate nonetheless though. |
@cafkafk iirc joepie91 got this sledgehammer treatment. Here's a link to someone else who got dragged through hell: https://nrk.neocities.org/articles/miserable-state-of-github-moderation
@OPNA2608 don't worry, from what i hear 0.7 is going to be mostly minor patches and work for hardware export, so i doubt tildearrow will machine-gun prereleases for a while. |
For some reason this update did not add an automatic pull request...
Now that the update spam is over, I wonder if it might be time to update the release channel as well.
Notify maintainers
@OPNA2608
PS: I am once again asking y'all to prepare an escape plan from github - what with repeated false bans, including some of our members, that are so strong they are more-or-less removed from history, and unnerving serves of direction form host to social to ai... can't trust this site.
Note for maintainers: Please tag this issue in your PR.
The text was updated successfully, but these errors were encountered: