You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@livy.apache.org by larry mccay <lm...@apache.org> on 2022/11/12 18:24:58 UTC
JIRA Fix Version as Target Version for 0.8.0 and beyond
All -
I am trying to scope the JIRAs to target for the first release with the
revived community and planned to use the Target Version/s field to indicate
the intended release. However, we don't have that field available.
I propose that we use Fix Version/s to indicate both the intended release
version and ultimately the release that contains the patch.
As such, I will move the majority of open JIRAs to 0.9.0. This will result
in a lot of JIRA related emails.
As PRs get rebased and worked in the meantime, let's pull them back into
0.8.0. Also, if you would like to discuss specific JIRAs to remain in
0.8.0, feel free to do so on the JIRA and/or respond to this email.
If you have any concerns with the approach above, we can come up with
something else. This is essentially what we do on the Knox project and it
works fine.
thanks,
--larry
Re: JIRA Fix Version as Target Version for 0.8.0 and beyond
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Larry,
Thanks for the update. I will do a pass as well.
Regards
JB
On Sat, Nov 12, 2022 at 11:01 PM larry mccay <lm...@apache.org> wrote:
>
> Here is the list of JIRAs for 0.8.0 as of now
> https://issues.apache.org/jira/browse/LIVY-795?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.8.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> and here is the list of those that I moved to 0.9.0
> https://issues.apache.org/jira/browse/LIVY-686?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.9.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> We will add more to 0.8.0 for dependency upgrades and the like and pull
> some back in as folks have cycles for their patches.
>
> The second will need more of a deep dive to move some to backlog and close
> others as Won't Fix, etc.
>
>
> On Sat, Nov 12, 2022 at 1:49 PM larry mccay <lm...@apache.org> wrote:
>
> > I just did a bulk update for all open JIRA with an EMPTY Fix Version/s and
> > set them to 0.9.0.
> > I turned off email notification to avoid 340+ emails.
> >
> > Please note that there are likely JIRAs that have now been set to 0.9.0
> > and therefore out of the next release of 0.8.0 that you may be planning to
> > work on in the coming days.
> > Also, there may be some that may have already been merged in recent days
> > but the JIRA not updated and therefore inappropriately designated as 0.9.0
> > target.
> > I tried to look for the latter but have likely missed a few.
> >
> > If you are aware of either of the above class of JIRAs mislabeled as 0.9.0
> > please do change the Fix Version/s to 0.8.0.
> >
> > Thanks!
> >
> > --larry
> >
> > On Sat, Nov 12, 2022 at 1:24 PM larry mccay <lm...@apache.org> wrote:
> >
> >> All -
> >>
> >> I am trying to scope the JIRAs to target for the first release with the
> >> revived community and planned to use the Target Version/s field to indicate
> >> the intended release. However, we don't have that field available.
> >>
> >> I propose that we use Fix Version/s to indicate both the intended release
> >> version and ultimately the release that contains the patch.
> >>
> >> As such, I will move the majority of open JIRAs to 0.9.0. This will
> >> result in a lot of JIRA related emails.
> >>
> >> As PRs get rebased and worked in the meantime, let's pull them back into
> >> 0.8.0. Also, if you would like to discuss specific JIRAs to remain in
> >> 0.8.0, feel free to do so on the JIRA and/or respond to this email.
> >>
> >> If you have any concerns with the approach above, we can come up with
> >> something else. This is essentially what we do on the Knox project and it
> >> works fine.
> >>
> >> thanks,
> >>
> >> --larry
> >>
> >
Re: JIRA Fix Version as Target Version for 0.8.0 and beyond
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Larry,
Thanks for the update. I will do a pass as well.
Regards
JB
On Sat, Nov 12, 2022 at 11:01 PM larry mccay <lm...@apache.org> wrote:
>
> Here is the list of JIRAs for 0.8.0 as of now
> https://issues.apache.org/jira/browse/LIVY-795?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.8.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> and here is the list of those that I moved to 0.9.0
> https://issues.apache.org/jira/browse/LIVY-686?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.9.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> We will add more to 0.8.0 for dependency upgrades and the like and pull
> some back in as folks have cycles for their patches.
>
> The second will need more of a deep dive to move some to backlog and close
> others as Won't Fix, etc.
>
>
> On Sat, Nov 12, 2022 at 1:49 PM larry mccay <lm...@apache.org> wrote:
>
> > I just did a bulk update for all open JIRA with an EMPTY Fix Version/s and
> > set them to 0.9.0.
> > I turned off email notification to avoid 340+ emails.
> >
> > Please note that there are likely JIRAs that have now been set to 0.9.0
> > and therefore out of the next release of 0.8.0 that you may be planning to
> > work on in the coming days.
> > Also, there may be some that may have already been merged in recent days
> > but the JIRA not updated and therefore inappropriately designated as 0.9.0
> > target.
> > I tried to look for the latter but have likely missed a few.
> >
> > If you are aware of either of the above class of JIRAs mislabeled as 0.9.0
> > please do change the Fix Version/s to 0.8.0.
> >
> > Thanks!
> >
> > --larry
> >
> > On Sat, Nov 12, 2022 at 1:24 PM larry mccay <lm...@apache.org> wrote:
> >
> >> All -
> >>
> >> I am trying to scope the JIRAs to target for the first release with the
> >> revived community and planned to use the Target Version/s field to indicate
> >> the intended release. However, we don't have that field available.
> >>
> >> I propose that we use Fix Version/s to indicate both the intended release
> >> version and ultimately the release that contains the patch.
> >>
> >> As such, I will move the majority of open JIRAs to 0.9.0. This will
> >> result in a lot of JIRA related emails.
> >>
> >> As PRs get rebased and worked in the meantime, let's pull them back into
> >> 0.8.0. Also, if you would like to discuss specific JIRAs to remain in
> >> 0.8.0, feel free to do so on the JIRA and/or respond to this email.
> >>
> >> If you have any concerns with the approach above, we can come up with
> >> something else. This is essentially what we do on the Knox project and it
> >> works fine.
> >>
> >> thanks,
> >>
> >> --larry
> >>
> >
Re: JIRA Fix Version as Target Version for 0.8.0 and beyond
Posted by larry mccay <lm...@apache.org>.
Here is the list of JIRAs for 0.8.0 as of now
https://issues.apache.org/jira/browse/LIVY-795?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.8.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
and here is the list of those that I moved to 0.9.0
https://issues.apache.org/jira/browse/LIVY-686?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.9.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
We will add more to 0.8.0 for dependency upgrades and the like and pull
some back in as folks have cycles for their patches.
The second will need more of a deep dive to move some to backlog and close
others as Won't Fix, etc.
On Sat, Nov 12, 2022 at 1:49 PM larry mccay <lm...@apache.org> wrote:
> I just did a bulk update for all open JIRA with an EMPTY Fix Version/s and
> set them to 0.9.0.
> I turned off email notification to avoid 340+ emails.
>
> Please note that there are likely JIRAs that have now been set to 0.9.0
> and therefore out of the next release of 0.8.0 that you may be planning to
> work on in the coming days.
> Also, there may be some that may have already been merged in recent days
> but the JIRA not updated and therefore inappropriately designated as 0.9.0
> target.
> I tried to look for the latter but have likely missed a few.
>
> If you are aware of either of the above class of JIRAs mislabeled as 0.9.0
> please do change the Fix Version/s to 0.8.0.
>
> Thanks!
>
> --larry
>
> On Sat, Nov 12, 2022 at 1:24 PM larry mccay <lm...@apache.org> wrote:
>
>> All -
>>
>> I am trying to scope the JIRAs to target for the first release with the
>> revived community and planned to use the Target Version/s field to indicate
>> the intended release. However, we don't have that field available.
>>
>> I propose that we use Fix Version/s to indicate both the intended release
>> version and ultimately the release that contains the patch.
>>
>> As such, I will move the majority of open JIRAs to 0.9.0. This will
>> result in a lot of JIRA related emails.
>>
>> As PRs get rebased and worked in the meantime, let's pull them back into
>> 0.8.0. Also, if you would like to discuss specific JIRAs to remain in
>> 0.8.0, feel free to do so on the JIRA and/or respond to this email.
>>
>> If you have any concerns with the approach above, we can come up with
>> something else. This is essentially what we do on the Knox project and it
>> works fine.
>>
>> thanks,
>>
>> --larry
>>
>
Re: JIRA Fix Version as Target Version for 0.8.0 and beyond
Posted by larry mccay <lm...@apache.org>.
Here is the list of JIRAs for 0.8.0 as of now
https://issues.apache.org/jira/browse/LIVY-795?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.8.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
and here is the list of those that I moved to 0.9.0
https://issues.apache.org/jira/browse/LIVY-686?jql=project%20%3D%20LIVY%20AND%20fixVersion%20in%20(0.9.0)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
We will add more to 0.8.0 for dependency upgrades and the like and pull
some back in as folks have cycles for their patches.
The second will need more of a deep dive to move some to backlog and close
others as Won't Fix, etc.
On Sat, Nov 12, 2022 at 1:49 PM larry mccay <lm...@apache.org> wrote:
> I just did a bulk update for all open JIRA with an EMPTY Fix Version/s and
> set them to 0.9.0.
> I turned off email notification to avoid 340+ emails.
>
> Please note that there are likely JIRAs that have now been set to 0.9.0
> and therefore out of the next release of 0.8.0 that you may be planning to
> work on in the coming days.
> Also, there may be some that may have already been merged in recent days
> but the JIRA not updated and therefore inappropriately designated as 0.9.0
> target.
> I tried to look for the latter but have likely missed a few.
>
> If you are aware of either of the above class of JIRAs mislabeled as 0.9.0
> please do change the Fix Version/s to 0.8.0.
>
> Thanks!
>
> --larry
>
> On Sat, Nov 12, 2022 at 1:24 PM larry mccay <lm...@apache.org> wrote:
>
>> All -
>>
>> I am trying to scope the JIRAs to target for the first release with the
>> revived community and planned to use the Target Version/s field to indicate
>> the intended release. However, we don't have that field available.
>>
>> I propose that we use Fix Version/s to indicate both the intended release
>> version and ultimately the release that contains the patch.
>>
>> As such, I will move the majority of open JIRAs to 0.9.0. This will
>> result in a lot of JIRA related emails.
>>
>> As PRs get rebased and worked in the meantime, let's pull them back into
>> 0.8.0. Also, if you would like to discuss specific JIRAs to remain in
>> 0.8.0, feel free to do so on the JIRA and/or respond to this email.
>>
>> If you have any concerns with the approach above, we can come up with
>> something else. This is essentially what we do on the Knox project and it
>> works fine.
>>
>> thanks,
>>
>> --larry
>>
>
Re: JIRA Fix Version as Target Version for 0.8.0 and beyond
Posted by larry mccay <lm...@apache.org>.
I just did a bulk update for all open JIRA with an EMPTY Fix Version/s and
set them to 0.9.0.
I turned off email notification to avoid 340+ emails.
Please note that there are likely JIRAs that have now been set to 0.9.0 and
therefore out of the next release of 0.8.0 that you may be planning to work
on in the coming days.
Also, there may be some that may have already been merged in recent days
but the JIRA not updated and therefore inappropriately designated as 0.9.0
target.
I tried to look for the latter but have likely missed a few.
If you are aware of either of the above class of JIRAs mislabeled as 0.9.0
please do change the Fix Version/s to 0.8.0.
Thanks!
--larry
On Sat, Nov 12, 2022 at 1:24 PM larry mccay <lm...@apache.org> wrote:
> All -
>
> I am trying to scope the JIRAs to target for the first release with the
> revived community and planned to use the Target Version/s field to indicate
> the intended release. However, we don't have that field available.
>
> I propose that we use Fix Version/s to indicate both the intended release
> version and ultimately the release that contains the patch.
>
> As such, I will move the majority of open JIRAs to 0.9.0. This will result
> in a lot of JIRA related emails.
>
> As PRs get rebased and worked in the meantime, let's pull them back into
> 0.8.0. Also, if you would like to discuss specific JIRAs to remain in
> 0.8.0, feel free to do so on the JIRA and/or respond to this email.
>
> If you have any concerns with the approach above, we can come up with
> something else. This is essentially what we do on the Knox project and it
> works fine.
>
> thanks,
>
> --larry
>
Re: JIRA Fix Version as Target Version for 0.8.0 and beyond
Posted by larry mccay <lm...@apache.org>.
I just did a bulk update for all open JIRA with an EMPTY Fix Version/s and
set them to 0.9.0.
I turned off email notification to avoid 340+ emails.
Please note that there are likely JIRAs that have now been set to 0.9.0 and
therefore out of the next release of 0.8.0 that you may be planning to work
on in the coming days.
Also, there may be some that may have already been merged in recent days
but the JIRA not updated and therefore inappropriately designated as 0.9.0
target.
I tried to look for the latter but have likely missed a few.
If you are aware of either of the above class of JIRAs mislabeled as 0.9.0
please do change the Fix Version/s to 0.8.0.
Thanks!
--larry
On Sat, Nov 12, 2022 at 1:24 PM larry mccay <lm...@apache.org> wrote:
> All -
>
> I am trying to scope the JIRAs to target for the first release with the
> revived community and planned to use the Target Version/s field to indicate
> the intended release. However, we don't have that field available.
>
> I propose that we use Fix Version/s to indicate both the intended release
> version and ultimately the release that contains the patch.
>
> As such, I will move the majority of open JIRAs to 0.9.0. This will result
> in a lot of JIRA related emails.
>
> As PRs get rebased and worked in the meantime, let's pull them back into
> 0.8.0. Also, if you would like to discuss specific JIRAs to remain in
> 0.8.0, feel free to do so on the JIRA and/or respond to this email.
>
> If you have any concerns with the approach above, we can come up with
> something else. This is essentially what we do on the Knox project and it
> works fine.
>
> thanks,
>
> --larry
>