Based on previous discussions it seems the best course of action. I'm
holding the vote open for 3 business days.
I'm +1 binding.
Darin
+1 (if the vote is open to non-comitters)
On Tue, Jun 20, 2017 at 9:22 AM, Darin Johnson wrote:
> Based on previous discussions it seems the best course of action. I'm
> holding the vote open for 3 business days.
>
> I'm +1 binding.
>
> Darin
>
--
Brandon
+1
On Tue, Jun 20, 2017 at 10:13 PM Brandon Gulla
wrote:
> +1 (if the vote is open to non-comitters)
>
>
>
> On Tue, Jun 20, 2017 at 9:22 AM, Darin Johnson wrote:
>
> > Based on previous discussions it seems the best course of action. I'm
> > holding the vote open for 3 business days.
> >
> >
+1
On Tue, Jun 20, 2017 at 10:22 AM, Klaus Ma wrote:
> +1
>
> On Tue, Jun 20, 2017 at 10:13 PM Brandon Gulla
> wrote:
>
> > +1 (if the vote is open to non-comitters)
> >
> >
> >
> > On Tue, Jun 20, 2017 at 9:22 AM, Darin Johnson
> wrote:
> >
> > > Based on previous discussions it seems the bes
I am trying to understand what changed since the last discussion.
If I remember correctly, Ted asked for 3-5 committers to vet the next
release.
4 committers said they were willing. Did I miss something ?
Regards
Swapnil
On Tue, Jun 20, 2017 at 7:35 AM, John Yost wrote:
> +1
>
> On Tue, Jun
Swapnil: I only counted myself and Adam, if there's two additional
committers who are willing to vet the release AND merge commits I'll
consider changing my vote.
Darin
On Tue, Jun 20, 2017 at 12:54 PM, Swapnil Daingade <
swapnil.daing...@gmail.com> wrote:
> I am trying to understand what change
Sorry for chiming in late. I was out of town.
I think we should keep the project going if there is an activity on the project.
I can definitely contribute time to vet the release, review and merge. I may
not be able to actively work on the project as it is not inline with my current
work schedule
I’ve been busy keeping up with a number of things and disengaged for some
time.. I would like to come back to active status as a committer and I’m
willing to commit to:
1. Review and merge of code.
2. Vet releases
Ken
> On Jun 20, 2017, at 10:26 AM, yuliya Feldman
> wrote:
>
> Sorry for ch
@Darin Initially it was you, Adam, me & Santosh who replied.
I think the confusion may have been due to me replying directly to Ted
(instead of reply all)
and later forwarding the reply to dev@myriad. My bad
Now with Yuliya and Ken, we have 6 committers who are willing to vet and
merge commits!