Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: swill <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1658-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1658-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #1658: Added an additional JSON diff output to the ApiXmlDo...
Content-Type: text/plain
Message-Id: <20160912174829.3C27BE0158@git1-us-west.apache.org>
Date: Mon, 12 Sep 2016 17:48:29 +0000 (UTC)
archived-at: Mon, 12 Sep 2016 17:48:31 -0000

Github user swill commented on the issue:

    https://github.com/apache/cloudstack/pull/1658
  
    @jburwell since 4.6 we have effectively had the RM merge everything.  I am not saying that is required, or even specified anywhere, but the reason we have been doing that was because the RM was actively maintaining the stability of master.  Regardless of who is merging what, my question stands.  How are we validating the stability of master right now?  All the other details are basically irrelevant, this is the single most important question...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---