<div dir="ltr"><div>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 think a single issue will need to be a CLI and an Installer and a $other_tag all at once (multi-selected). Categories are a single selection which seems more appropriate. We also make little use of them today and they are built into all Issues redmine has.<br><br></div><div>Should I make a Categories for 'Ansible Installer', 'CLI' and 'Migration Tool' in the Pulp project on Redmine?<br><br></div><div>Other suggestions and ideas are welcome.<br></div><div><br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 10, 2018 at 11:23 AM, Jeff Ortel <span dir="ltr"><<a href="mailto:jortel@redhat.com" target="_blank">jortel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span>
<br>
<br>
<div class="m_-7669174744155202874m_-5962239689157859736moz-cite-prefix">On 04/10/2018 10:15 AM, Jeff Ortel
wrote:<br>
</div>
<blockquote type="cite">
<br>
<br>
<div class="m_-7669174744155202874m_-5962239689157859736moz-cite-prefix">On 04/04/2018 05:09 PM, Dennis Kliban
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>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. <br>
<br>
</div>
Are we going to release the CLI, Ansible Installer, and the
Migration tool as part of one version of Pulp or will these
all be versioned separately?<br>
</div>
</blockquote>
<br>
Separately.<br>
</blockquote>
<br></span>
Meant to clarify. The CLI can be released separately but I think
the migration tool needs to be released in step with Pulp. As for
the installer .. seems like that also needs to be released in step
with Pulp.<span><br>
<br>
<blockquote type="cite"> <br>
<blockquote type="cite">
<div dir="ltr"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Apr 4, 2018 at 5:41 PM,
Austin Macdonald <span dir="ltr"><<a href="mailto:austin@redhat.com" target="_blank">austin@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><span>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
<div class="m_-7669174744155202874m_-5962239689157859736m_-5339351893109439989m_4148905111584813164gmail-h5">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div>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 each of
them we should either make their own
Redmine projects or a tag under Pulp. We
already have many Redmine projects and
they are kind of a pain so I want to
float a tags based approach for
feedback. Perhaps keeping them out of
"Pulp" means that we remove all the
existing tags from them and tag them
with new tags like 'Ansible Installer',
'2to3 Migration' and 'CLI'?</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span>
<div>I had hoped that someday there would be a
separate group of committers for pulp/devel or
wherever we keep it. Also, I wouldnt want
potential users/PMs to see a "bug count" that
includes non-user facing issues. These concerns
are trivial though, and if projects are a pain,
I'm fine with keeping Tags.</div>
<div><br>
</div>
<div>Since projects are a pain, can we get rid of
the "external" project? <a href="https://pulp.plan.io/projects/external/issues" target="_blank">https://pulp.plan.io/projects/<wbr>external/issues</a></div>
<div><br>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="m_-7669174744155202874m_-5962239689157859736mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
Pulp-dev mailing list
<a class="m_-7669174744155202874m_-5962239689157859736moz-txt-link-abbreviated" href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a>
<a class="m_-7669174744155202874m_-5962239689157859736moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-dev" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</span></div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div></div>