-
-
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.23 #30261
Labels
type/summary
This issue aggregates a bunch of other issues
Comments
I plan to work on:
|
I expect to work on:
|
|
|
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
Gitea
v1.22.0-rc0
has been released.We have created the
release/v1.22
branch accompanied by thev1.23.0-dev
tag and are now usingmain
for1.23
development.As always, this issue is intended to show what you can expect from the next version.
Schedule
Gitea
1.23
is currently set to enter feature freeze on 2024-06-15 23:59 UTC, so in the middle of 2024.This deadline is at the moment only a rough estimate and might change in the future.
Roadmap
UI Improvements
The target is retiring Jquery & Fomantic UI and introduces some realtime updating in some pages instead of reload the whole page.
Actions Improvements
Projects Improvements
Packages Improvements
Translation
Try to use another format to store the translation files.
Performance
Improve the pull request details page loading performance.
Administration
Support change frequently changes configurations from the admin panel.
Others
Previous Plans
This summary is for things you plan to implement yourself, not things you want (from other people).
Wishes and other off-topic comments will be hidden.
The text was updated successfully, but these errors were encountered: