Codeberg/Community
54
325
Fork
You've already forked Community
12

Gitea v1.13.0 Is looking around the corner #310

Closed
opened 2020年10月14日 14:26:32 +02:00 by 6543 · 11 comments

I can access https://test.codeberg.org/ -> ssl error ...

There most likely won't be new db migrations. So It would be nice if Codeberg can test if migration to v1.13.0-rc works fine or not :)

https://github.com/go-gitea/gitea/milestone/67

close #330
close #335
close #344
close #79
close #207

I can access `https://test.codeberg.org/` -> ssl error ... There most likely won't be new db migrations. So It would be nice if Codeberg can test if migration to v1.13.0-rc works fine or not :) *https://github.com/go-gitea/gitea/milestone/67* close #330 close #335 close #344 close #79 close #207
Author
Copy link

ping @hw @ashimokawa

ping @hw @ashimokawa

@6543

You are looking for https://codeberg-test.org :)

And yes. I can deploy 1.13 there soon.

@6543 You are looking for https://codeberg-test.org :) And yes. I can deploy 1.13 there soon.

Deployed 1.13 on codeberg-test.org !

Deployed 1.13 on codeberg-test.org !
Member
Copy link

Do we have an eta for production?

Do we have an eta for production?

@hw

Don't ask for ETAs ;)

In the past we deployed around -rc2, but 1.12 only had one rc IIRC, and we had problems with migration that's why we tested everyting very carefully.

1.13 looks far less problematic, we do not have to wait till it is final, but maybe we should do a dry run like last time

@hw Don't ask for ETAs ;) In the past we deployed around -rc2, but 1.12 only had one rc IIRC, and we had problems with migration that's why we tested everyting very carefully. 1.13 looks far less problematic, we do not have to wait till it is final, but maybe we should do a dry run like last time
Author
Copy link

ETA missing rate = 100% ;)

And happy to hear it,s less problematic.

ETA missing rate = 100% ;) And happy to hear it,s less problematic.
Author
Copy link

@ashimokawa noticed bugs are fixed and gitea will release 1.13.0 soon - if everything is going well ;)

did you found any bugs we should be aware of?

@ashimokawa noticed bugs are fixed and gitea will release 1.13.0 soon - if everything is going well ;) did you found any bugs we should be aware of?
Member
Copy link

@6543 : nothing that is not tracked in gitea's issue tracker.

@6543 : nothing that is not tracked in gitea's issue tracker.
Author
Copy link

UPDATE: Add Allow-/Block-List for Migrate & Mirrors (13610) will be in v1.14.0 release but could be worth a cherry-pick for codeberg's v1.13 test branch ...

UPDATE: [Add Allow-/Block-List for Migrate & Mirrors (13610)](https://github.com/go-gitea/gitea/commit/b2435af9be75a0cdeea08881c162e65740225f56) will be in **v1.14.0** release but could be worth a **cherry-pick** for codeberg's v1.13 test branch ...
Author
Copy link

https://github.com/go-gitea/gitea/releases/tag/v1.13.0

released

https://github.com/go-gitea/gitea/releases/tag/v1.13.0 released
Member
Copy link

@6543 you are quick :)

@6543 you are quick :)
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#310
Reference in a new issue
Codeberg/Community
No description provided.
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?