Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

I added two categories: 'CLI' and 'Migration Tool' to the core project in Redmine On Tue, Apr 10, 2018 at 4:42 PM, Dennis Kliban wrote: > I still think the CLI should have it's own project if we are going to > version it separately from Pulp. I hope we do version it separately from > pulpcore. >

[Pulp-dev] Pulp 3 MVP issue cleanup (round 2)

Note: there will be some redundancy with "Various MVP micro-discussions". That email includes all changes to the MVP document, this thread covers all changes to issues with the "Pulp 3 MVP" tag. *Needs attention (please respond on issue):* - single resource OperationPostponed https://pulp.plan

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

I still think the CLI should have it's own project if we are going to version it separately from Pulp. I hope we do version it separately from pulpcore. We should use categories for the installer and migration tool. On Tue, Apr 10, 2018 at 3:01 PM, Jeff Ortel wrote: > > > On 04/10/2018 11:28 AM

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

On 04/10/2018 11:28 AM, Brian Bouterse wrote: OK so to bring it back to how to manage this in Redmine. We've been talking about 'Tags' and I've read a some +1s for their use to track these things and no -1s. I want to identify I think it would be better to use the 'Category' built-in field of

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

I like the idea of making better use of existing Redmine functionality by going with categories over tags if there's no overlap. +1 Dana Walker Associate Software Engineer Red Hat On Tue, Apr 10, 2018 at 1:20 PM, Austin Macdonald wrote: > -0 Ans

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

-0 Ansible installer (since this lives in a totally separate repository) +1 CLI +1 Migration Tool On Tue, Apr 10, 2018 at 12:28 PM, Brian Bouterse wrote: > OK so to bring it back to how to manage this in Redmine. We've been > talking about 'Tags' and I've read a some +1s for their use to track t

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

OK so to bring it back to how to manage this in Redmine. We've been talking about 'Tags' and I've read a some +1s for their use to track these things and no -1s. I want to identify I think it would be better to use the 'Category' built-in field of Redmine. Tags can be multi-selcted, but I don't thi

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

On 04/10/2018 10:15 AM, Jeff Ortel wrote: On 04/04/2018 05:09 PM, Dennis Kliban wrote: Anything that is going to have it's own release cadence should be tracked in it's own project. That way we can assign issues related to specific release of that project to the particular release. Are we

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

On 04/04/2018 05:09 PM, Dennis Kliban wrote: Anything that is going to have it's own release cadence should be tracked in it's own project. That way we can assign issues related to specific release of that project to the particular release. Are we going to release the CLI, Ansible Installer,

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

Looks great.  Thanks for putting this together! On 04/04/2018 02:23 PM, Austin Macdonald wrote: David and I went through all the pulpcore issues that have the "Pulp3 MVP" tag. We added this one to the sprint: * https://pulp.plan.io/issues/3545 These two need to be updated before we can mo

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

On Tue, Apr 10, 2018 at 8:17 AM, David Davis wrote: > So the only content filter we have on the MVP doc is repo version. I think > this might be tricky and you can already view content for a repository > version (ie /api/v3/repositories//versions//content) so I > think we should just leave this o

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

So the only content filter we have on the MVP doc is repo version. I think this might be tricky and you can already view content for a repository version (ie /api/v3/repositories//versions//content) so I think we should just leave this out of the MVP. David On Mon, Apr 9, 2018 at 12:19 PM, Austi

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

Here's another one that needs to be groomed and added to the sprint(thanks kersom!) - (@David maybe?) Content Filters https://pulp.plan.io/issues/3084 All of these have been added to the sprint: - https://pulp.plan.io/issues/3552 - https://pulp.plan.io/issues/3395 - https://pulp.pla

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

I expect our CLI to be agnostic of the plugins. With that in mind, when we have a problem with the CLI it's an actual problem with the CLI. Any plugin specific problems are probably issues with the REST API. On Thu, Apr 5, 2018 at 9:07 AM, Ina Panova wrote: > I would try for now to minimize the

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

I would try for now to minimize the number of projects because they are difficult to maintain and stick to Tags field until we clearly define what goes where. Some thoughts: if we put CLI as a separate project, where we'd put some plugin specific, for example PRM, cli section/command/option reques

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

On Wed, Apr 4, 2018 at 6:09 PM, Dennis Kliban wrote: > Anything that is going to have it's own release cadence should be tracked > in it's own project. That way we can assign issues related to specific > release of that project to the particular release. > Are we going to release the CLI, Ansible

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

Anything that is going to have it's own release cadence should be tracked in it's own project. That way we can assign issues related to specific release of that project to the particular release. Are we going to release the CLI, Ansible Installer, and the Migration tool as part of one version of P

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

> > >> I'm hoping to continue the "Infrastructure" Redmine project for things > like website hosting. I see what you mean though because it will be > developed and released separately. I think we're in a similar situation for > 3 things: the ansible installer, the migration tool, and CLI, and for e

Re: [Pulp-dev] Pulp 3 MVP Issue Cleanup

All this looks good to me, ty so much for organizing. I left 1 inline comment On Wed, Apr 4, 2018 at 3:23 PM, Austin Macdonald wrote: > David and I went through all the pulpcore issues that have the "Pulp3 MVP" > tag. > > We added this one to the sprint: > >- https://pulp.plan.io/issues/3545

[Pulp-dev] Pulp 3 MVP Issue Cleanup

David and I went through all the pulpcore issues that have the "Pulp3 MVP" tag. We added this one to the sprint: - https://pulp.plan.io/issues/3545 These two need to be updated before we can move forward: - @dalley https://pulp.plan.io/issues/3505 - @asmacdo https://pulp.plan.io/issue