I'd like to support opening this discussion. In fact I have been asking here and there for about a week or more already.
As already reported in slack I prepared the infrastructure according to the conclusion / suggestion here https://confluence.suse.com/pages/viewpage.action?pageId=1894285383&spaceKey=YAST&title=Products%2Band%2BGit%2Bbranches to polish things mainly in relation to SLE-16. However, what I really would like to see the most currently is updating Devel:YaST:Agama:Release resp its OBS counter part. This project (in OBS) is intended to contain most current (kind of) stable version for TW, but currently it contains a few months old version which was released for SLE-16. So it is quite obsolete. And if we update it it will unblock one of my PBIs ;-) Regards Michal On Wed, Oct 22, 2025 at 6:05 PM Ancor Gonzalez Sosa <[email protected]> wrote: > With release of Leap 16.0 and the preparation of the to-be-released QU0 > for SLE-16, I feel we need to have a conversation about versions and > branches for Agama. > > Right now we have an SLE-16 branch that contains the version that will > be submitted to SLE-16.QU0 and likely to future quarterly updates. I > don't think we want to have a branch per QU. > > Just looking at the package agama, the IBS project that is in sync with > that branch produces something like agama-17+387.e512aa16d > > Then we have the master branch in which development should continue. As > I understand it, that means: > a) We should be submitting regularly from that branch to TW > b) We should be generating SLE-16-based images for that branch, so > internal SUSE QA can start testing new/future stuff like the changes of > the storage UI. > c) That will be the branch submitted to 16.1 (not to be confused with > 16.QU1). > At this point in time and according to the versioning we followed in the > past, I would have expected to see something like version > 18.pre+something in the IBS project synced with that branch. But we > actually have agama-17+512.b408500e7 > > In addition to all that, we also have a project at IBS called > Devel:YaST:Agama:Release that I assume (just speculating) contains > exactly what was submitted to SLE-16.0 (without any update). The agama > package there is agama-17+359.34bc8cc0b. > > I find that to be a bit confusing. I personally expect master and SLE-16 > to have different major version numbers. So does internal QA. Do we need > to reconsider versioning and branches a bit? > > Cheers. > -- > Ancor González Sosa > YaST Team at SUSE Software Solutions >
