I like Forgejo and have it set up in a private server with several repositories. My questions about it are:
How does the Fedora project handle the version churn? Is the plan to just keep up with the frequent versions and switch to an LTS version (15?) once available?
It appears (as of today) that forge.fedoraproject.org is running version 14.0.1-4 (according to the footer) but this doesn’t match versions available in Fedora or EPEL repositories (13.0.4-2) available * here
I have a copr repository where I’ve built EPEL 9 versions, and want to provide newer 14.0.2 versions, but don’t want to duplicate efforts by anyone else (Nils Philippsen according to Fedora package sources).
I’m a Fedora packager for a few packages and wouldn’t mind helping with this package, but the bugzilla tickets (and there’s many…) appear to get assigned to “Fedora Infrastructure Sig” and I’m not sure how I would get involved in that…
I like Forgejo and have it set up in a private server with several repositories. My questions about it are:
How does the Fedora project handle the version churn? Is the plan to just keep up with the frequent versions and switch to an LTS version (15?) once available?
Handle where? The fedora rpm packages? The forge instance?
I think the rpm packages should just continue to update as releases come
out.
It appears (as of today) that forge.fedoraproject.org is running version 14.0.1-4 (according to the footer) but this doesn’t match versions available in Fedora or EPEL repositories (13.0.4-2) available * here
Right. forge.fedoraproject.org instance is not installed from the rpm.
It’s using a container built in the konflux build system and deployed
on our openshift cluster. So, the version may well not match up with the
rpm version all the time.
I have a copr repository where I’ve built EPEL 9 versions, and want to provide newer 14.0.2 versions, but don’t want to duplicate efforts by anyone else (Nils Philippsen according to Fedora package sources).
You might ask him if he would like to add a epel9 version to the
official packages and offer to help maintain the fedora/epel ones?
But of course you are welcome to do a copr if you prefer…
I’m a Fedora packager for a few packages and wouldn’t mind helping with this package, but the bugzilla tickets (and there’s many…) appear to get assigned to “Fedora Infrastructure Sig” and I’m not sure how I would get involved in that…
You don’t have to… thats basically a sig of people who work on
infrastructure and want to maintain packages used by infrastructure, but
particular packages could be maintained by other people too.
I think that group is added here because we were still deciding how we
wanted to deploy things for forge.fedoraproject.org and thought it might
be using the rpm.
Anyhow, I’d mail Nils and ask if he would like help…
