On 06/04/2020 13:28, Cantor, Scott wrote:
On 4/6/20, 8:24 AM, "Roger Leigh" wrote:
It should be pretty simple for any Apache contributor to push any
potential update as a feature branch to GitBox and then check the CI run
passes, prior to merging to an integration branch. This will ensure
On 4/6/20, 8:24 AM, "Roger Leigh" wrote:
> It should be pretty simple for any Apache contributor to push any
> potential update as a feature branch to GitBox and then check the CI run
> passes, prior to merging to an integration branch. This will ensure
> that no regressions should be
On 06/04/2020 12:42, Cantor, Scott wrote:
On 4/6/20, 7:21 AM, "Roger Leigh" wrote:
You can simply push your feature branch and wait for the tests to pass before
merging to and pushing the integration
branch.
I'm not sure that there's been adequate discussion of any actual development
On 4/6/20, 7:21 AM, "Roger Leigh" wrote:
> You can simply push your feature branch and wait for the tests to pass
> before merging to and pushing the integration
> branch.
I'm not sure that there's been adequate discussion of any actual development
process for using git, or any policies put
Dear all,
CI testing was present prior to the switch from SVN to GitBox, but
needed re-enabling by Infra for the new repository. It's re-enabled
since yesterday (see INFRA-20073), and both the xerces-3.2 and master
branch are passing for both Travis and AppVeyor:
