[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changing release process for release candidates

If it’s not clear, “release manager” is an important role. The RM is responsible for the key events in the release - building a release candidate (including signatures), putting it in a place that it can be viewed, writing release notes, starting a vote, closing the vote, writing the release announcement.

There MUST be a vote on the release, but for other parts of the process it’s best if the the RM doesn’t hang around waiting for permission.

> On Aug 6, 2018, at 4:52 PM, Gian Merlino <gian@xxxxxxxxxx> wrote:
> It sounds good to me, it streamlines things a bit and seems to be what
> other projects are doing. As Julian pointed out in the other thread it
> still pays to have someone "managing" the release and to have some
> discussion about when's the right time to start a release branch. The
> "release manager" job has rotated through a few different people over the
> past few major releases, which is good.
> On Mon, Aug 6, 2018 at 3:20 PM Jihoon Son <jihoonson@xxxxxxxxxx> wrote:
>> Hi all,
>> Our current release process for RCs begins with a vote. It usually takes up
>> a few days, but is actually not a mandatory process for creating RCs. If we
>> can reach consensus without explicit votes, we can expect the faster
>> release in the future.
>> The original discussion is available at
>> https://lists.apache.org/thread.html/d887f0c6e23f1625e549389c08a9a5e74a7a24db4d5e007b6e8d10f6@%3Cdev.druid.apache.org%3E
>> .
>> Welcome any idea.
>> Best,
>> Jihoon

To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxx