Plans for Gitea 1.24 #13840

New Issue

GiteaMirror · 2025-11-02T10:54:48-06:00

GiteaMirror commented

2025-11-02 10:54:48 -06:00

Originally created by @lunny on GitHub (Dec 17, 2024).

Hi all,

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

Schedule

Gitea 1.24 is currently set to enter feature freeze on 2025-04-01 23:59 UTC, and released on 2025-04-25 23:59 UTC
This deadline is at the moment only a rough estimate and might change in the future.

Roadmap

Potential pull requests to be included in this release.

Previous Plans

⚠️ Important

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.

Originally created by @lunny on GitHub (Dec 17, 2024). Hi all, Gitea `v1.23.0-rc0` has been released. We have created the `release/v1.23` branch accompanied by the `v1.24.0-dev` tag and are now using `main` for `1.24` development. As always, this issue is intended to show what you can expect from the next version. ## Schedule Gitea `1.24` is currently set to enter feature freeze on <time datetime="2025-04-01 23:59+00:00">2025-04-01 23:59 UTC</time>, and released on <time datetime="2025-04-25 23:59+00:00">2025-04-25 23:59 UTC</time> This deadline is at the moment only a rough estimate and might change in the future. ## Roadmap Potential pull requests to be included in this release. - #31899 - #20311 - #28958 - #30205 - #29045 - #21820 - #29413 - #32786 - #32721 - #30617 <details><summary><h2>Previous Plans</h2></summary> - #30261 - #27194 - #25123 - #23072 - #21598 - #20022 - #18345 - #16429 - #14477 </details> ## :warning: Important 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.

GiteaMirror added the type/docs label 2025-11-02 10:54:48 -06:00

GiteaMirror closed this issue

2025-11-02 10:54:48 -06:00

GiteaMirror commented

2025-11-02 10:54:49 -06:00

@delvh commented on GitHub (Dec 18, 2024):

I'll start with my plan:

Automating the release process as much as possible.
My goal is that periodically (most likely every 4 months so that we have three releases per year) on a certain date, a release job runs that uses the current state of main, and releases it as is as the next full version. Our only remaining job will then be preparing the blog post in advance.

@delvh commented on GitHub (Dec 18, 2024): I'll start with my plan: - [ ] Automating the release process as much as possible. My goal is that periodically (most likely every 4 months so that we have three releases per year) on a certain date, a `release` job runs that uses the current state of `main`, and releases it as is as the next full version. Our only remaining job will then be preparing the blog post in advance.

GiteaMirror commented

2025-11-02 10:54:49 -06:00

@marcellmars commented on GitHub (Jan 6, 2025):

I plan to follow up on Enhancing Gitea OAuth2 Provider with Granular Scopes for Resource Access and address the access to resources if the scope public is present in the OAuth2/OIDC grant application.

The steps are:

Open an issue to discuss how we want to process the public scope if the request targets "nested" resources, such as repositories under a user URL path. In cases where a list is returned, we will need to make decisions, such as whether to consolidate the process by always performing a database search query or traversing without it, etc. I will propose my preferred approach for implementing this.
Implement the agreed-upon solution.

@marcellmars commented on GitHub (Jan 6, 2025): I plan to follow up on [Enhancing Gitea OAuth2 Provider with Granular Scopes for Resource Access](https://github.com/go-gitea/gitea/pull/32573) and address the access to resources if the scope `public` is present in the OAuth2/OIDC grant application. The steps are: - Open an issue to discuss how we want to process the `public` scope if the request targets "nested" resources, such as repositories under a `user` URL path. In cases where a list is returned, we will need to make decisions, such as whether to consolidate the process by always performing a database search query or traversing without it, etc. I will propose my preferred approach for implementing this. - Implement the agreed-upon solution.

GiteaMirror commented

2025-11-02 10:54:49 -06:00

@RedCocoon commented on GitHub (Feb 16, 2025):

Hopefully I can get Separation of Conversations and Issues, and Adding Conversation to Commits implemented.

Right now I still need some suggestions on how to make it better, and later on make the documentation for its API endpoint and whatnot.

@RedCocoon commented on GitHub (Feb 16, 2025): Hopefully I can get [Separation of Conversations and Issues, and Adding Conversation to Commits](https://github.com/go-gitea/gitea/pull/32384) implemented. Right now I still need some suggestions on how to make it better, and later on make the documentation for its API endpoint and whatnot.

GiteaMirror commented

2025-11-02 10:54:49 -06:00

@wxiaoguang commented on GitHub (Apr 5, 2025):

Although some PRs here are not ready in 1.24, there are enough new enhancements and features: https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+milestone%3A1.24.0 , and now it reaches Gitea 1.24 is currently set to enter feature freeze on 2025-04-01 23:59 UTC, and released on 2025-04-25 23:59 UTC

@RedCocoon Thank you very much for the PR, but I can't help because https://github.com/go-gitea/gitea/pull/32384#issuecomment-2447857831 : I think it's better to get more familiar with the whole code base and use proper design to implement a new feature step by step, but not copy a lot of existing code into one large PR .....

@wxiaoguang commented on GitHub (Apr 5, 2025): Although some PRs here are not ready in 1.24, there are enough new enhancements and features: https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+milestone%3A1.24.0 , and now it reaches `Gitea 1.24 is currently set to enter feature freeze on 2025-04-01 23:59 UTC, and released on 2025-04-25 23:59 UTC` ---- @RedCocoon Thank you very much for the PR, but I can't help because https://github.com/go-gitea/gitea/pull/32384#issuecomment-2447857831 : I think it's better to get more familiar with the whole code base and use proper design to implement a new feature step by step, but not copy a lot of existing code into one large PR .....

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13840