[Pulp-dev] 2.16.0 dev freeze -- 22:00 UTC Tuesday, March 13th

Any Pulp2 core or plugin code that you want included in the 2.16.0 release must be: a) merged to master by 22:00 UTC, March 13th b) associated with a story, refactor, task or a bugfix issue. If you want/need to adjust this date, please reply on list. Thanks, Tanya

[Pulp-dev] Next Community Demo -- Tomorrow March 14th

Several folks have things to demo and wanted to demo earlier, so we're going to have a special Pi Day community demo tomorrow, March 14th. If you have something to add consider adding it here: https://etherpad.net/p/Pulp_Community_Demo_Agenda We accept entries right up until the start time.

Re: [Pulp-dev] Pulp Community Demo - Tomorrow March 14

wrong-list, sorry, sending to pulp-list now. On Tue, Mar 13, 2018 at 1:08 PM, Brian Bouterse wrote: > A special Pi Day community demo will be broadcast live via YouTube. The > tentative agenda is: > > > * sync rich dependencies, milan, Pulp2 > > * SUSE Errata support,

Re: [Pulp-dev] Importer Name

> > On Mon, Mar 12, 2018 at 9:50 AM, Justin Sherrill > wrote: > >> I'm fairly apathetic to a name change. It would be annoying to us in >> katello land, but not really a huge deal either way. I don't think >> importer a bad name, as it does hold configuration around

[Pulp-dev] Plugin relationship to tasks

tldr; I am running with an idea that Milan brought up. I think this will create a simpler user experience while providing an obvious pattern to plugin writers. This pattern will offer greater plugin control and flexibility. Problem: Tasks that add/remove content to a repo (which creates

Re: [Pulp-dev] 2.16.0 dev freeze -- 22:00 UTC Tuesday, March 13th

The code for 2.16.0 is now frozen. There are a total of 9 stories/tasks/refactors prepared for the release: https://pulp.plan.io/issues?query_id=61 Tanya On Tue, Mar 13, 2018 at 11:05 AM, Tatiana Tereshchenko wrote: > Any Pulp2 core or plugin code that you want included