I fixed queries: - MODIFIED - No Release - MODIFIED not tagged for release
They are basically the same, just show the same issues in different format. FYI, those are used in the release process for Pulp 2 and also by QE to see what's already merged for the upcoming Pulp 2 releases. NOTE: Now, with Pulp 2 tag, it's very critical to set it on *every Pulp 2 issue/story*, because identifying issues which lack Pulp 2 tag will be a pain for release shepherds - there are hundreds of issues in MODIFIED state without Pulp 2 tag. Let me know if I miss something and there is a way to identify a missing Pulp 2 tag. Brian, Any ideas how to fix pulp3 docs query? https://pulp.plan.io/issues?query_id=128 I think it needs two conditions for the same field: tag is `Documentation` and tag is not `Pulp 2`. Tanya On Thu, Apr 25, 2019 at 7:18 PM Brian Bouterse <bbout...@redhat.com> wrote: > David and I removed the 'Pulp 3', 'Pulp3 MVP', and 'Pulp 3 RC Blocker' > tags from Redmine today. Attached are the 3 csv's for posterity showing the > issues they tagged. Any issue not tagged with 'Pulp 2' in any redmine > project is a Pulp3 issue, so Pulp3 is the default issue type now. > > There are two saved queries that were updated to match. > 3.0 query - this is for all issues that would block the 3.0 GA - > https://pulp.plan.io/issues?query_id=77 > 3.1+ query - this is for all issues that are not on the 3.0 release - > https://pulp.plan.io/issues?query_id=130 > > Thank you! > Brian > > > On Tue, Apr 23, 2019 at 4:20 PM Brian Bouterse <bbout...@redhat.com> > wrote: > >> David and I are planning to remove the tags mentioned on this thread on >> Thursday the 25th and send the csv's that day with the record. We will also >> disable updates for issues during that time to minimize the spam. >> >> If there are any concerns, questions, or people want more time to discuss >> please reach out. >> >> In terms of tag use going forward, use the 'Pulp 2' tag for Pulp 2 >> issues. Anything without the 'Pulp 2' tag is a Pulp3 items. The Pulp3 items >> with the milestone 3.0 should indicate all tickets included in the 3.0 >> milestone for pulpcore, i.e ( https://pulp.plan.io/versions/57 ). I >> think we should delete the 3.0.0 "platform release" (which is different) >> since we don't use it and it only is confuses us. That was created a long >> time ago when we had no pulp3 processes yet. Here are issues with that set >> only 12 of them ( https://tinyurl.com/y3xknewl ). We should do this on >> Thursday too. >> >> >> On Tue, Apr 16, 2019 at 1:08 PM David Davis <davidda...@redhat.com> >> wrote: >> >>> I'll wait on removing the Pulp 3 tags until Friday to leave more time >>> for discussion. >>> >>> I noticed that there's also a "3.0.0" option for the Platform Release >>> field. Should we set it for all issues that are at Modified+ with the Pulp >>> 3 tag? >>> >>> David >>> >>> >>> On Tue, Apr 16, 2019 at 9:26 AM Brian Bouterse <bbout...@redhat.com> >>> wrote: >>> >>>> The thinking is that keeping 'historical' tags mixed in with actual >>>> tags will make the 'Tag's field less usable and more confusing. The removal >>>> of these historical tags uses the csv export serving at the historical >>>> record, which was the best/easiest way we could come up with to store that >>>> long-term without making even more changes to Redmine. Ideas and >>>> suggestions are welcome. >>>> >>>> As an aside, next time we'll disable email updates during these >>>> mass-changes. Thanks for the suggestion @pcreech. >>>> >>>> >>>> On Tue, Apr 16, 2019 at 6:25 AM Ina Panova <ipan...@redhat.com> wrote: >>>> >>>>> Curiosity question - what we will benefit from removing tags Pulp 3, >>>>> Pulp 3 MVP, and Pulp 3 RC Blocker? >>>>> Except of tons notifications received? I would keep them on the issues >>>>> as they are, for historical reasons of pulp3 development. >>>>> >>>>> -------- >>>>> Regards, >>>>> >>>>> Ina Panova >>>>> Software Engineer| Pulp| Red Hat Inc. >>>>> >>>>> "Do not go where the path may lead, >>>>> go instead where there is no path and leave a trail." >>>>> >>>>> >>>>> On Mon, Apr 15, 2019 at 10:18 PM David Davis <davidda...@redhat.com> >>>>> wrote: >>>>> >>>>>> The Pulp 2 tag has been created in redmine. Please start using it to >>>>>> tag issues that apply to Pulp 2. We’re also applying the new Pulp 2 tag >>>>>> to >>>>>> issues without the Pulp 3 tag in the following projects in redmine: >>>>>> >>>>>> Debian >>>>>> Crane >>>>>> Docker >>>>>> Nectar >>>>>> OSTree >>>>>> Packaging >>>>>> Pulp >>>>>> Puppet >>>>>> Python >>>>>> RPM >>>>>> >>>>>> This includes about 1161 issues. Please let us know if there are any >>>>>> issues that shouldn’t be tagged or ones we have missed. >>>>>> >>>>>> The final step which we hope to do on Wednesday will be to remove the >>>>>> tags: Pulp 3, Pulp 3 MVP, and Pulp 3 RC Blocker. We’ll make csv backups >>>>>> for >>>>>> each before we remove them. >>>>>> >>>>>> David >>>>>> >>>>>> >>>>>> On Mon, Apr 15, 2019 at 2:52 PM Mike DePaulo <mikedep...@redhat.com> >>>>>> wrote: >>>>>> >>>>>>> +1 to the "Pulp 2" tag. >>>>>>> (I was just thinking this.) >>>>>>> >>>>>>> On Fri, Apr 12, 2019 at 4:28 PM Austin Macdonald < >>>>>>> amacd...@redhat.com> wrote: >>>>>>> >>>>>>>> Pulp2 tag sounds great to me. >>>>>>>> >>>>>>>> On Fri, Apr 12, 2019, 16:23 Brian Bouterse <bbout...@redhat.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> +1 to making a 'Pulp 2' tag >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Apr 12, 2019 at 3:16 PM David Davis <davidda...@redhat.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I’ve been thinking through this and I think there are 3 steps to >>>>>>>>>> perform: >>>>>>>>>> >>>>>>>>>> 1. Create a Pulp 2 tag >>>>>>>>>> 2. Assign the Pulp 2 tag to issues not tagged with Pulp 3 >>>>>>>>>> 3. Remove the Pulp 3 tag >>>>>>>>>> >>>>>>>>>> Does that make sense? If so, I’d like to perform 1 and create the >>>>>>>>>> Pulp 2 tag in the next few days so we can start adding it to issues. >>>>>>>>>> >>>>>>>>>> I’ll follow up with more concrete plans for steps 2 and 3 next >>>>>>>>>> week. >>>>>>>>>> >>>>>>>>>> David >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Apr 11, 2019 at 11:10 AM David Davis < >>>>>>>>>> davidda...@redhat.com> wrote: >>>>>>>>>> >>>>>>>>>>> Cool, I will try to think through how to transition and we can >>>>>>>>>>> discuss at the team meeting Monday. >>>>>>>>>>> >>>>>>>>>>> David >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, Apr 11, 2019 at 11:04 AM Ina Panova <ipan...@redhat.com> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> +1 to create a pulp2 tag after mass-close >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -------- >>>>>>>>>>>> Regards, >>>>>>>>>>>> >>>>>>>>>>>> Ina Panova >>>>>>>>>>>> Software Engineer| Pulp| Red Hat Inc. >>>>>>>>>>>> >>>>>>>>>>>> "Do not go where the path may lead, >>>>>>>>>>>> go instead where there is no path and leave a trail." >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Apr 11, 2019 at 3:48 PM Brian Bouterse < >>>>>>>>>>>> bbout...@redhat.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Great idea David! >>>>>>>>>>>>> >>>>>>>>>>>>> Once we get through tomorrow's mass-close, let's plan a >>>>>>>>>>>>> transition to remove the Pulp3 tag and introduce a Pulp 2 tag >>>>>>>>>>>>> instead. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Apr 11, 2019 at 9:34 AM Dana Walker < >>>>>>>>>>>>> dawal...@redhat.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> +1 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Dana Walker >>>>>>>>>>>>>> >>>>>>>>>>>>>> Software Engineer >>>>>>>>>>>>>> >>>>>>>>>>>>>> Red Hat >>>>>>>>>>>>>> >>>>>>>>>>>>>> <https://www.redhat.com> >>>>>>>>>>>>>> >>>>>>>>>>>>>> <https://red.ht/sig> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Apr 11, 2019 at 9:22 AM Daniel Alley < >>>>>>>>>>>>>> dal...@redhat.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I feel like using the Pulp 3 tag is suboptimal since we are >>>>>>>>>>>>>>>> closing out most of our Pulp 2 issues and a majority of the new >>>>>>>>>>>>>>>> bugs/tasks/stories are for Pulp 3. Wouldn’t it make more sense >>>>>>>>>>>>>>>> to create a >>>>>>>>>>>>>>>> Pulp 2 tag and use it on the rare Pulp 2 issues that get filed? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Agreed, +1 to having a "Pulp 2" tag to replace the Pulp 3 >>>>>>>>>>>>>>> tag. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Apr 11, 2019 at 9:19 AM David Davis < >>>>>>>>>>>>>>> davidda...@redhat.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I feel like using the Pulp 3 tag is suboptimal since we are >>>>>>>>>>>>>>>> closing out most of our Pulp 2 issues and a majority of the new >>>>>>>>>>>>>>>> bugs/tasks/stories are for Pulp 3. Wouldn’t it make more sense >>>>>>>>>>>>>>>> to create a >>>>>>>>>>>>>>>> Pulp 2 tag and use it on the rare Pulp 2 issues that get filed? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> David >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, Apr 11, 2019 at 8:27 AM Ina Panova < >>>>>>>>>>>>>>>> ipan...@redhat.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> +1 to handle tag during the triage process >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -------- >>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Ina Panova >>>>>>>>>>>>>>>>> Software Engineer| Pulp| Red Hat Inc. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> "Do not go where the path may lead, >>>>>>>>>>>>>>>>> go instead where there is no path and leave a trail." >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Apr 2, 2019 at 3:53 PM Brian Bouterse < >>>>>>>>>>>>>>>>> bbout...@redhat.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> +1 to Tanya's suggestion. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Also I have an action item to start a separate thread on >>>>>>>>>>>>>>>>>> how we can plan-and-then-close all pulp2 bugs that we are >>>>>>>>>>>>>>>>>> not actively >>>>>>>>>>>>>>>>>> working on. I wanted to mention it here to identify it as a >>>>>>>>>>>>>>>>>> possible >>>>>>>>>>>>>>>>>> resolution to this issue since it was related. I'll send >>>>>>>>>>>>>>>>>> this today. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Tue, Apr 2, 2019 at 7:54 AM Tatiana Tereshchenko < >>>>>>>>>>>>>>>>>> ttere...@redhat.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> In my opinion, it's a part of triage or grooming process. >>>>>>>>>>>>>>>>>>> Triage leader (for issues) and a person who grooms the >>>>>>>>>>>>>>>>>>> task should pay attention to the tags. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Tanya >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Tue, Apr 2, 2019 at 1:47 PM David Davis < >>>>>>>>>>>>>>>>>>> davidda...@redhat.com> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Looking in redmine at our current sprint, I see several >>>>>>>>>>>>>>>>>>>> issues that don’t have Pulp 3 tag that should. Here are >>>>>>>>>>>>>>>>>>>> some: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> https://pulp.plan.io/issues/4587 >>>>>>>>>>>>>>>>>>>> <https://pulp.plan.io/issues/4587> >>>>>>>>>>>>>>>>>>>> https://pulp.plan.io/issues/4595 >>>>>>>>>>>>>>>>>>>> <https://pulp.plan.io/issues/4595> >>>>>>>>>>>>>>>>>>>> https://pulp.plan.io/issues/4577 >>>>>>>>>>>>>>>>>>>> <https://pulp.plan.io/issues/4577> >>>>>>>>>>>>>>>>>>>> https://pulp.plan.io/issues/4576 >>>>>>>>>>>>>>>>>>>> <https://pulp.plan.io/issues/4576> >>>>>>>>>>>>>>>>>>>> https://pulp.plan.io/issues/4545 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> <https://pulp.plan.io/issues/4545>Talking with the QE >>>>>>>>>>>>>>>>>>>> team, it’s difficult for them to get a feel for how much >>>>>>>>>>>>>>>>>>>> Pulp 2 vs Pulp 3 >>>>>>>>>>>>>>>>>>>> work there is. I guess we could try to get better about >>>>>>>>>>>>>>>>>>>> tagging issues when >>>>>>>>>>>>>>>>>>>> we create them? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> However, at least one issue is by someone outside the >>>>>>>>>>>>>>>>>>>> core Pulp team and I am not sure community members will >>>>>>>>>>>>>>>>>>>> know to tag their >>>>>>>>>>>>>>>>>>>> issues w/ Pulp 3 tag. Are there any other alternatives to >>>>>>>>>>>>>>>>>>>> ensuring Pulp 3 >>>>>>>>>>>>>>>>>>>> issues get properly tagged? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> David >>>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Pulp-dev mailing list >>>>>>>>>>>> Pulp-dev@redhat.com >>>>>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>> Pulp-dev mailing list >>>>>>>>> Pulp-dev@redhat.com >>>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Pulp-dev mailing list >>>>>>>> Pulp-dev@redhat.com >>>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pulp-dev mailing list >>>>>>> Pulp-dev@redhat.com >>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> >>>>>> _______________________________________________ >>>>>> Pulp-dev mailing list >>>>>> Pulp-dev@redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>> >>>>> _______________________________________________ >>>>> Pulp-dev mailing list >>>>> Pulp-dev@redhat.com >>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>> >>>> _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
