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.

Sign up for GitHub

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

Jump to bottom

Plans for Gitea v1.18 #20022

Closed
delvh opened this issue Jun 18, 2022 · 14 comments
Closed

Plans for Gitea v1.18 #20022

delvh opened this issue Jun 18, 2022 · 14 comments
Labels
type/summary This issue aggregates a bunch of other issues
Milestone
1.18.0

Comments

@delvh
Copy link
Member

delvh commented Jun 18, 2022 •
edited
Loading

Hi all,

Gitea v1.17.0-rc1 will be released in the next few hours.
We have created the release/v1.17 branch accompanied by the v1.18.0-dev tag and are now using main for 1.18 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.18-rc1 is currently set to be released on 2022-09-15, so in the middle of september.
All new features for 1.18 should be merged until 2022-08-21 to be included in the next release.

Previous Plans
@delvh delvh added type/proposal The new feature has not been accepted yet but needs to be discussed first. type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/summary This issue aggregates a bunch of other issues labels Jun 18, 2022
@delvh delvh added this to the 1.18.0 milestone Jun 18, 2022
@delvh delvh removed type/proposal The new feature has not been accepted yet but needs to be discussed first. type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Jun 18, 2022
@6543 6543 pinned this issue Jun 18, 2022
@delvh
Copy link
Member Author

delvh commented Jun 18, 2022 •
edited
Loading

My plans are

  • Reviewing a lot of PRs (as always 😃 )
  • 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 scarce until the next release)

@Gusted
Copy link
Contributor

Gusted commented Jun 19, 2022

To keep this thread going, my optimistic plans for this release:

  • Continue improving mobile experience for Gitea.
  • Continue with QoL improvements.
  • Fix-up my open private issues PR to be more secure-by-design and hopefully get it merged this release or early next one.
  • Help moving forward with federation.

@silentcodeg
Copy link
Contributor

silentcodeg commented Jun 24, 2022 •
edited
Loading

@6543
Copy link
Member

6543 commented Jun 24, 2022 •
edited
Loading

@harryzcy
Copy link
Contributor

harryzcy commented Jun 29, 2022 •
edited
Loading

@dineshsalunke
Copy link

dineshsalunke commented Jul 3, 2022 •
edited
Loading

@ghost
Copy link

ghost commented Jul 13, 2022 •
edited by ghost
Loading

Various federation features:

  • Implement ForgeFed vocabulary
  • Federated following
  • Federated starring
  • Federated issues
  • Federated comments
  • Federated forking
  • Federated pull requests
  • Cross-instance user migrations
  • UI for federated features (Remote interactions pop-up and authorize_interaction?uri= page, similar to Mastodon)
  • Blocking users and instances

@pat-s
Copy link
Member

pat-s commented Aug 19, 2022

Enhanced 2FA support and disabling simple user/pass login in favor of SSO are two long standing feature wishes which would be great to have :)

@CodeDoctorDE
Copy link
Contributor

I'm currently not an expert but I want to add the move issue functionality to gitea: #20788

@6543
Copy link
Member

6543 commented Aug 24, 2022

@CodeDoctorDE #453 (comment) would be the original ;)

@earl-warren
Copy link
Contributor

earl-warren commented Sep 6, 2022 •
edited
Loading

@Rainson12

This comment was marked as off-topic.

Sign in to view
@f403

This comment was marked as off-topic.

Sign in to view
@delvh
Copy link
Member Author

delvh commented Oct 17, 2022 •
edited
Loading

Yes, we are now officially in feature freeze.
We discussed the release cycle internally and came to the conclusion that it would make sense to release rc0 once we enter feature freeze.
This means that 1.18.0-rc0 can be expected in the next few days.

@lunny lunny closed this as completed Oct 26, 2022
@lunny lunny mentioned this issue Oct 26, 2022
Closed
@lunny lunny unpinned this issue Oct 26, 2022
@delvh delvh mentioned this issue Feb 22, 2023
Closed
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/summary This issue aggregates a bunch of other issues
Projects
None yet
Milestone
1.18.0
Development

No branches or pull requests