github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Plans for Gitea v1.18 #9085

New Issue
Closed
opened 2025-11-02 08:28:49 -06:00 by GiteaMirror · 14 comments
GiteaMirror commented 2025-11-02 08:28:49 -06:00
Owner
Copy Link

Originally created by @delvh on GitHub (Jun 18, 2022).

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

Originally created by @delvh on GitHub (Jun 18, 2022). 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 - #18345 - #16429 - #14477
GiteaMirror added the type/summary label 2025-11-02 08:28:50 -06:00
GiteaMirror commented 2025-11-02 08:28:51 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jun 18, 2022):

My plans are

  • Reviewing a lot of PRs (as always 😃 )
  • 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 scarce until the next release)
@delvh commented on GitHub (Jun 18, 2022): My plans are - [x] Reviewing **a lot** of PRs (as always :smiley: ) - [ ] 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 scarce until the next release)
GiteaMirror commented 2025-11-02 08:28:51 -06:00
Author
Owner
Copy Link

@Gusted commented on GitHub (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.
@Gusted commented on GitHub (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](https://github.com/go-gitea/gitea/pull/17711) PR to be more secure-by-design and hopefully get it merged this release or early next one. - Help moving forward with [federation](https://github.com/go-gitea/gitea/issues/18240).
GiteaMirror commented 2025-11-02 08:28:51 -06:00
Author
Owner
Copy Link

@silentcodeg commented on GitHub (Jun 24, 2022):

@silentcodeg commented on GitHub (Jun 24, 2022): * Help moving forward with [federation](https://github.com/go-gitea/gitea/issues/18240)
GiteaMirror commented 2025-11-02 08:28:52 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Jun 24, 2022):

  • help @Gusted 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)
@6543 commented on GitHub (Jun 24, 2022): * help @Gusted 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)
GiteaMirror commented 2025-11-02 08:28:52 -06:00
Author
Owner
Copy Link

@harryzcy commented on GitHub (Jun 29, 2022):

@harryzcy commented on GitHub (Jun 29, 2022): - [x] help to finish off #19411
GiteaMirror commented 2025-11-02 08:28:52 -06:00
Author
Owner
Copy Link

@dineshsalunke commented on GitHub (Jul 3, 2022):

@dineshsalunke commented on GitHub (Jul 3, 2022): - Try to see if I can finish off [API for projects](https://github.com/go-gitea/gitea/issues/14299)
GiteaMirror commented 2025-11-02 08:28:53 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 13, 2022):

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
@ghost commented on GitHub (Jul 13, 2022): Various federation features: - Implement [ForgeFed](https://forgefed.org/) 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
GiteaMirror commented 2025-11-02 08:28:53 -06:00
Author
Owner
Copy Link

@pat-s commented on GitHub (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 :)

@pat-s commented on GitHub (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 :) - https://github.com/go-gitea/gitea/issues/880 - https://github.com/go-gitea/gitea/issues/13606
GiteaMirror commented 2025-11-02 08:28:53 -06:00
Author
Owner
Copy Link

@CodeDoctorDE commented on GitHub (Aug 19, 2022):

I'm currently not an expert but I want to add the move issue functionality to gitea: https://github.com/go-gitea/gitea/issues/20788

@CodeDoctorDE commented on GitHub (Aug 19, 2022): I'm currently not an expert but I want to add the move issue functionality to gitea: https://github.com/go-gitea/gitea/issues/20788
GiteaMirror commented 2025-11-02 08:28:53 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Aug 24, 2022):

@CodeDoctorDE https://github.com/go-gitea/gitea/issues/453#issuecomment-861599858 would be the original ;)

@6543 commented on GitHub (Aug 24, 2022): @CodeDoctorDE https://github.com/go-gitea/gitea/issues/453#issuecomment-861599858 would be the original ;)
GiteaMirror commented 2025-11-02 08:28:54 -06:00
Author
Owner
Copy Link

@earl-warren commented on GitHub (Sep 6, 2022):

@earl-warren commented on GitHub (Sep 6, 2022): * Help move forward with https://github.com/go-gitea/gitea/issues/18240 * https://gitea.com/earl-warren/gitea/pulls/2: Add support for the [Friendly Forge Format (F3)](https://forum.forgefriends.org/t/about-the-friendly-forge-format-f3/681) (continuation of https://github.com/go-gitea/gitea/pull/20122)
GiteaMirror commented 2025-11-02 08:28:54 -06:00
Author
Owner
Copy Link

@Rainson12 commented on GitHub (Oct 17, 2022):

is there any plan on the release date? Im following the features included in this release and would really love to use them but i can see the milestone is again past due.

@Rainson12 commented on GitHub (Oct 17, 2022): is there any plan on the release date? Im following the features included in this release and would really love to use them but i can see the milestone is again past due.
GiteaMirror commented 2025-11-02 08:28:54 -06:00
Author
Owner
Copy Link

@f403 commented on GitHub (Oct 17, 2022):

I would also like to have already merged functions sooner.
Maybe moving work-in-progress to the next release, and releasing 1.18 with current features?

@f403 commented on GitHub (Oct 17, 2022): I would also like to have already merged functions sooner. Maybe moving work-in-progress to the next release, and releasing 1.18 with current features?
GiteaMirror commented 2025-11-02 08:28:55 -06:00
Author
Owner
Copy Link

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

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.

@delvh commented on GitHub (Oct 17, 2022): 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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/summary
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9085
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?