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

[viceice]

Is v1.22 already freezed? I've a small improvement for the nuget api with integration test.

• Support nuspec manifest download for nuget packages #28921

[denyskon]

@viceice No, we currently schedule the feature freeze for mid February. With some luck your PR should be merged until then :)

[zokkis]

Is it necessary to suggest changes for the new version here?
If yes, I would like to see #29122 in the new Release

[delvh]

1. No, it's not necessary
2. I am trying to get both of your recent PRs merged into 1.22 (especially Show depending and blocked PRs in the PR list #29117 since that one is an essential UI improvement). However, we need a second approver as well.

[sahinakkaya]

Is there a chance these two PR to be included in 1.22? #29191, #29210
I think they'll do good with Contributors graph.

[sameer-m-dev]

Hi, not sure if the v1.22 has been frozen or not, but by any chance do we also have a possibility to merge
#26673, this seems like a good change to have to add more customizability to Actions. Would love to help if any is required to get this merged

[delvh]

Ah, almost forgot to announce it here:

[delvh]

Gitea will enter feature freeze for 1.22 on Sunday, March 3, 2024 23:59 UTC.
We aim to release 1.22.0-rc0 shortly after.

Major improvements already include :

• Child PRs get retargeted once the parent PR has been merged
• Contributors Graph of a repo
• Files show the latest commit changing this file
• Commits prefixed with [skip ci] are not run in Gitea Actions
• Support for SHA256 repos
• New merge style: fast-forward only
• new and improved markdown syntax for writing alerts (Tip, Note, Warning, …)

Until then, everything that is merged will be included in 1.22

[theoludwig]

Why this issue have been unpinned? @silverwind
Also what is the state of v1.22? Still no Release candidate?
It seems like the v1.23 milestone has already started: https://github.com/go-gitea/gitea/milestone/159, but from what I see, there are no separations of branch between v1.22 and v1.23? All PRs land on main branch.
Whereas usually, if I understand correctly, you create a release/v1.22 from main, and then from there main becomes v1.23, and v1.22 is in feature freeze, but it seems like, it is not the case for this release?

[silverwind]

Why this issue have been unpinned

Because I think pinned issues should better be reserved for "common issues", so people don't open so many duplicate issues, which was a problem in the last couple of weeks.

[techknowlogick]

@theoludwig the branch is created when the first rc is cut.

[tulzke]

When is the first rc planned?

[techknowlogick]

@tulzke rc0 was released a few hours ago.

[techknowlogick]

As rc0 of 1.22 is now out I will now close/lock this thread. Plans for 1.23 can be listed in the new thread (once it is created)