You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by Kyle Richardson <ky...@gmail.com> on 2016/12/05 18:48:48 UTC
Process for closing JIRAs
What's our current process for closing JIRAs once the github PR has been
merged? Are we setting it to Done with a particular fix version?
If a JIRA is a duplicate, are we marking it any particular way?
Thanks,
Kyle
Re: Process for closing JIRAs
Posted by Kyle Richardson <ky...@gmail.com>.
Awesome. Thanks, guys!
-Kyle
On Mon, Dec 5, 2016 at 3:59 PM, Casey Stella <ce...@gmail.com> wrote:
> Yeah, when committed, close it and make it Next + 1.
>
> On Mon, Dec 5, 2016 at 3:58 PM, Nick Allen <ni...@nickallen.org> wrote:
>
> > I saw just today that someone added a "Next + 1" version to the JIRA. I
> > started using that assuming that it was created to solve that problem.
> > Open to correction though.
> >
> > On Mon, Dec 5, 2016 at 3:47 PM, Michael Miklavcic <
> > michael.miklavcic@gmail.com> wrote:
> >
> > > To the first question, mark the Jira as DONE. I don't believe we can do
> > fix
> > > version until the community agrees on the next version increment, which
> > we
> > > normally won't know until we're getting close to cutting a release and
> > can
> > > make an assessment of it being major or minor.
> > >
> > > On Mon, Dec 5, 2016 at 11:48 AM, Kyle Richardson <
> > > kylerichardson2@gmail.com>
> > > wrote:
> > >
> > > > What's our current process for closing JIRAs once the github PR has
> > been
> > > > merged? Are we setting it to Done with a particular fix version?
> > > >
> > > > If a JIRA is a duplicate, are we marking it any particular way?
> > > >
> > > > Thanks,
> > > > Kyle
> > > >
> > >
> >
> >
> >
> > --
> > Nick Allen <ni...@nickallen.org>
> >
>
Re: Process for closing JIRAs
Posted by Casey Stella <ce...@gmail.com>.
Yeah, when committed, close it and make it Next + 1.
On Mon, Dec 5, 2016 at 3:58 PM, Nick Allen <ni...@nickallen.org> wrote:
> I saw just today that someone added a "Next + 1" version to the JIRA. I
> started using that assuming that it was created to solve that problem.
> Open to correction though.
>
> On Mon, Dec 5, 2016 at 3:47 PM, Michael Miklavcic <
> michael.miklavcic@gmail.com> wrote:
>
> > To the first question, mark the Jira as DONE. I don't believe we can do
> fix
> > version until the community agrees on the next version increment, which
> we
> > normally won't know until we're getting close to cutting a release and
> can
> > make an assessment of it being major or minor.
> >
> > On Mon, Dec 5, 2016 at 11:48 AM, Kyle Richardson <
> > kylerichardson2@gmail.com>
> > wrote:
> >
> > > What's our current process for closing JIRAs once the github PR has
> been
> > > merged? Are we setting it to Done with a particular fix version?
> > >
> > > If a JIRA is a duplicate, are we marking it any particular way?
> > >
> > > Thanks,
> > > Kyle
> > >
> >
>
>
>
> --
> Nick Allen <ni...@nickallen.org>
>
Re: Process for closing JIRAs
Posted by Nick Allen <ni...@nickallen.org>.
I saw just today that someone added a "Next + 1" version to the JIRA. I
started using that assuming that it was created to solve that problem.
Open to correction though.
On Mon, Dec 5, 2016 at 3:47 PM, Michael Miklavcic <
michael.miklavcic@gmail.com> wrote:
> To the first question, mark the Jira as DONE. I don't believe we can do fix
> version until the community agrees on the next version increment, which we
> normally won't know until we're getting close to cutting a release and can
> make an assessment of it being major or minor.
>
> On Mon, Dec 5, 2016 at 11:48 AM, Kyle Richardson <
> kylerichardson2@gmail.com>
> wrote:
>
> > What's our current process for closing JIRAs once the github PR has been
> > merged? Are we setting it to Done with a particular fix version?
> >
> > If a JIRA is a duplicate, are we marking it any particular way?
> >
> > Thanks,
> > Kyle
> >
>
--
Nick Allen <ni...@nickallen.org>
Re: Process for closing JIRAs
Posted by Michael Miklavcic <mi...@gmail.com>.
To the first question, mark the Jira as DONE. I don't believe we can do fix
version until the community agrees on the next version increment, which we
normally won't know until we're getting close to cutting a release and can
make an assessment of it being major or minor.
On Mon, Dec 5, 2016 at 11:48 AM, Kyle Richardson <ky...@gmail.com>
wrote:
> What's our current process for closing JIRAs once the github PR has been
> merged? Are we setting it to Done with a particular fix version?
>
> If a JIRA is a duplicate, are we marking it any particular way?
>
> Thanks,
> Kyle
>