-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plans for Gitea 1.21 #25123
Labels
type/summary
This issue aggregates a bunch of other issues
Milestone
Comments
I'll start with my plans:
somewhere on the back of my TODO list |
I'm pretty new to the codebase but I'm going to try my hand at implementing:
|
|
This comment was marked as off-topic.
This comment was marked as off-topic.
Backlog
|
|
|
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I am currently working on
|
Closed
Closing as 1.21rc0 released, replaced by #27194 :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi all,
Gitea
v1.20.0-rc0
has been released.We have created the
release/v1.20
branch accompanied by thev1.21.0-dev
tag and are now usingmain
for1.21
development.As always, this issue is intended to show what you can expect from the next version.
Schedule
Gitea
1.21
is currently set to enter feature freeze on 2023-09-03 23:59 UTC, so in the beginning of september.This deadline is at the moment only a rough estimate and might change in the future.
Previous Plans
This summary is for things you plan to implement yourself, not things you want (from other people).
Wishes and other offtopic comments will be hidden.
The text was updated successfully, but these errors were encountered: