Dave / mentors,
since this thread was not marked with [VOTE], would we need to have a
separate vote thread or do you believe this one is enough to proceed?
Thanks,
Matteo
On Tue, Sep 4, 2018 at 12:56 AM Jia Zhai wrote:
> +1.
>
> I am honored to be asked to be on the PMC. Please keep me on the
+1
Thanks Matteo.
-Taylor
> On Sep 5, 2018, at 8:36 PM, Matteo Merli wrote:
>
> Sorry for sending out at very last minute (deadline is today). Please take
> a look.
>
> I have added a paragraph regarding the branding discussion that happen in
> early June (as discussed with Taylor then) since
Sorry for sending out at very last minute (deadline is today). Please take
a look.
I have added a paragraph regarding the branding discussion that happen in
early June (as discussed with Taylor then) since the previous draft was
already out at that point.
---
Pulsar
Pulsar is a highly scal
> The pain comes from issues marked for a bug release milestone but it is
> merged directly to master and never cherry-picked to branch for bugfix
> releases.
> So the release manager has to compare branches and master and also have to
> compare labels, milestones and even look into the details of
My motivation is simple - I would like to see a process for managing
merging pull requests, add labels and milestone and cherry-picks for
releases. Otherwise things just become very messy with different people
merging pull requests in different ways.
I know there was a discussion about the merge s
On Mon, Sep 3, 2018 at 12:14 AM Ivan Kelly wrote:
> > All the bug fixes are deferred to release manager cherry-picking to bug
> fix
> > branches. Since master and branches are quickly diverged with changes,
> > it is very painful for cherry-picks later and there is no clear process
> for
> > cher
