Dear Hackers, On Mon, 2025-05-19 at 17:01 +0200, Marcus Hähnel wrote: > On Wed, 2025-05-14 at 22:01 +0200, Paul Boddie wrote: > > On Wednesday, 14 May 2025 16:52:48 CEST Marcus Hähnel wrote: > > > > > Some of the convenience features — like release tagging — do exist in our > > > customer repositories, but it’s more of a workflow habit than a conscious > > > decision to exclude them from GitHub. No one had brought up the need for > > > that kind of reproducibility in the open repo so far — and now that you > > > have, let’s fix it. > > > > I can understand that it can be easy to overlook. How many times has one > > seen > > missing tags in public repositories because Git makes it easy to forget to > > push them? I also understand that publicly tagging releases can make > > mistakes > > difficult to rectify, but I suppose this is just another hazard of release > > management, and eventually we all get used to making "patch" releases. > > I talked to our release engineers and we'll try to integrate this into our > release process in the future, such that > specific source states that ran through our QA will be tagged accordingly, > also on GitHub. Indeed internally we already > have them tagged, but these tags aren't transferred over to GitHub.
We have started to integrate a process into our release pipeline to tag the releases. This hopefully helps your use-cases to better get back to a known-good state for the specific setups you have. See an example here: https://github.com/kernkonzept/mk/tree/r-2025-W24 The release tag schema for now is r-yyyy-Www (with y = Year, w = week, W/r = literal W/r). We might re-evaluate that schema if we see that it is not perfect, but for now it should be OK. Right now the latest release has been tagged as r-2025-W24 (see above) and we will make sure future releases will be tagged as well. You can check out this state, for example when using ham, through: `ham checkout r-2025-W24` (and to optionally create a local branch named my-project as well and avoid the detached head messages) `ham checkout -b my-project r-2025-W24` Thanks a lot to Matthias Lange who implements this into our release pipeline. Best regards, - Marcus -- +++ Register now for our workshop “Get to know L4Re in 3 days” on October 28–30. Learn to design and deploy secure system architectures for your product with L4Re: https://www.kernkonzept.com/workshop-getting-started-with-l4re/ +++ --- Kernkonzept GmbH Sitz: Dresden HRB 31129 Geschäftsführer: Dr.-Ing. Michael Hohmuth _______________________________________________ l4-hackers mailing list -- [email protected] To unsubscribe send an email to [email protected]
