June 2023 - Uyuni Announce - openSUSE Mailing Lists

Community Hours Friday, June 30th, at 16.00 CEST / 14.00 UTC
by Marina Latini 30 Jun '23

30 Jun '23

Hello folks! As every last Friday of each month, we'll be having today, Friday, June 30th a session of the Uyuni Community Hours. The agenda is: - Uyuni project: a status update - GSoC 2023: Accessibility improvements for Uyuni - New way of writing changelogs for developers - Uyuni containerization administration tool - Upgrading podman-containerized Uyuni Servers The link to join is: https://teams.microsoft.com/l/meetup-join/19%3Ameeting_ZjZlMWI0OTctNGMxZi00… Remember you can find all the information about the Community hours, included updated agenda and link for the meeting at https://github.com/uyuni-project/uyuni/wiki/Uyuni-Community-Hours See you there! -- Marina Latini (she/her/hers) Software Release Engineer SUSE Software Solutions Germany GmbH Frankenstraße 146 90461 Nürnberg, Germany Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg) #ThePowerOfMany #DareToBeDifferent #HaveALotOfFun

1 0

IMPORTANT: New changelog style in git starting 23th June
by Can Bulut Bayburt 23 Jun '23

23 Jun '23

Hello all, The previously announced changes in changelog tests are now in effect. Please refer to the "Contributing" wiki page [1] to find out how to write changelogs in the new style. I recommend using the newly added 'mkchlog' tool in 'rel-eng/bin' to create entries conveniently. Feel free to run 'mkchlog --help' to find out how to use this tool. You can also consider adding 'rel-eng/bin' into your $PATH so you can run the tool from any subdirectory. Cheers, Can [1] https://github.com/uyuni-project/uyuni/wiki/Contributing#changelog-rules-fo…

1 0

Running acceptance tests at Pull Request
by Jordi Massaguer Pla 13 Jun '23

13 Jun '23

Hello! This is for contributors to the uyuni project, mainly Software and Quality Engineers. This is Jordi, and I have been working, with the help of other members or our team, on being able to run the acceptance tests at the Pull Requests, using github actions and containers. With this, you can run a subset of the acceptance tests before merging, so you know your code won't create a regression. Acceptance tests are the tests our Quality Engineers rely on approving a release, so it is important that new code passes that. Running this before merging, helps the release. In short, in your new Pull Request you will see some new "checks" . They take one hour. If you think this is a lot, have in mind that this was initially taking 8 hours! The checks are not mandatory, but we ask you to look at it if you see them failing. There is a link to a cucumber report and you can view the screenshot of what went wrong. You will need to sign up at https://reports.cucumber.io , which is free. More at https://github.com/uyuni-project/uyuni/wiki/Running-Acceptance-Tests-at-PR Enjoy! jordi

1 0

IMPORTANT: New changelog style in git starting 23th June
by Can Bulut Bayburt 08 Jun '23

08 Jun '23

Hi all, We're updating the way we write the changelog entries in Uyuni and spacewalk repositories in git. TL;DR: Starting 23.06, you must write your changelog entries into a newly created file named as "<packagename>.changes.<author>.<featurename>". This file must reside in the same directory as the master changelog (.changes) file. Editing the master changelog file directly is not allowed anymore. GitHub "Changelogs" action will be updated to test against this new style. I introduced a new helper script `rel-eng/bin/mkchlog` to automatically create new changelog files with proper naming. You can add `rel-eng/bin` to your $PATH and use the script conveniently from any subdirectory of any package to create entries for that package. It can either be used as `mkchlog "My changelog entry text"` or without any argument. In the latter case, it opens a text editor for you to input your entries into the newly created file. It can be run multiple times to add multiple entries. You can run `mkchlog --help` for complete usage instructions. When does it start? To allow everyone to merge their PRs without having to change them, we are announcing a deadline of 2 weeks before we enforce this change. The tooling and the tests will be updated on 23 June 2023. If you have any open PRs then, you will have to update it to use the new changelog style. If you have any open PRs, please consider finalizing and merging them before the deadline. Why do we do this? The master changelog files (.changes) are the most frequently modified files in all our PRs. This causes us to constantly have merge conflicts in almost every PR. Using personal files this way will prevent this and allow for smoother merges and a better development experience. What is being changed? - GitHub "Changelogs" action * Master changelog files cannot be modified directly * Changelog entries must be added as dedicated changelog files named conveniently as <packagename>.changes.<author>.<feature>. Example: susemanager.changes.cbbayburt.my_new_feature At the moment, the suggested filename style is just by convention. The test does not strictly enforce the author and the feature parts. It will pass as long as the file has any suffix after ".changes" part. * Workflow only runs for the 'master' and the release branches, ignoring feature branches. The test will run when pulling the feature branch into 'master'. * Workflow only runs for directories that have a changelog file. * Workflow is simplified, and the output is made more user-friendly. - Release Engineering: tito [2] * tito is updated to compile every changelog file into the master changelog (.changes) file. - New devtool: "mkchlog" [1] Recommended way to create changelog entries. Just add `rel-eng/bin/` to your $PATH and run `mkchlog --help` for usage instructions. - Uyuni wiki page: Contributing [3] Page updated with new instructions All the listed changes will be rolled out on the 23th of June. I hope you'll find the new style convenient in your day-to-day experience. Please feel free to reach out to me for any feedback, questions, or issues. Cheers, Can [1] https://github.com/uyuni-project/uyuni/pull/7065 [2] https://github.com/cbbayburt/tito/pull/1 [3] https://github.com/uyuni-project/uyuni/wiki/Contributing#changelog-rules-fo…

1 0

Community Hours Friday 26th, at 16.00 CEST
by Marina Latini 02 Jun '23

02 Jun '23

Hello, As every last Friday of each month, we'll be having on Friday 26th a session of the Uyuni Community Hours. The agenda for May is: - Uyuni 2023.06: What will be new? - Recurrent states - Uyuni at openSUSE Conference and SUSECON The link to join is: https://teams.microsoft.com/l/meetup-join/19%3Ameeting_ZjZlMWI0OTctNGMxZi00… Remember, you can find all the information about the Community hours, included updated agenda and link for the meeting at https://github.com/uyuni-project/uyuni/wiki/Uyuni-Community-Hours See you there! -- Marina Latini Software Release Engineer SUSE Software Solutions Germany GmbH Frankenstraße 146 90461 Nürnberg, Germany Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg) #ThePowerOfMany #DareToBeDifferent #HaveALotOfFun

1 1