Branko Čibej <brane_at_apache.org> writes:
>> I know this has been discussed before, but it was never made reality.
>> On last week's hackathon we also didn't come to a full consensus on
>> various details. But I think we should simply work out those details,
>> hopefully come to some compromise, and if so, JFD it.
> It has been discussed before and for a while we even did it this way.
> The problem is that we're again at the point where we have to find a
> reluctant volunteer to RM any release we want to make. So ...
> "There's no 'we' in Team" :p Some individual has to step up and do
> this. The sort of release train you describe needs someone to drive it,
> to whit, a "permanent" release manager. No amount of documentation and
> schedules and good intentions will make this happen all by itself.
I concur that the time-based releases most likely won't happen just based
on the agreement, and that there has to be a person driving them.
Perhaps, we could try this approach by finding a volunteer responsible for
RM-ing the 1.11 release — for example, right after 1.10 is released.
Received on 2017-11-28 14:04:16 CET