Update Release Candidate
-
Owner
In this release KVM and gitlab are broken ( for what seems to be a buildout bug, because for gitlab a workaround like jerome/slapos@5806ed5c seems to fix ).
@rafael @tomo How should we do when we need to release but master is broken ?
PS: is anybody working on repairing the state on master ?
+=
andextends
have always been buggy in buildout, maybe we should apply this gitlab patch and do same in kvm ? -
Owner
How should we do when we need to release but master is broken ?
It is a bit complex but couldn't it get fixed by who broken it or make a workarround? KVM needs to be stable for a project so, in any case, it should be fixed somehow.
-
Owner
How should we do when we need to release but master is broken ?
It's OK to merge on 1.0 branch even if all software are not working. The purpose of merging in 1.0 is to be able to tag and generate a SR in slapos master. We won't generate a SR in slapos master for broken SR for sure.
And of course, master should be fixed in the meantime.
PS: is anybody working on repairing the state on master ?
+=
andextends
have always been buggy in buildout, maybe we should apply this gitlab patch and do same in kvm ?You can have a look at https://www.erp5.com/group_section/forum/buildout--extends-and---cheat-sheet-O0wP6uGjM1