Cleanup the build process #357

Open
opened 2022-12-20 17:01:11 +00:00 by nico · 2 comments
Owner

I cannot release new versions of cdist at the moment, because I haven't done it in a long time. Last time I created docs/release-process.org, but it is somewhat incomplete and it seems 7.0.0 is not linked as the most current release.

Also it would be good if more people than just me could create new releases.

cc @steven @fnux @evilham

I cannot release new versions of cdist at the moment, because I haven't done it in a long time. Last time I created docs/release-process.org, but it is somewhat incomplete and it seems 7.0.0 is not linked as the most current release. Also it would be good if more people than just me could create new releases. cc @steven @fnux @evilham
Collaborator

Hey, sorry, it's been crazy days.

I also have some patches pending, so I'll try to take a look into this next week with an employee.

Hey, sorry, it's been crazy days. I also have some patches pending, so I'll try to take a look into this next week with an employee.
evilham self-assigned this 2023-01-26 14:33:36 +00:00
Collaborator

@nico Was taking a quick look at this and I notice following, most of it requires some sort of internal knowledge:

  • For pypi: It'd be necessary to add a user as maintainer to the cdist project (e.g. mine is evilham)
  • For source tarball: From what I gather, the GPG signature should match at least what is documented here: https://www.cdi.st/manual/latest/cdist-install.html#installing-from-source-with-signature-verification
    So it shouldn't radically change from one version to the next.
  • Signed git tag: similar to above, key shouldn't dramatically change between versions
  • The helper script heavily assumes master as branch and origin as the upstream (important to keep in mind)
  • ML announcement: just discovered there is one on googlegroups? I guess that one h as to be done manually
  • gitea release: the API might have changed since the GL migration, indeed there are no "releases" on gitea so far
  • website update: back on GitLab there was a worker of some sorts that did the building and uploading, I guess this doesn't exist anymore? What would be necessary to restore that?

Other than that, it seems like the release script should mostly work.

@nico Was taking a quick look at this and I notice following, most of it requires some sort of internal knowledge: - [ ] For pypi: It'd be necessary to add a user as maintainer to the cdist project (e.g. mine is evilham) - [ ] For source tarball: From what I gather, the GPG signature should match at least what is documented here: https://www.cdi.st/manual/latest/cdist-install.html#installing-from-source-with-signature-verification So it shouldn't radically change from one version to the next. - [ ] Signed git tag: similar to above, key shouldn't dramatically change between versions - [ ] The helper script heavily assumes master as branch and origin as the upstream (important to keep in mind) - [ ] ML announcement: just discovered there is one on googlegroups? I guess that one h as to be done manually - [ ] gitea release: the API might have changed since the GL migration, indeed there are no "releases" on gitea so far - [ ] website update: back on GitLab there was a worker of some sorts that did the building and uploading, I guess this doesn't exist anymore? What would be necessary to restore that? Other than that, it seems like the release script should mostly work.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ungleich-public/cdist#357
No description provided.