[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Re: KDE release 20.12.0 packages available for packagers
From: Ben Cooksley <bcooksley () kde ! org>
Date: 2020-12-24 18:41:19
Message-ID: CA+XidOFeYduWxcp1FcPAek8BfokM7D6k31JQiVqGL3=PYcE9EQ () mail ! gmail ! com
[Download RAW message or body]
On Fri, 25 Dec 2020, 4:18 am Christoph Feck, <cfeck@kde.org> wrote:
> On 12/10/20 16:30, Heiko Becker wrote:
> > On Donnerstag, 10. Dezember 2020 15:32:35 CET, Christoph Feck wrote:
> >> While the 20.12.0 releases are now published, the KDE release team
> >> is still looking for volunteers to package future releases.
> >
> > considering that I've enjoyed nice tarballs as a packager for quite a
> > few years, I'd be willing to step up and give something back. I know my
> > way around a command line and git and I think I roughly know how the
> > release service tarballs are made.
>
> Hello Heiko,
>
Hi all,
> sorry for getting back to you this late. Thank you for volunteering to
> help the release team with future KDE releases! To get you started, I
> plan to involve you in the release process for the 20.12.1 releases.
>
> The steps involved are documented at https://phabricator.kde.org/T12272
> (but may a bit outdated). The schedule[1] says we should prepare the
> repositories before Jan 4. In the meantime, you could start preparing
> your system. I currently do not have access to the machine from where I
> do the releases, so some details might be missing.
>
> * git checkout the following repositories:
> - sysadmin/release-tools (releases/20.12 branch)
> - Jonathan Riddel's repository for "add_appstream_versions.sh"
> (which needs some Python setup)
> - all repositories listed at release-tools/modules.git to a flat
> directory
> (there used to be a mapping file to find the invent location ...)
>
You can use the git-kclone script in repo-metadata to do this cloning - it
accepts both the repository identifiers (which are unique) or wildcard
rules to just clone larger numbers of repositories.
You will need a full clone of repo-metadata to use it though.
> * Locally adapt the config file in release-tools to point to the
> add_appstream_versions location.
>
> * svn checkout the i18n data using release-tools/update_l10n.sh
>
> * ask sysadmins to get ssh access to these accounts:
> - pkgapplications@capona.kde.org
> - ftpadmin@deino.kde.org
> Also you need commit access to some repositories for WWW, but since
> that recently changed, I am not sure about the repository names.
>
I believe the correct repository for this is websites/kde-org but Carl
should be able to confirm this.
> * make sure you have a GPG key setup. If you are not in our ring,
> Albert knows best how to do the key signing via Internet video
> conferencing (e.g. Jitsi).
> If possible, also investigate how to get your key setup forwarded
> to the capona account.
>
> (If anyone can correct me or add to this list, please do :)
>
> Merry Christmas and a Happy New Year to you and the whole KDE community!
>
> BG,
> Christoph
>
Many thanks,
Ben
> [1]
> https://community.kde.org/Schedules/release_service/20.12_Release_Schedule
>
> --
> Christoph Feck
> KDE Release Team
>
>
[Attachment #3 (text/html)]
<div dir="auto"><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On \
Fri, 25 Dec 2020, 4:18 am Christoph Feck, <<a \
href="mailto:cfeck@kde.org">cfeck@kde.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">On 12/10/20 16:30, Heiko Becker wrote:<br> > On \
Donnerstag, 10. Dezember 2020 15:32:35 CET, Christoph Feck wrote:<br> >> While \
the 20.12.0 releases are now published, the KDE release team<br> >> is still \
looking for volunteers to package future releases.<br> ><br>
> considering that I've enjoyed nice tarballs as a packager for quite a<br>
> few years, I'd be willing to step up and give something back. I know my<br>
> way around a command line and git and I think I roughly know how the<br>
> release service tarballs are made.<br>
<br>
Hello Heiko,<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Hi \
all, </div><div dir="auto"><br></div><div dir="auto"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
sorry for getting back to you this late. Thank you for volunteering to<br>
help the release team with future KDE releases! To get you started, I<br>
plan to involve you in the release process for the 20.12.1 releases.<br>
<br>
The steps involved are documented at <a href="https://phabricator.kde.org/T12272" \
rel="noreferrer noreferrer" \
target="_blank">https://phabricator.kde.org/T12272</a><br> (but may a bit outdated). \
The schedule[1] says we should prepare the<br> repositories before Jan 4. In the \
meantime, you could start preparing<br> your system. I currently do not have access \
to the machine from where I<br> do the releases, so some details might be \
missing.<br> <br>
* git checkout the following repositories:<br>
- sysadmin/release-tools (releases/20.12 branch)<br>
- Jonathan Riddel's repository for \
"add_appstream_versions.sh"<br> (which needs some Python setup)<br>
- all repositories listed at release-tools/modules.git to a flat<br>
directory<br>
(there used to be a mapping file to find the invent location \
...)<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">You can \
use the git-kclone script in repo-metadata to do this cloning - it accepts both the \
repository identifiers (which are unique) or wildcard rules to just clone larger \
numbers of repositories.</div><div dir="auto"><br></div><div dir="auto">You will need \
a full clone of repo-metadata to use it though. </div><div dir="auto"><br></div><div \
dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 \
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
* Locally adapt the config file in release-tools to point to the<br>
add_appstream_versions location.<br>
<br>
* svn checkout the i18n data using release-tools/update_l10n.sh<br>
<br>
* ask sysadmins to get ssh access to these accounts:<br>
- <a href="mailto:pkgapplications@capona.kde.org" target="_blank" \
rel="noreferrer">pkgapplications@capona.kde.org</a><br>
- <a href="mailto:ftpadmin@deino.kde.org" target="_blank" \
rel="noreferrer">ftpadmin@deino.kde.org</a><br>
Also you need commit access to some repositories for WWW, but since<br>
that recently changed, I am not sure about the repository \
names.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I \
believe the correct repository for this is websites/kde-org but Carl should be able \
to confirm this. </div><div dir="auto"><br></div><div dir="auto"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
* make sure you have a GPG key setup. If you are not in our ring,<br>
Albert knows best how to do the key signing via Internet video<br>
conferencing (e.g. Jitsi).<br>
If possible, also investigate how to get your key setup forwarded<br>
to the capona account.<br>
<br>
(If anyone can correct me or add to this list, please do :)<br>
<br>
Merry Christmas and a Happy New Year to you and the whole KDE community!<br>
<br>
BG,<br>
Christoph<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Many \
thanks, </div><div dir="auto">Ben</div><div dir="auto"><br></div><div \
dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 \
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
[1] <br>
<a href="https://community.kde.org/Schedules/release_service/20.12_Release_Schedule" \
rel="noreferrer noreferrer" \
target="_blank">https://community.kde.org/Schedules/release_service/20.12_Release_Schedule</a><br>
<br>
-- <br>
Christoph Feck<br>
KDE Release Team<br>
<br>
</blockquote></div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic