Just a quick update: voting on PUP-3 ended Monday Oct 8th. PUP-3 was
approved with nine +1 votes. I think the next step is to work on a
transition plan. If you’d like to be involved with this, please let me know.
More updates next week.
David
On Wed, Oct 4, 2017 at 9:10 AM, wrote:
> +1
>
> __
+1
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
+1
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
+1
On Mon, Oct 2, 2017 at 3:42 PM, Bihan Zhang wrote:
> +1
>
> On Oct 2, 2017 9:28 AM, "Ina Panova" wrote:
>
>> +1
>>
>>
>>
>>
>> Regards,
>>
>> Ina Panova
>> Software Engineer| Pulp| Red Hat Inc.
>>
>> "Do not go where the path may lead,
>> go instead where there is no path and leave
+1
On Oct 2, 2017 9:28 AM, "Ina Panova" wrote:
> +1
>
>
>
>
> Regards,
>
> Ina Panova
> Software Engineer| Pulp| Red Hat Inc.
>
> "Do not go where the path may lead,
> go instead where there is no path and leave a trail."
>
> On Mon, Oct 2, 2017 at 2:45 PM, Daniel Alley wrote:
>
>> +1
+1
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Mon, Oct 2, 2017 at 2:45 PM, Daniel Alley wrote:
> +1
>
> On Mon, Oct 2, 2017 at 7:37 AM, Michael Hrivnak
> wrote:
>
>> +1
>>
+1
On Mon, Oct 2, 2017 at 7:37 AM, Michael Hrivnak wrote:
> +1
>
> On Fri, Sep 29, 2017 at 10:08 AM, Brian Bouterse
> wrote:
>
>> +1
>>
>> I believe the cherry picking approach will avoid merge-forward problems
>> we've experienced, allow for less friction during community contribution,
>> and
+1
On Fri, Sep 29, 2017 at 10:08 AM, Brian Bouterse
wrote:
> +1
>
> I believe the cherry picking approach will avoid merge-forward problems
> we've experienced, allow for less friction during community contribution,
> and create a more stable project overall.
>
> On Fri, Sep 29, 2017 at 9:53 AM,
+1
I believe the cherry picking approach will avoid merge-forward problems
we've experienced, allow for less friction during community contribution,
and create a more stable project overall.
On Fri, Sep 29, 2017 at 9:53 AM, Dennis Kliban wrote:
> +1
>
> On Fri, Sep 29, 2017 at 9:17 AM, David Da
+1
On Fri, Sep 29, 2017 at 9:17 AM, David Davis wrote:
> I went back and looked at PUP-3 and it does lay out some of the items
> @pcreech mentions although at a higher, more general level. I’ll leave the
> document as is unless someone disagrees.
>
> With that in mind, let's go ahead and vote on
I went back and looked at PUP-3 and it does lay out some of the items
@pcreech mentions although at a higher, more general level. I’ll leave the
document as is unless someone disagrees.
With that in mind, let's go ahead and vote on PUP-3. We’ll end the voting
on October 8th which is about 10 days
Thanks @pcreech for all the comments. I also believe that switching to a
cherry-picking model will provide many benefits.
As a general FYI, the way PUP-3 is written, it allows us to adopt it
(assuming it passes at vote) and then figure out how to roll it out later
in coordination w/ release engine
Patrick,
Thanks for the feedback. I’d like to update PUP-3 in the next couple days
with the pain points you mention.
Also, I’d love the idea of having some tooling that tells us exactly which
commits to cherry pick into which release branch. I think we should have
this in place before we switch t
Since I was one of the early voices against cherrypicking during the initial
vote, I figured I'd send this e-mail along with some points that have helped me
be in favor of cherry picking before voting
starts.
In taking over the release engineering process, I have gained some perspective
on our
I’d like to extend the discussion (and put off voting) for another week
since we’re wrapping up the alpha release of Pulp 3 this week. Any
objections? If not, then we’ll start voting on September 26th.
David
On Tue, Sep 12, 2017 at 12:23 PM, David Davis wrote:
> Previously we had a vote on the
Previously we had a vote on the proposal to change our git workflow mainly
by using cherry-picks instead of merging changes forward. This proposal,
PUP-3, can be viewed here:
https://github.com/daviddavis/pups/blob/pup3/pup-0003.md
When we had the vote though, it became clear that there was some
16 matches
Mail list logo
