pcp
[Top] [All Lists]

Re: [pcp] pcp updates: pmmgr, pmwebd

To: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Subject: Re: [pcp] pcp updates: pmmgr, pmwebd
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 28 Apr 2015 18:42:37 -0400 (EDT)
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <553F4BA8.5000001@xxxxxxxxxx>
References: <20150421224405.GN6822@xxxxxxxxxx> <5536E65F.50600@xxxxxxxxxx> <20150422000949.GP6822@xxxxxxxxxx> <553F4BA8.5000001@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: tZQDS+7hx5dltPWInM7gnCQtXdSoGQ==
Thread-topic: pcp updates: pmmgr, pmwebd

----- Original Message -----
> [...]
> Howdy Frank, will I just pull in all your changes? Or cherry-pick
> only the pmwebd changes? Your tree of unmerged stuff seems to go back
> to the commit listed below I think. The pmmgr changes are marked as
> 'blocked' on https://trello.com/b/5t9Ml341/release-task-tracking.

The pmmgr changes are blocked on fixes for these two bugs:
http://git.pcp.io/bugzilla/show_bug.cgi?id=1105
http://git.pcp.io/bugzilla/show_bug.cgi?id=1106

It's inappropriate to merge this before those are fixed (esp. since the
feature is apparently useless without 1106) - if we accept this sort of
'Not My Problem' attitude, we cultivate a class of contributor working
primarily on features in their pet project(s), and less on fixing core
PCP bugs for the greater good.

No reason for merging it at this stage has been provided - is there one?
The situation was explained and the path to resolving it discussed - so,
I'd suggest it can wait.  Or are there legitimate reasons for merging 
before those bugs are fixed?  Taa.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>