Re: [sage-release] Re: Release process

2018-05-12 Thread Volker Braun
Just to suggest something that is not burdened with combinatorial explosion, how about listing the conflicting tickets. Which is just O(N^2) On Saturday, May 12, 2018 at 5:10:52 PM UTC+2, Maarten Derickx wrote: > > > > On Saturday, 12 May 2018 14:10:27 UTC+2, Jeroen Demeyer wrote: >> >> On 2018-

Re: [sage-release] Re: Release process

2018-05-12 Thread Maarten Derickx
On Saturday, 12 May 2018 14:10:27 UTC+2, Jeroen Demeyer wrote: > > On 2018-05-12 10:31, Marc Mezzarobba wrote: > > it could perhaps > > be useful to have additional integration branches where the *reviewer* > > would be supposed to merge a branch when setting the corresponding > > ticket to p

[sage-release] Re: Re: Re: Release process

2018-05-12 Thread Marc Mezzarobba
Jeroen Demeyer wrote: > I agree that these two are very valid use cases. But both can be > checked easily and probably better by the patchbot. I don't mind if the branch is maintained by a bot rather than a human, but I think it should be easily accessible. -- Marc -- You received this messa

Re: [sage-release] Re: Re: Release process

2018-05-12 Thread Jeroen Demeyer
On 2018-05-12 14:30, Marc Mezzarobba wrote: - detecting and solving conflicts early (without constant back- and-forth with people like myself who work on sage for a few days and then disappear for weeks--which seems to me to be a major cause of bitrotting), - making it easy to test one'

[sage-release] Re: Re: Release process

2018-05-12 Thread Marc Mezzarobba
Jeroen Demeyer wrote: > I don't see how this would be useful. If it's not automated, it's > regularly going to be forgotten or wrong. Even if it would be > automated (and therefore correct), I still don't see the use case Fro me, beside what you said about the patchbot: - detecting and solving c

Re: [sage-release] Re: Release process

2018-05-12 Thread Jeroen Demeyer
On 2018-05-12 10:31, Marc Mezzarobba wrote: it could perhaps be useful to have additional integration branches where the *reviewer* would be supposed to merge a branch when setting the corresponding ticket to positive review. I don't see how this would be useful. If it's not automated, it's re

[sage-release] Re: Release process

2018-05-12 Thread Marc Mezzarobba
Jeroen Demeyer wrote: > To be honest, I think it's not very meaningful to do that without > consulting the release manager. I mean, you can write up all the > documentation that you want; in the end, it's the release manager who > decides what happens. Even without switching to the model Erik is a