Thank you for clearing that up :) On Thu, Nov 29, 2018 at 8:00 AM David Davis <davidda...@redhat.com> wrote:
> The Pulp RC depends on work outside of the pulp project (e.g. the Docker > and RPM betas). If Docker/RPM/etc use the tag to tag their own RC stories, > how do we track Docker/RPM/etc issues for the upcoming Pulp RC? One > solution would be to have plugins use milestones and reserve the Pulp 3 RC > Blocker tag for the upcoming Pulp 3 RC. > > David > > > On Thu, Nov 29, 2018 at 7:36 AM Brian Bouterse <bbout...@redhat.com> > wrote: > >> >> >> On Wed, Nov 28, 2018 at 10:16 AM Daniel Alley <dal...@redhat.com> wrote: >> >>> I am assuming that this can be used on a per-plugin basis, e.g. that >>> applying this tag to an RPM plugin will be assumed to mean the RPM plugin >>> RC as opposed to core? >>> >> That is how I think about it. >> >> >>> On Wed, Nov 28, 2018 at 9:45 AM David Davis <davidda...@redhat.com> >>> wrote: >>> >>>> Just wanted to make a quick announcement that there’s a new RC Blocker >>>> tag in redmine for issues that need to be completed by the RC release. >>>> Please use it on all issues that you know block the RC. >>>> >>>> Thank you. >>>> >>>> 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
