Clarification on packaging latest versions of software
Yeh, I think the expectation/wording comes from the old times where people would manually publicly release via. a tarball somewhere ... now we live in a world where every git commit can be a release.
Bundling docs: explain/note why bundling should be avoided
Bundling docs: explain/note why bundling should be avoided
If you want to open a PR that might be useful, but in general it's difficult to explain the why of everything.
Package Review Exception - mysql9.7
Exception was granted, and we are changing the wording so it should be automatic next time.
Package Review Exception - mysql9.7
Update to ELNBuildSync 1.2.0 and add database connectivity and OpenID Connect
I don't think you can have blah.stg as a key ... all the ones I see are either: blah/blah_staging, blah/blah_stg or blah_prod/blah_stg ... Eg. using {{env}} or {{env_short}}
Bodhi: only the rawhide package is visible in updates
EBS: bump to 1.1.2 in staging
ELNBuildSync: use the correct principal name
ELNBuildSync: Pass krb5 principal name
ELNBuildSync: deploy 1.1.1 in staging