| ... | ... | @@ -25,19 +25,19 @@ Throughout the entirety of this timeline, the IT team will use mailing lists, ec |
|
|
|
|
|
|
|
#### April-June 2024
|
|
|
|
|
|
|
|
* Send deprecation/shutdown reminder/notice to the Eclipse committers list.
|
|
|
|
* ~~Send deprecation/shutdown reminder/notice to the Eclipse committers list.~~
|
|
|
|
|
|
|
|
#### July-September 2024
|
|
|
|
|
|
|
|
* Audit existing sites for the presence of PHP code, and create helpdesk issues for those projects with a due date of December 2024
|
|
|
|
* ~~Audit existing sites for the presence of PHP code, and create helpdesk issues for those projects with a due date of December 2024~~
|
|
|
|
* As of August 2024 60% of projects still have some PHP code in their websites.
|
|
|
|
|
|
|
|
#### October-December 2024
|
|
|
|
|
|
|
|
* Re-run audit and remind outstanding projects directly
|
|
|
|
* Send deprecation/shutdown reminder/notice to the Eclipse committers list
|
|
|
|
* Schedule/run eclipse.dev PHP service brownouts
|
|
|
|
* Remove PHP support on eclipse.dev
|
|
|
|
* ~~Re-run audit and remind outstanding projects directly~~
|
|
|
|
* ~~Send deprecation/shutdown reminder/notice to the Eclipse committers list~~
|
|
|
|
* ~~Schedule/run eclipse.dev PHP service brownouts~~
|
|
|
|
* ~~Remove PHP support on eclipse.dev~~
|
|
|
|
|
|
|
|
#### January-March 2025
|
|
|
|
|
| ... | ... | |
