Rename repo zeroconf-ioslave to kio-zeroconf
Closed, ResolvedPublic

Description

With the porting of the repo from using KIO::SlaveBase to KIO::WorkerBase and thus following the new nomenclatura, the name of the repo no longer matches. (see https://invent.kde.org/network/zeroconf-ioslave/-/merge_requests/2 for the related MR).

And it is also not following the pattern seen with other repos of that kind, like "kio-gopher", "kio-gdrive", "kio-fuse", "kio-stash".

Therefore I propose to rename the repo officially to kio-zeroconf in time for the upcoming KDE Gear 22.08 release.

Inside the repo the only thing that needs adaption is the appstream metainfo.xml file, no changes needed in catalog names, documentation or installed files, if I saw correctly.

Opinions?

kossebau created this task.Jul 6 2022, 2:52 PM
kossebau updated the task description. (Show Details)

When it comes to timing, guess such a rename is best done after July 7, 2022: 22.04.3 release and before July 14 2022: 22.08 Freeze and Beta (22.07.80) tag & release. So that the 22.08 tarballs are named folloiwing the new name right from the beta one.

I.e. in the next 7 days (after tomorrow). So please have your mind made up soonish? :)

Probably doesn't matter much, but if there is no respin (which seems like a reasonable bet) it could happen even now.

sitter added a comment.Jul 6 2022, 4:07 PM

+1 to the change

aacid added a comment.Jul 6 2022, 4:37 PM

There's some adaptation in the release scripts and translation structure needed, but nothing insurmountable.

I have no opinion on the change.

Sysadmin wise this should not be a problem, however it would probably be good that this change is widely advertised.

Okay, so seems at least on first thought that should be an okay move, and thus we can get rid of the misnomer now with the MR also merged.

With 22.04.3 now out and no respin to expect, could you please execute the rename on next occasion, @bcooksley ?

I would care for adapting the metainfo.xml file and the referenced screenshot afterwards.

it would probably be good that this change is widely advertised.

Of which target groups are you thinking here exactly?

bcooksley closed this task as Resolved.Jul 8 2022, 9:16 AM
bcooksley claimed this task.

I have now renamed the repository in the metadata and on Gitlab.

Thanks, Ben, and everyone for discussion.

@aacid @heikobecker Can you please add a note to the 22.08 tarball release announcements about the repo/tarball name change? Hm, actually I would have thought there might be some "new/removed" section for each KDE Gear main release, where this would be fitting, but could not find that, did I look at the wrong places? At least I saw such "Added/Removed" section in the KF announcements.

E.g. I would propose/ask to mention this in the "KDE Gear 22.08 Beta packages available for packagers" email, as I see at least distribution packagers as main target group to make aware here, so they do not have to find things out themselves.

And I just noticed there is also sdk/kdesdk-kioslaves which might need the same treatment, will see to prepare things code-side this late afternoon with a MR for WorkerBase.

@aacid @heikobecker Can you please add a note to the 22.08 tarball release announcements about the repo/tarball name change? Hm, actually I would have thought there might be some "new/removed" section for each KDE Gear main release, where this would be fitting, but could not find that, did I look at the wrong places? At least I saw such "Added/Removed" section in the KF announcements.

We mentioned it in the release notes, which are linked in the announcements and I just created a page for 22.08: https://community.kde.org/KDE_Gear/22.08_Release_notes

kossebau added a comment.EditedJul 8 2022, 1:37 PM

Ah, must have failed to click the very link to the very release notes then (and actually was sure I had seen such lists also for KDE Gear).
Good then, thanks (and just got one +1 on this being what packagers like to see, so all happy from my side here).

I've adapted scripty to handle this:

I'd like to point out that the metainfo file inside the repository still refers to the old name: it is safe to rename it, or would it break anything?

< I've adapted scripty to handle this:

Thanks.

I'd like to point out that the metainfo file inside the repository still refers to the old name: it is safe to rename it, or would it break anything?

Good to be reminded in any case, but can happily report that https://invent.kde.org/network/kio-zeroconf/-/merge_requests/3 is up to care for that :)