Skip to content
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.19 #21598

Closed
lunny opened this issue Oct 26, 2022 · 17 comments
Closed

Plans for Gitea 1.19 #21598

lunny opened this issue Oct 26, 2022 · 17 comments
Labels
type/summary This issue aggregates a bunch of other issues
Milestone

Comments

@lunny
Copy link
Member

lunny commented 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

@lunny lunny added the type/summary This issue aggregates a bunch of other issues label Oct 26, 2022
@lunny lunny added this to the 1.19.0 milestone Oct 26, 2022
@lunny lunny pinned this issue Oct 26, 2022
@lunny
Copy link
Member Author

lunny commented Oct 26, 2022

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

@delvh
Copy link
Member

delvh commented 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 Plugin Mechanism #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)

@6543
Copy link
Member

6543 commented Oct 26, 2022


#20022 (comment)

@ivancxj
Copy link

ivancxj commented Oct 28, 2022

@richmahn
Copy link
Contributor

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

Plan to get a conflict resolver done. #9014

@harryzcy
Copy link
Contributor

@ghost
Copy link

ghost commented Oct 31, 2022

@ghost

This comment was marked as off-topic.

@techknowlogick

This comment was marked as off-topic.

@helibin

This comment was marked as off-topic.

@massimiliano-dalcero
Copy link

massimiliano-dalcero commented Dec 1, 2022

@JakobDev
Copy link
Contributor

JakobDev commented 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.

@AkarinLiu

This comment was marked as off-topic.

@CodeDoctorDE
Copy link
Contributor

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

@gnat
Copy link
Contributor

gnat commented Feb 8, 2023

@go-gitea go-gitea locked and limited conversation to collaborators Feb 22, 2023
@techknowlogick techknowlogick unpinned this issue Feb 22, 2023
@techknowlogick
Copy link
Member

closing and locking now that rc0 is out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/summary This issue aggregates a bunch of other issues
Projects
None yet
Development

No branches or pull requests