[RELEASE] Forgejo 1.18.1-0 #231

New Issue

Closed

opened 2023-01-10 21:46:36 +00:00 by dachary · 14 comments

dachary commented

2023-01-10 21:46:36 +00:00

Owner

Following the instructions

publish for testing at https://codeberg.org/forgejo-experimental/ under 1.18.1-0
publish release notes using https://github.com/go-gitea/gitea/pull/22471 and https://gitea.com/gitea/blog/pulls/227/files
~~publish blog post~~
release 1.18.1-0

Following [the instructions](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING/RELEASE.md) - [x] publish for testing at https://codeberg.org/forgejo-experimental/ under 1.18.1-0 - [x] [publish release notes](https://codeberg.org/forgejo/forgejo/pulls/232) using https://github.com/go-gitea/gitea/pull/22471 and https://gitea.com/gitea/blog/pulls/227/files - [x] ~~publish blog post~~ - [x] release 1.18.1-0

dachary added the

enhancement/feature

forgejo/release

labels 2023-01-10 21:46:36 +00:00

dachary self-assigned this 2023-01-10 21:46:36 +00:00

dachary referenced this issue

2023-01-10 22:17:08 +00:00

WIP: [DOCS] RELEASE-NOTES: 1.18.1-0 release notes #232

dachary added a new dependency 2023-01-10 22:19:07 +00:00

#232 WIP: [DOCS] RELEASE-NOTES: 1.18.1-0 release notes

dachary commented

2023-01-10 22:20:40 +00:00

Poster

Owner

@caesar I included the blog post in the above task list, in case someone feels like writing one. As a Gitea admin I'd be happy just with the release notes considering it is a point release.

dachary added the due date 2023-01-11

2023-01-10 22:20:58 +00:00

dachary commented

2023-01-10 22:22:30 +00:00

Poster

Owner

Setting the due date to 11 January 2023 because Gitea 1.18.1 is imminent.

Setting the due date to 11 January 2023 because [Gitea 1.18.1](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/$qkrGA6-w9l5hnK9nHArU8JHncTKzIJfnI2X-Nq7EKAY?via=matrix.org&via=envs.net&via=tchncs.de) is imminent.

caesar commented

2023-01-10 23:34:36 +00:00

Owner

@caesar I included the blog post in the above task list, in case someone feels like writing one. As a Gitea admin I'd be happy just with the release notes considering it is a point release.

Agreed, I don't think a blog post is necessary for a point release. That's what the releases page and feed are for.

> @caesar I included the blog post in the above task list, in case someone feels like writing one. As a Gitea admin I'd be happy just with the release notes considering it is a point release. Agreed, I don't think a blog post is necessary for a point release. That's what the releases page and feed are for.

👍 1

caesar commented

2023-01-11 07:00:02 +00:00

Owner

Why is the testing build 1.18.0-2 when the release is 1.18.1-0?
Why is the patch version different?

Why is the testing build `1.18.0-2` when the release is `1.18.1-0`? Why is the patch version different?

dachary commented

2023-01-11 07:39:55 +00:00

Poster

Owner

Because, by chance, the 1.18.0-2 was created as a byproduct of yesterday's rebasing of Forgejo on the latest Gitea. There is only one commit difference with what 1.18.1-0 will be. I think there is a good chance that an additional commit is added to the 1.18.1 Gitea release, related to a security fix. But it's a wild guess on my part.

Because, by chance, the 1.18.0-2 was created as a byproduct of [yesterday's rebasing of Forgejo on the latest Gitea](https://codeberg.org/forgejo/forgejo/issues/51#issuecomment-764490). There is only one commit difference with what 1.18.1-0 will be. I think there is a good chance that an additional commit is added to the 1.18.1 Gitea release, related to a security fix. But it's a wild guess on my part.

👍 1

dachary commented

2023-01-11 08:13:10 +00:00

Poster

Owner

From the activity I see in Gitea, the release is unlikely to happen today. I asked @6543 for clarity on the matter as it would help me plan for this week workload. This is not a problem but I like to have some idea of when and how things happen.

From the activity I see in Gitea, the release is unlikely to happen today. I asked @6543 [for clarity on the matter](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/$VxA5V9-Z94wb4u6j1TZ0Zid_XxkYFEZtcMay8RaBXwM?via=matrix.org&via=envs.net&via=tchncs.de) as it would help me plan for this week workload. This is not a problem but I like to have some idea of when and how things happen.

dachary modified the due date from 2023-01-11 to 2023-01-12

2023-01-12 08:19:24 +00:00

dachary commented

2023-01-12 08:20:17 +00:00

Poster

Owner

One more commit in v1.18

https://github.com/go-gitea/gitea/pull/22409

I'm a little confused by the fact that nothing seems to be happening in terms of release. @6543 how is this supposed to go down?

One more commit in v1.18 https://github.com/go-gitea/gitea/pull/22409 I'm a little confused by the fact that nothing seems to be happening in terms of release. @6543 how is this supposed to go down?

Gusted commented

2023-01-12 10:18:14 +00:00

Owner

I'm a little confused by the fact that nothing seems to be happening in terms of release.

It usually goes like this:

"Hey guys, seems like a good time to release a new version?"
Few days/weeks later
Someone opens a PR for release notes
Few days/weeks later
"Alright, does anyone still want a PR in or not? Otherwise I'm going to tag and release"

Sometimes it is within a few days and other times it is silent for a week before actually tagging + release notes.

> I'm a little confused by the fact that nothing seems to be happening in terms of release. It usually goes like this: 1. "Hey guys, seems like a good time to release a new version?" *Few days/weeks later* 2. *Someone opens a PR for release notes* *Few days/weeks later* 3. "Alright, does anyone still want a PR in or not? Otherwise I'm going to tag and release" Sometimes it is within a few days and other times it is silent for a week before actually tagging + release notes.

👍 1

dachary removed the due date 2023-01-12

2023-01-13 08:51:24 +00:00

dachary commented

2023-01-13 08:52:18 +00:00

Poster

Owner

There has been a few backports in the past 24h from lunny & zeripath. https://github.com/go-gitea/gitea/milestone/129 1.18.1 is moving forward.

I removed the due date since there really is no way to figure out when this is due.

There has been a few backports in the past 24h from lunny & zeripath. https://github.com/go-gitea/gitea/milestone/129 1.18.1 is moving forward. I removed the due date since there really is no way to figure out when this is due.

👍 2

dachary added the due date 2023-01-17

2023-01-16 23:25:20 +00:00

dachary commented

2023-01-17 01:23:29 +00:00

Poster

Owner

Release notes are being prepared. It will happen soon.

Release notes are [being prepared](https://github.com/go-gitea/gitea/pull/22471). It will happen soon.

dachary modified the due date from 2023-01-17 to 2023-01-18

2023-01-17 13:39:58 +00:00

dachary commented

2023-01-17 17:38:11 +00:00

Poster

Owner

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

dachary commented

2023-01-18 00:19:34 +00:00

Poster

Owner

The the release is delayed until the Codeberg performance problems are resolved.

viceice commented

2023-01-20 07:29:23 +00:00

v1.18.1-0 is already released, so this can be closed.

v1.18.2 of gitea was also released with some important bug fixes.

v1.18.1-0 is already released, so this can be closed. [v1.18.2](https://togithub.com/go-gitea/gitea) of gitea was also released with some important bug fixes.

dachary commented

2023-01-20 08:10:06 +00:00

Poster

Owner

Right! Forgejo v1.18.2-0 is going to be published momentarily.

❤️ 1

dachary closed this issue

2023-01-20 08:10:08 +00:00

No Label