Skip to content

Commit 1de30e0

Browse files
authored
Update README.md
Better callout and strikethrough for clarity
1 parent a76733d commit 1de30e0

1 file changed

Lines changed: 29 additions & 19 deletions

File tree

README.md

Lines changed: 29 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,48 @@
1-
# Since the release of Processing 3.5.4 in January 2020, development has moved to [a new repository](https://github.com/processing/processing4/).
2-
Using a [4.0 release](https://github.com/processing/processing4/releases) (even an alpha or beta version) is recommended if you find an issue. To avoid confusion, this repo will remain open at least until a 4.0 release is the default download at https://processing.org/download. We chose to move to a new repository so that we could clean out old files accumulated over the last 20 years.
1+
2+
3+
>[!WARNING]
4+
> # Development has moved to [a new repository](https://github.com/processing/processing4/).
5+
6+
Since the release of Processing 3.5.4 in January 2020, development has continued in a new repository: [processing/processing4](https://github.com/processing/processing4/).
7+
8+
We chose to move to a new repository so that we could clean out old files accumulated over the last 20 years.
9+
10+
To report bugs or request features, please open a [new issue](https://github.com/processing/processing4/issues/new/choose) on the Processing 4 repository.
11+
312
<!-- Is there not a better way to do a callout box? -->
13+
<!-- Yes there is! -->
414

5-
Processing
15+
~~Processing~~
616
==========
717

8-
This is the official source code for the [Processing](http://processing.org) Development Environment (PDE),
9-
the “core” and the libraries that are included with the [download](http://processing.org/download).
18+
~~This is the official source code for the [Processing](http://processing.org) Development Environment (PDE),
19+
the “core” and the libraries that are included with the [download](http://processing.org/download).~~
1020

11-
__I've found a bug!__
12-
Let us know [here](https://github.com/processing/processing/issues) (after first checking if someone has already posted a similar problem).
21+
~~__I've found a bug!__~~
22+
~~Let us know [here](https://github.com/processing/processing/issues) (after first checking if someone has already posted a similar problem).
1323
If it's a reference, web site, or examples issue, take that up with folks [here](https://github.com/processing/processing-docs/issues).
1424
There are also separate locations for [Android Mode](https://github.com/processing/processing-android/issues), or the [Video](https://github.com/processing/processing-video/issues) and [Sound](https://github.com/processing/processing-sound/issues) libraries.
15-
The [processing.js](http://processingjs.org) project is not affiliated with us, but you can find their issue tracker [here](https://github.com/processing-js/processing-js/issues).
25+
The [processing.js](http://processingjs.org) project is not affiliated with us, but you can find their issue tracker [here](https://github.com/processing-js/processing-js/issues).~~
1626

17-
__Locked Issues__
18-
Where possible, I've started locking issues once resolved. This helps reduce the amount of noise from folks adding to an issue that's been closed for years. Because this project has existed for a long time and we have thousands of closed issues, lots of them may sound similar to an issue you're having. But if there's a new problem, it'll be missed if it's lost in a comment added to an already closed issue. I don't like to lock issues because it cuts off conversation, but it's better than legitimate problems being missed. Once an issue has been resolved for 30 days, it will automatically lock.
27+
~~__Locked Issues__
28+
Where possible, I've started locking issues once resolved. This helps reduce the amount of noise from folks adding to an issue that's been closed for years. Because this project has existed for a long time and we have thousands of closed issues, lots of them may sound similar to an issue you're having. But if there's a new problem, it'll be missed if it's lost in a comment added to an already closed issue. I don't like to lock issues because it cuts off conversation, but it's better than legitimate problems being missed. Once an issue has been resolved for 30 days, it will automatically lock.~~
1929

20-
__That [processing-bugs](https://github.com/processing-bugs) fella is suspicious.__
30+
~~__That [processing-bugs](https://github.com/processing-bugs) fella is suspicious.__
2131
The issues list has been imported from Google Code, so there are many spurious references
2232
amongst them since the numbering changed. Basically, any time you see references to
2333
changes made by [processing-bugs](https://github.com/processing-bugs), it may be somewhat suspect.
2434
Over time this will clean itself up as bugs are fixed and new issues are added from within GitHub.
25-
Help speed this process along by helping us!
35+
Help speed this process along by helping us!~~
2636

27-
__Please help.__
37+
~~__Please help.__
2838
The instructions for building the source [are here](https://github.com/processing/processing/wiki/Build-Instructions).
29-
Please help us fix problems, and if you're submitting code, following the [style guidelines](https://github.com/processing/processing/wiki/Style-Guidelines) helps save me a lot of time.
39+
Please help us fix problems, and if you're submitting code, following the [style guidelines](https://github.com/processing/processing/wiki/Style-Guidelines) helps save me a lot of time.~~
3040

31-
__And finally...__
32-
Someday we'll also fix all these bugs, throw together hundreds of unit tests, and get rich off all this stuff that we're giving away for free. But not today.
41+
~~__And finally...__
42+
Someday we'll also fix all these bugs, throw together hundreds of unit tests, and get rich off all this stuff that we're giving away for free. But not today.~~
3343

34-
So in the meantime, I ask for your patience,
44+
~~So in the meantime, I ask for your patience,
3545
[participation](https://github.com/processing/processing/wiki/Project-List),
36-
and [patches](https://github.com/processing/processing/pulls).
46+
and [patches](https://github.com/processing/processing/pulls).~~
3747

38-
Ben Fry, 20 January 2019
48+
~~Ben Fry, 20 January 2019~~

0 commit comments

Comments
 (0)