GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — Added blurb about 5.0 dev and 4.x by catilac · Pull Request #1576 · processing/processing4 Conversation
|
| > - **New features and 5.0 work:** open pull requests against `main`. | ||
| > - **Bug fixes for Processing 4:** open pull requests against the [`4.x`](https://github.com/processing/processing4/tree/4.x) branch. It starts from the [`processing-1435-4.5.7`](https://github.com/processing/processing4/releases/tag/processing-1435-4.5.7) release, and all 4.x patch releases will come from it. |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
| > - **New features and 5.0 work:** open pull requests against `main`. | |
| > - **Bug fixes for Processing 4:** open pull requests against the [`4.x`](https://github.com/processing/processing4/tree/4.x) branch. It starts from the [`processing-1435-4.5.7`](https://github.com/processing/processing4/releases/tag/processing-1435-4.5.7) release, and all 4.x patch releases will come from it. | |
| > - **New features and 5.0 work:** Open pull requests against `main`. | |
| > - **Bug fixes for Processing 4:** Open pull requests against the [`4.x`](https://github.com/processing/processing4/tree/4.x) branch. It starts from the [`processing-1435-4.5.7`](https://github.com/processing/processing4/releases/tag/processing-1435-4.5.7) release, and all 4.x patch releases will come from it. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I can guess what does
It starts from the
processing-1435-4.5.7release
mean but I believe the text can be further clarified.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I'm looking at it, and I think that maybe just removing that detail would make sense? People only need to understand the purpose of the 4.x branch.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| > - **New features and 5.0 work:** open pull requests against `main`. | ||
| > - **Bug fixes for Processing 4:** open pull requests against the [`4.x`](https://github.com/processing/processing4/tree/4.x) branch. It starts from the [`processing-1435-4.5.7`](https://github.com/processing/processing4/releases/tag/processing-1435-4.5.7) release, and all 4.x patch releases will come from it. |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I can guess what does
It starts from the
processing-1435-4.5.7release
mean but I believe the text can be further clarified.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| > - **New features and 5.0 work:** open pull requests against `main`. | ||
| > - **Bug fixes for Processing 4:** open pull requests against the [`4.x`](https://github.com/processing/processing4/tree/4.x) branch. It starts from the [`processing-1435-4.5.7`](https://github.com/processing/processing4/releases/tag/processing-1435-4.5.7) release, and all 4.x patch releases will come from it. | ||
| > | ||
| > Not sure which branch to use? Ask in the issue thread or on [Discord](https://discord.processing.org). |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Should we mention devs-chat channel?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Resolved.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.