v13 release & upgrade party - October 21, 16.00 UTC / 18.00 CEST #402

fnetX commented 2025年10月13日 21:01:23 +02:00

Hi everyone! Forgejo admins, contributors and users, I invite you to celebrate the release of Forgejo v13 (scheduled for October 16) together. Forgejo admins are invited to use the time to perform their upgrades.

The meeting is scheduled for October 21 at 16.00 UTC / 18.00 CEST (Berlin time), via BigBlueButton at https://lecture.senfcall.de/ott-zml-1vs-qcc.

The meeting is a place to

• Celebrate the release and what we have achieved recently.
• Perform Forgejo upgrades and assist admins in case there are questions or problems.
• Troubleshoot potential problems together, if any.
• Discuss and set a focus for the Forgejo v14 development cycle.
• Relax and get more familiar with other team members.

If Codeberg preparations (custom patches, migration tests etc) go well, the meeting could also be used to upgrade Codeberg.org together (usually later in the evening).

I'm looking forward to seeing you!

There was a similar event last year, see #198.

Hi everyone! Forgejo admins, contributors and users, I invite you to celebrate the release of Forgejo v13 (scheduled for October 16) together. Forgejo admins are invited to use the time to perform their upgrades. The meeting is scheduled for October 21 at 16.00 UTC / 18.00 CEST (Berlin time), via BigBlueButton at https://lecture.senfcall.de/ott-zml-1vs-qcc. The meeting is a place to * Celebrate the release and what we have achieved recently. * Perform Forgejo upgrades and assist admins in case there are questions or problems. * Troubleshoot potential problems together, if any. * Discuss and set a focus for the Forgejo v14 development cycle. * Relax and get more familiar with other team members. If Codeberg preparations (custom patches, migration tests etc) go well, the meeting could also be used to upgrade Codeberg.org together (usually later in the evening). I'm looking forward to seeing you! There was a similar event last year, see https://codeberg.org/forgejo/discussions/issues/198.

fnetX commented 2025年10月21日 12:25:37 +02:00

Since this was not yet announced anywhere (neither in the blog post nor via social media, I kinda forgot that this would be very useful), I assume we'll mostly be Forgejo contributors around.

Still, what about sending this in a few hours:

Dear Forgejo admins,
Planning to upgrade to Forgejo v13 soon? Join our upgrade party and upgrade together, get help from Forgejo developers and get to know the community.
Join us today, October 21 at 16.00 UTC / 18.00 CEST. See #402 for details.

Since this was not yet announced anywhere (neither in the blog post nor via social media, I kinda forgot that this would be very useful), I assume we'll mostly be Forgejo contributors around. Still, what about sending this in a few hours: > Dear Forgejo admins, > Planning to upgrade to Forgejo v13 soon? Join our upgrade party and upgrade together, get help from Forgejo developers and get to know the community. > Join us today, October 21 at 16.00 UTC / 18.00 CEST. See https://codeberg.org/forgejo/discussions/issues/402 for details.

mahlzahn commented 2025年10月21日 12:36:10 +02:00

Let’s not wait too long, I will send it on Mastodon with the Forgejo account at 15:00 CEST if there are no objections until then.

Edit: scheduled to be published at 15:00.

Edit: https://floss.social/@forgejo/115412277942587493

Let’s not wait too long, I will send it on Mastodon with the Forgejo account at 15:00 CEST if there are no objections until then. Edit: scheduled to be published at 15:00. Edit: https://floss.social/@forgejo/115412277942587493

fnetX commented 2025年10月21日 21:05:18 +02:00

We're closing the meeting now.

• some admins actually performed upgrades
• Codeberg.org was upgraded successfully
  • The migration was fast.
  • The behaviour change in the quota implementation bricked pushing for a moment. We disabled all quota rules.
  • No other problems apart from that.
• We have scrubbed some issues (as visible from the references above, and some more that didn't reference the issue).
• Talked about some designs and future plans.

We're closing the meeting now. * some admins actually performed upgrades * Codeberg.org was upgraded successfully * The migration was fast. * The behaviour change in the quota implementation bricked pushing for a moment. We disabled all quota rules. * No other problems apart from that. * We have scrubbed some issues (as visible from the references above, and some more that didn't reference the issue). * Talked about some designs and future plans.