tl;dr @daviddavis and I will try to handle the announcing of the builds and
document a process to have others help do in the future.
In some conversations with the folks who make the Pulp2 builds, they want
to focus only on building and transition the announcing of builds back to
developers. I
> Nope, it does not. THe tooling I'm looking at modifying to use with
pulp from my end can handle that situation, as wel as multiple commits to
an issue.
Great!
___
Pulp-dev mailing list
Pulp-dev@redhat.com
On Tue, 2018-02-06 at 14:32 -0500, Jeremy Audet wrote:
> > Also it would verify that each issue has an associated commit because the
> > build machinery will fail if there are fewer commits.
>
> Does this mean that a single commit can't fix two issues? If so, this seems
> like a case of the
> Also it would verify that each issue has an associated commit because the
build machinery will fail if there are fewer commits.
Does this mean that a single commit can't fix two issues? If so, this seems
like a case of the tail wagging the dog.
___
