Plans for Gitea 1.22

[delvh]

Hi all,

Gitea v1.21.0-rc0 has been released.
We have created the release/v1.21 branch accompanied by the v1.22.0-dev tag and are now using main for 1.22 development.
As always, this issue is intended to show what you can expect from the next version.

Schedule

Gitea 1.22 is currently set to enter feature freeze on 2023-12-17 23:59 UTC, so at the end of 2023.
This deadline is at the moment only a rough estimate and might change in the future.

Previous Plans

• Plans for Gitea 1.21 #25123
• Plans for Gitea 1.20 #23072
• Plans for Gitea 1.19 #21598
• Plans for Gitea v1.18 #20022
• Plan of Gitea v1.17 #18345
• Plan of Gitea v1.16 #16429
• Discussion of v1.15.x Roadmap #14477

⚠️ Important

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.

[delvh]

I'll start with my plans:

• Reviewing a lot of PRs (as always)
• Refactorings. Many of them. There are still way too many refactorings that need to be done at one point.
• Improve the documentation

So, overall, it will be a fairly feature free release from my side.
However, I'll gladly review features to get them merged.
Current contenders for it are

• Add Audit Trail/Logging #24257
• enhancement of compare feature #25322
• Implement contributors graph #25439

[denyskon]

I'll try to review some of the open & forgotten PRs, specially:

• Add support for forking single branch #25821
• Add milestone labels #20620
• Support repo license #24872
• client certificate validation #21221

For my own work, I plan to implement details pages for organisations and repo list and reverting of multiple commits.

Also of course as always, mobile vievport fixes and refactorings :)

I thought of taking a look at ways to switch to a new translation file format and cleaning up translations, but I don't know if I'll have time for that.

[silverwind]

• Introduce either unocss or tailwindcss
• Remove more fomantic
• Finish New commits list #24423
• Finish Support rendering openapi and swagger documents #26802

[sahinakkaya]

At the start of this month, I realized due date for v1.21 milestone is end of month and I thought maybe I can find some time to finish #25439. Today I saw that my PR is moved to v1.22 milestone. Is there any chance that we finalize it before end of month and have it merged? @delvh Would it worth it if I rush? :)

[delvh]

No, we've been in feature freeze for 1.21 for a month now.
I'll try to get it into 1.22, but 1.21 is absolutely impossible now.

[lunny]

• Fix bugs
• Improve Actions, make Gitea CI can PASS.
• Possible Add support to import repository data from an exported data of Github #18165
• Renderers Framework based on Docker/GRpc
• WIP: Reduce using reporootpath directly #25071

[Hypnotist1148]

Hey, how about global Teams instead of only Organization Teams?
Would be the first step to support LDAP group importing in the future, without the need to manually map a LDAP group to a specific Team in an Organization, would be an absolute Gitlab killer feature for corporate environments.

[denyskon]

@Hypnotist1148 Please open an Issue (or look if there already is one). This Issue is only for communication about what you are going to do.

[caixiangibm]

hi, when will the final forma gitea:1.21.0 image to be released in docker hub?
Is it possible for it to use go1.21.3 (released 2023-10-10) includes a security fix to the net/http package?

[delvh]

1. Wrong issue to discuss that.
2. The docker image uses the newest go 1.21 at the time of pulling
3. Not before we haven't released 1.21.0. Current plan is somewhere between the weekend and next week.