[Pulp-dev] 2.15.2 dev freeze -- 22:00 UTC Tuesday Feb 13th

Any Pulp2 core or plugin code that you want included in the 2.15.2 release must be: a) merged to master by 22:00 UTC, Tuesday Feb 13th b) be associated with a bugfix issue. stories, refactors, and tasks are not included in z-stream releases. This is a new process so send any questions or ideas!

Re: [Pulp-dev] Release Announcing and Versioning

The first one or two releases we do this for, we'll do by hand, but here is the redmine ticket on the automation to match: https://pulp.plan.io/issues/3348 Can someone groom or comment on it? On Tue, Feb 6, 2018 at 3:20 PM, Jeremy Audet wrote: > > Nope, it does not. THe

[Pulp-dev] Adding Model.created.

A few of our models have a field: created = models.DateTimeField(auto_now_add=True) To support ordering needed by a FilePlugin use case, I'm planning to add Content.created as it seems generally useful and I believe will be needed by most plugins. This raises a more general question: should

Re: [Pulp-dev] Adding Model.created.

+1. Also, wondering if we should add a Model.last_updated field as well. David On Mon, Feb 12, 2018 at 12:22 PM, Jeff Ortel wrote: > A few of our models have a field: > > created = models.DateTimeField(auto_now_add=True) > > To support ordering needed by a FilePlugin use

Re: [Pulp-dev] Adding Model.created.

+1 to created and +1 to updated. On Mon, Feb 12, 2018 at 3:52 PM, David Davis wrote: > +1. Also, wondering if we should add a Model.last_updated field as well. > > > David > > On Mon, Feb 12, 2018 at 12:22 PM, Jeff Ortel wrote: > >> A few of our models

Re: [Pulp-dev] Adding Model.created.

FYI: https://github.com/pulp/pulp/pull/3325 On 02/12/2018 03:01 PM, Dennis Kliban wrote: +1 to created and +1 to updated. On Mon, Feb 12, 2018 at 3:52 PM, David Davis > wrote: +1. Also, wondering if we should add a Model.last_updated

Re: [Pulp-dev] Plugin Writer's Coding Workshop Feedback

You forgot to mention the huge amount of fun, we had while debugging the designated pulp3 development environment. But i agree, that focussing on one environment (that fits all, including core and plugin development) sounds reasonable. And the vagrant setup with ansible roles sounds like my first