-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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.20 #23072
Comments
I'll start with my plans:
|
Mine
|
This comment was marked as resolved.
This comment was marked as resolved.
|
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 hope that #20956 gets finally merged into 1.20. I also plan to make existing PRs ready to merge. For new PRs I think I will do mostly minor stuff like new APIs. I also plan to rework the Forks page. I had this Plan for quite a while since I have read a blogpost that talks about, how hard it is to find active Forks on GitHub. Since than, GitHub has made a new Forks Page, so I think it's time to do this also in Gitea, but I don't know if I get it ready before 1.20. |
Hi all,
Gitea
v1.19.0-rc0
has been released.We have created the
release/v1.19
branch accompanied by thev1.20.0-dev
tag and are now usingmain
for1.20
development.As always, this issue is intended to show what you can expect from the next version.
Important
This summary is for things you plan to do yourself, not things you want other people to do.
Other comments will be hidden.
Schedule
Gitea
1.20
is currently set to enter feature freeze on 2023-05-28 23:59 UTC, so in the end of May.This deadline is at the moment only a rough estimate and might change in the future.
Previous Plans
BTW: This is a contribution plan issue, any off-topic comment will be hidden. Please go to the special issue or open one to discuss your idea.
The text was updated successfully, but these errors were encountered: