You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our setup is actually compatible with Java 17 now, but we're not yet ready to make the move. Nevertheless, we should not require any devs with only Java 17 to download Java 11 exclusively for TM, but with the caveat that the officially used language is still Java 11 and thus newer language features are not to be used.
We can adopt a newer version of Contributor Covenant instead of an older version 1.4 that we are currently using.
Although, admittedly, this is more of a formality than anything else.
We can add SECURITY.md to allow a more native integration for vulnerability reports.
With GitHub Discussions becoming the main communication channel, the previous way of using issue tracker is now discontinued. All related instructions need to be updated.
There are also more parts of the documentation referring to outdated practices; those need to be updated.
The text was updated successfully, but these errors were encountered:
…cumentation (#12358)
* Add placeholder index.html
* Update troubleshooting guide
* Add preliminary JDK 17 support
* Update code of conduct to use latest version
* Add SECURITY.md
* Update RolesAndTechnologies to simple table
* Update workflow to sequence diagram
* Update outdated versions of design diagrams
* Fix outdated process descriptions
* Retire `t-*` label group
* Move help request from issue tracker to discussion forum
localhost:8080
returns 404/403,api-output
is missing, front-end compilation error after pullingmaster
branch.teammates/docs/setting-up.md
Line 47 in 9d0dfa4
There are also more parts of the documentation referring to outdated practices; those need to be updated.
The text was updated successfully, but these errors were encountered: