[Pulp-dev] 2.16.4 Dev Freeze — Monday, July 16 at 21:00 UTC

Any Pulp2 core or plugin code that you want included in the 2.16.4 release must be: a) merged to 2-master by 21:00 UTC, July 16th b) associated with a story, refactor, task or a bugfix issue. The release page containing the schedule is here:

Re: [Pulp-dev] 2.17.0 Release request

Austin has agreed to be 2.17.0 build prime and handle responsibilities to ensure a smooth build process. Given the desire to ensure we deliver all requested 2.17.0 content in a timely manner, I'd like for us to use the milestone function of Redmine: https://pulp.plan.io/versions/63 I'll work

Re: [Pulp-dev] Revising PUPs

+1 Dana Walker Associate Software Engineer Red Hat On Mon, Jul 9, 2018 at 9:05 AM, Daniel Alley wrote: > +1 > > On Mon, Jul 9, 2018 at 9:02 AM, Milan Kovacik wrote: > >> Hey David, >> >> thanks, +1 >> >> -- >> milan >> >> On Mon, Jul 9, 2018 at

Re: [Pulp-dev] Revising PUPs

+1 On Mon, Jul 9, 2018 at 9:02 AM, Milan Kovacik wrote: > Hey David, > > thanks, +1 > > -- > milan > > On Mon, Jul 9, 2018 at 1:49 PM, David Davis wrote: > >> I’ve opened a PR with the process on how to revise a PUP. >> Reviews/feedback are welcome: >> >> https://github.com/pulp/pups/pull/11

Re: [Pulp-dev] Revising PUPs

Hey David, thanks, +1 -- milan On Mon, Jul 9, 2018 at 1:49 PM, David Davis wrote: > I’ve opened a PR with the process on how to revise a PUP. Reviews/feedback > are welcome: > > https://github.com/pulp/pups/pull/11 > > I’d also like to call a vote on this proposed change. Here’s the voting >

Re: [Pulp-dev] Revising PUPs

I’ve opened a PR with the process on how to revise a PUP. Reviews/feedback are welcome: https://github.com/pulp/pups/pull/11 I’d also like to call a vote on this proposed change. Here’s the voting model from PUP-1: +1: "Will benefit the project and should definitely be adopted." +0: "Might