From jhunsake at redhat.com Tue Jun 1 15:02:47 2021 From: jhunsake at redhat.com (Jake Hunsaker) Date: Tue, 1 Jun 2021 11:02:47 -0400 Subject: [sos-devel] sos 4.2 checkpoint/update Message-ID: Hello all, Couple updates for the sos project recently that I wanted to reach out to the wider audience about. Nothing all that major, but just as a heads up: 1. You may have noticed this already, but the maintainers are switching up the merge process a little bit. We will now be trying to default to using the GH interface for merges so that PRs properly get the 'merged' tag. Hopefully this means no more confusion around seeing a 'Closed' tag on your contributions after getting the thumbs up from the maintainers! Props to Bryan Quigley on pursuing this despite my own misunderstanding of what the end result would be if we stopped doing the manual rebase and merge. Note that if we're doing batch merges and there arises a conflict that the GH interface can't automatically solve, we may still on occasion fall back to the former method, in which case your PR would still be marked as 'closed'. As always though, as long as it gets into master then that's the important bit. What does this mean for you, the contributor? Not much really, aside from getting the 'merged' tag like you probably were expecting all along. There may be some spot requests for rebases on your end before merge if a situation like the above arises, but those should be few and far between. 2. Speaking of master - following the neutral language initiative that many projects/companies have adopted, we'll be renaming the "master" branch to "main" along with the 4.2 release. I'm not immediately sure if we'll make this change *after* the 4.2 tag is made (meaning the 4.2 tag will still reference 'master') or *before* (meaning the 'main' branch will effectively start with the tagging/release of 4.2). Suggestions welcome on that front. 3. In line with this, `sos collect` is deprecating the `--master` option. See #2555 for more details, but the plan at the moment is to deprecate `--master` in 4.2 and remove it wholly with the 4.3 release. As an aside, if there are other areas that contain language you'd like to see improved, please feel free to open an issue for it. 4. The new avocado framework based test suite has been getting built up rather well, so we should have more confidence in our releases for downstreams. That being said, I'd like to make a call for suggestions on other projects/products to add specific tests for - much like we recently did with the Foreman project. While I can't guarantee every suggestion will get its own addition, we can at least discuss any projects out there that rely on sos for troubleshooting. 5. Finally, there's the recent Freenode kerfuffle. Many organizations and projects have already moved to libera.chat and removed their presence from Freenode entirely. I've created #sos on libera.chat, however this is probably a good point to discuss other alternatives. The most popular one would be Matrix. We've also opened the #sosreport:matrix.org room. If there are preferences on what becomes the "official" chat, please let us know. We have also been discussing using Matrix as the "primary" and maintaining bridges/sync with libera.chat which seems like a good move. In either event, I am personally of the opinion that once we've established which one to go to, we should move off Freenode. Please let us know if there are any questions or concerns, Thanks! - jake / turboturtle -- Jake Hunsaker RHCA Cloud Specialist Senior Software Engineer, CEE Engineering Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: