[Pulp-dev] Pulp 3 release quality
dkliban at redhat.com
Mon Apr 16 20:30:11 UTC 2018
The documentation has been updated.
On Fri, Apr 6, 2018 at 2:52 PM, Dennis Kliban <dkliban at redhat.com> wrote:
> I have updated the redmine issue to include a page in the contributors
> guide on "Continuous Integration" as a deliverable. That page will include
> that quote.
>  https://pulp.plan.io/issues/3530
> On Fri, Apr 6, 2018 at 2:06 PM, Robin Chan <rchan at redhat.com> wrote:
>> Thanks for putting this together. I don't see any responses on this
>> thread and take that to mean there were no concerns about this proposal.
>> Would this process/responsibility change need to go anywhere? (Side
>> questions, was this technically a PUP?)
>> "author of the PR would need to be responsible for making additional PRs
>> to pulp_file and/or pulp-smash to fix the smash tests"
>> I think this is minor enough to skip some process, however I would like
>> to see the above quote go into the developers guide. A new contributor
>> shouldn't have to glean through mail list archives to understand this new
>> On Tue, Mar 27, 2018 at 8:22 PM, Dennis Kliban <dkliban at redhat.com>
>>> One of the requirements for this plan to work is making sure that pulp,
>>> pulp_file, and pulp-smash always continue working together. This means that
>>> any time we have a PR that breaks pulp-smash tests, the author of the PR
>>> would need to be responsible for making additional PRs to pulp_file and/or
>>> pulp-smash to fix the smash tests. To enforce this requirement using
>>> Travis, I have filed 2 tasks[0,1] in redmine that I would like to get
>>> groomed and added to the sprint. I plan on working on these tasks as I
>>> introduce a change that will result from resolving issue 3488.
>>>  https://pulp.plan.io/issues/3530
>>>  https://pulp.plan.io/issues/3531
>>>  https://pulp.plan.io/issues/3488
>>> On Fri, Mar 23, 2018 at 2:37 PM, Dennis Kliban <dkliban at redhat.com>
>>>> I've started putting together a Continuous Delivery of Pulp 3 page
>>>> on our wiki.
>>>> This page outlines a plan for how we can ensure and prove the quality
>>>> of Pulp 3 releases by relying on pulp-smash tests and unit tests.
>>>> This plan enables anyone to improve the quality of Pulp 3 releases
>>>> through contributions to pulp-smash and unit tests.
>>>> Please take a look at the plan and provide feedback on this thread or
>>>> feel free to make edits directly on the page.
>>>>  https://pulp.plan.io/projects/pulp/wiki/Continuous_Delivery_
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev