Plans for Gitea 1.19 #9738

Closed
opened 2025-11-02 08:48:01 -06:00 by GiteaMirror · 17 comments
Owner

Originally created by @lunny on GitHub (Oct 26, 2022).

Feature Description

Hi all,

Gitea v1.18.0-rc0 has been released.
We have created the release/v1.18 branch accompanied by the v1.19.0-dev tag and are now using main for 1.19 development.

Please comment here your own plans for the next release.

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.19-rc1 is currently set to be released on 2023-01-26, so in the early of January.
All new features for 1.19 should be merged until 2022-01-11 to be included in the next release.

Previous Plans

Screenshots

No response

Originally created by @lunny on GitHub (Oct 26, 2022). ### Feature Description Hi all, Gitea v1.18.0-rc0 has been released. We have created the release/v1.18 branch accompanied by the v1.19.0-dev tag and are now using main for 1.19 development. Please comment here your own plans for the next release. 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.19-rc1 is currently set to be released on 2023-01-26, so in the early of January. All new features for 1.19 should be merged until 2022-01-11 to be included in the next release. Previous Plans - #20022 - #18345 - #16429 - #14477 ### Screenshots _No response_
GiteaMirror added the type/summary label 2025-11-02 08:48:01 -06:00
Author
Owner

@lunny commented on GitHub (Oct 26, 2022):

I would like below issues/prs could be resolved in this release.

@lunny commented on GitHub (Oct 26, 2022): I would like below issues/prs could be resolved in this release. - #18165 - #13539
Author
Owner

@delvh commented on GitHub (Oct 26, 2022):

I can directly copy my plans from 1.18, since nothing has changed about them:


My plans are

  • Reviewing a lot of PRs (the never ending task)
  • a #20126 so that we can finally offload all the optional customizations there without bloating the main binary too much. (At least if I find the time for it, I know already that my free time will be rather scarce until the next release)
@delvh commented on GitHub (Oct 26, 2022): I can directly copy my plans from 1.18, since nothing has changed about them: --- My plans are - [x] Reviewing **a lot** of PRs (the never ending task) - [ ] a #20126 so that we can finally offload all the optional customizations there without bloating the main binary too much. (At least if I find the time for it, I know already that my free time will be rather scarce until the next release)
Author
Owner

@6543 commented on GitHub (Oct 26, 2022):

  • help with private issues ...
  • help with federation - mostly reviews I guess
  • refactoring stuff ...
  • help long open pulls
  • better integration of external CIs (define api etc ... cc @lunny )
  • Project boards for organizations (#13405)

https://github.com/go-gitea/gitea/issues/20022#issuecomment-1165517967

@6543 commented on GitHub (Oct 26, 2022): * help with private issues ... * help with federation - mostly reviews I guess * refactoring stuff ... * help long open pulls * better integration of external CIs (define api etc ... cc @lunny ) * Project boards for organizations (#13405) --- https://github.com/go-gitea/gitea/issues/20022#issuecomment-1165517967
Author
Owner

@ivancxj commented on GitHub (Oct 28, 2022):

@ivancxj commented on GitHub (Oct 28, 2022): - #2175
Author
Owner

@richmahn commented on GitHub (Oct 28, 2022):

Plan to get the Git Refs API CRUD endpoints done. #21328

Plan to get a conflict resolver done. #9014

@richmahn commented on GitHub (Oct 28, 2022): Plan to get the Git Refs API CRUD endpoints done. #21328 Plan to get a conflict resolver done. #9014
Author
Owner

@harryzcy commented on GitHub (Oct 30, 2022):

@harryzcy commented on GitHub (Oct 30, 2022): - #20908
Author
Owner

@ghost commented on GitHub (Oct 31, 2022):

@ghost commented on GitHub (Oct 31, 2022): - #21638 - #21622 - #21617 - #21562 - #21559 - #21522
Author
Owner

@ghost commented on GitHub (Nov 10, 2022):

feature: HTTPS based deploy keys A proposal from 2017. really hope this can be supported.

@ghost commented on GitHub (Nov 10, 2022): [feature: HTTPS based deploy keys](https://github.com/go-gitea/gitea/issues/2051) A proposal from 2017. really hope this can be supported.
Author
Owner

@techknowlogick commented on GitHub (Nov 10, 2022):

@nick008a this thread is for comment here your own plans for the next release. I hope that means you are planning on submitting a PR for this?

@techknowlogick commented on GitHub (Nov 10, 2022): @nick008a this thread is for comment here your own plans for the next release. I hope that means you are planning on submitting a PR for this?
Author
Owner

@wolfogre commented on GitHub (Nov 11, 2022):

@wolfogre commented on GitHub (Nov 11, 2022): - [x] Fix bugs of parsing YAML template: - <img width="692" alt="image" src="https://user-images.githubusercontent.com/9418365/201316955-94ba7c96-0ad5-4534-a8cd-8071a98a0b6a.png"> - #21831 - #21830 - [ ] ~Support `config.yml` in ISSUE_TEMPLATE~ - [ ] #13539 - #21937
Author
Owner

@helibin commented on GitHub (Nov 23, 2022):

sub org can be support

@helibin commented on GitHub (Nov 23, 2022): sub org can be support
Author
Owner

@massimiliano-dalcero commented on GitHub (Dec 1, 2022):

@massimiliano-dalcero commented on GitHub (Dec 1, 2022): * Add automated project board ( https://github.com/go-gitea/gitea/issues/14359 ) * Show in the issue list the board name * Automation based on action on the boards (when a issue is moved to bord "XYZ" do "this")
Author
Owner

@JakobDev commented on GitHub (Dec 1, 2022):

Support config.yml in ISSUE_TEMPLATE

I've started working on this. See #20956. The PR is just for disabling blank issue. Other things should be in a separated PR.

@JakobDev commented on GitHub (Dec 1, 2022): > Support config.yml in ISSUE_TEMPLATE I've started working on this. See #20956. The PR is just for disabling blank issue. Other things should be in a separated PR.
Author
Owner

@AkarinLiu commented on GitHub (Dec 20, 2022):

I hope Can be intergrade Gitea Pages & Gitea workflow

@AkarinLiu commented on GitHub (Dec 20, 2022): I hope Can be intergrade Gitea Pages & Gitea workflow
Author
Owner

@CodeDoctorDE commented on GitHub (Jan 4, 2023):

I want to start contributing again and I'm currently working on #22273. I will look if I can do more in the future

@CodeDoctorDE commented on GitHub (Jan 4, 2023): I want to start contributing again and I'm currently working on #22273. I will look if I can do more in the future
Author
Owner

@gnat commented on GitHub (Feb 8, 2023):

@gnat commented on GitHub (Feb 8, 2023): * https://github.com/go-gitea/gitea/pull/22112
Author
Owner

@techknowlogick commented on GitHub (Feb 22, 2023):

closing and locking now that rc0 is out.

@techknowlogick commented on GitHub (Feb 22, 2023): closing and locking now that rc0 is out.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9738