6bb6309a4e
* Release number is v7.0.0+1.22.0 and following semantic versioning * Remove the workflow page which is no longer needed as: * it is implicitly understood pull requests go to the default branch * testing requirements are documented in the testing.md page * Explain how to cut a release and set the tag in forgejo-integration for proper numbering of the test releases that come out of the development branch Refs: https://codeberg.org/forgejo/forgejo/pulls/2448
1.1 KiB
| title | license |
|---|---|
| next.forgejo.org | CC-BY-SA-4.0 |
This is the developer documentation for Forgejo Next, covering technical details for Forgejo contributors. Go to end-user documentation for service overview.
https://next.forgejo.org, also known as Forgejo Next, is Forgejo's official testing and demonstration instance. The specific version of Forgejo running on this instance varies depending on the status of the latest release branch.
Typically, the instance will be running the daily build straight from the
forgejo branch, meaning it contains experimental code that will be
included in the next major version of Forgejo.
When a release branch is created and release candidates are posted,
Forgejo Next will be switched to the latest release candidate. Release
candidates are to be deployed until a stable release is
available. next.forgejo.org will then be upgraded back to the
forgejo branch.
For details on the hardward from which it is running, checkout the section in the infrastructe documentation.