github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitea v1.2 on dl.gitea.io #1009

New Issue
Closed
opened 2025-11-02 03:45:07 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-02 03:45:07 -06:00
Owner
Copy Link

Originally created by @sentabi on GitHub (Aug 28, 2017).

I saw Gitea 1.2 already on https://dl.gitea.io/gitea/ but on release page https://github.com/go-gitea/gitea/releases there's only 1.2-rc1

It's a bug on build system ?

Originally created by @sentabi on GitHub (Aug 28, 2017). I saw Gitea 1.2 already on https://dl.gitea.io/gitea/ but on release page https://github.com/go-gitea/gitea/releases there's only 1.2-rc1 It's a bug on build system ?
GiteaMirror added the topic/build label 2025-11-02 03:45:07 -06:00
GiteaMirror commented 2025-11-02 03:45:08 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 28, 2017):

folder x.y is for version of that release not counting minor version number. so in folder 1.1 will be same as 1.1.3 currently etc. It could probably be improved not to include rc versions there

@lafriks commented on GitHub (Aug 28, 2017): folder `x.y` is for version of that release not counting minor version number. so in folder 1.1 will be same as 1.1.3 currently etc. It could probably be improved not to include rc versions there
GiteaMirror commented 2025-11-02 03:45:08 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 28, 2017):

Maybe this should be a question label not kind/enhancement.

@lunny commented on GitHub (Aug 28, 2017): Maybe this should be a question label not kind/enhancement.
GiteaMirror commented 2025-11-02 03:45:08 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Aug 28, 2017):

This is definitively a build bug. Since we have both 1.2/gitea-1.2-linux-amd64 and 1.2.0-rc1/gitea-1.2.0-rc1-linux-amd64 🙄

@bkcsoft commented on GitHub (Aug 28, 2017): This is definitively a build bug. Since we have both `1.2/gitea-1.2-linux-amd64` and `1.2.0-rc1/gitea-1.2.0-rc1-linux-amd64` 🙄
GiteaMirror commented 2025-11-02 03:45:08 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 29, 2017):

@bkcsoft it's not really bug it is latest version from 1.2 branch

@lafriks commented on GitHub (Aug 29, 2017): @bkcsoft it's not really bug it is latest version from 1.2 branch
GiteaMirror commented 2025-11-02 03:45:09 -06:00
Author
Owner
Copy Link

@sentabi commented on GitHub (Aug 29, 2017):

@lafriks we have https://dl.gitea.io/gitea/1.2/gitea-1.2-linux-amd64.
It's the latest branch, but which one? The stable/RC or anything else, from the folder or file name itself it's not clear.

@sentabi commented on GitHub (Aug 29, 2017): @lafriks we have https://dl.gitea.io/gitea/1.2/gitea-1.2-linux-amd64. It's the latest branch, but which one? The stable/RC or anything else, from the folder or file name itself it's not clear.
GiteaMirror commented 2025-11-02 03:45:09 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 29, 2017):

It is the latest version of 1.2 branch and currently it is 1.2.0-rc1

@lafriks commented on GitHub (Aug 29, 2017): It is the latest version of 1.2 branch and currently it is 1.2.0-rc1
GiteaMirror commented 2025-11-02 03:45:09 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 29, 2017):

maybe we should rename 1.2 to release/v1.2 to match the branch name.

@lunny commented on GitHub (Aug 29, 2017): maybe we should rename `1.2` to `release/v1.2` to match the branch name.
GiteaMirror commented 2025-11-02 03:45:09 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 29, 2017):

I don't think it's needed

@lafriks commented on GitHub (Aug 29, 2017): I don't think it's needed
GiteaMirror commented 2025-11-02 03:45:09 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (May 10, 2018):

Can this ticket be closed?

@techknowlogick commented on GitHub (May 10, 2018): Can this ticket be closed?
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 topic/build
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#1009
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?