Using the bulk update feature of JIRA I did the following operations based on some JQL filters.
Remove the 4.0.0 tag from the following: * project = hive and (status = Resolved or status = closed) and (fixVersion = 4.0.0-alpha-1 or fixVersion = 4.0.0-alpha-2) Clear fixVersion from the following leaving also an appropriate comment: * project = hive and status in (Open, "In Progress","In Review" , "Patch Available") and fixVersion is not EMPTY Please check the JIRA guidelines in [1] to find out more about the reasoning behind this change. It appears that there is a JIRA bug [2] when handling archived versions so you may notice that a few tickets still have the version set. Change fixVersion from 4.0.0 to 4.0.0-alpha-2 for remaining resolved tickets. * project = hive and status = resolved and fixVersion = 4.0.0 After all these actions there are no tickets with fixVersion = 4.0.0 * project = hive and fixVersion = 4.0.0 If someone plans/wants to take additional actions please leave a message in this thread. Best, Stamatis [1] https://cwiki.apache.org/confluence/display/Hive/HowToContribute [2] https://jira.atlassian.com/browse/JRASERVER-6419 On Fri, Oct 21, 2022 at 8:49 AM Ayush Saxena <ayush...@gmail.com> wrote: > Correction: Marking as released for alpha2 and deleting and recreating 4.0 > > > On 21-Oct-2022, at 9:51 AM, Ayush Saxena <ayush...@gmail.com> wrote: > > > Thanx Stamatis for volunteering. I think we should delete the > 4.0.0-alpha-2 version from the Jira as well to prevent people from > carelessly using that. > > There is an option here[1] to delete a version, can give a try like if > just deleting the 4.0.0 also from this list helps or not. > > [1] > https://issues.apache.org/jira/plugins/servlet/project-config/HIVE/administer-versions?status=unreleased > > -Ayush > > On Thu, 20 Oct 2022 at 15:51, Stamatis Zampetakis <zabe...@gmail.com> > wrote: > >> No script at all, I am just going to use the "Bulk Update" feature in >> JIRA. >> >> I will wait 24h in case there are objections and then move forward with >> the >> update. >> >> Best, >> Stamatis >> >> On Thu, Oct 20, 2022 at 12:12 PM Denys Kuzmenko >> <dkuzme...@cloudera.com.invalid> wrote: >> >> > Hi Stamatis, >> > >> > If you have an automatic script for that please run it. >> > >> > Note, I saw tickets with `fixVersion = 4.0.0 and fixVersion = >> > 4.0.0-alpha-2` in resolved state as well. >> > >> > >> https://issues.apache.org/jira/browse/HIVE-26643?jql=project%20%3D%20HIVE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20in%20(4.0.0)%20AND%20fixVersion%20in%20(4.0.0-alpha-2) >> > >> > Regards, >> > Denys >> > >> > On Thu, Oct 20, 2022 at 11:26 AM Stamatis Zampetakis <zabe...@gmail.com >> > >> > wrote: >> > >> > > Hi everyone, >> > > >> > > The past discussions around the version used in JIRA can be found in >> the >> > > following threads [1, 2]. >> > > >> > > As Ayush mentioned there are ~3K resolved tickets with Fix Version >> 4.0.0 >> > > but most of them are also tagged with 4.0.0-alpha1 [3]. >> > > >> > > I can easily remove the 4.0.0 tag from those tickets and keep only >> > > 4.0.0-alpha1 in Fix Version using bulk update; we can treat the >> > > remaining cases afterwards. >> > > Let me know if you want me to proceed with this change or if you have >> > > other suggestions. >> > > >> > > Best, >> > > Stamatis >> > > >> > > [1] https://lists.apache.org/thread/13w1s029b6gbych56zhzvj4x2vbv8k8q >> > > [2] https://the-asf.slack.com/archives/CFSSP9UPJ/p1646216936802329 >> > > [3] project = hive and status = resolved and fixVersion = 4.0.0 and >> > > fixVersion = 4.0.0-alpha-1 >> > > >> > > On Thu, Oct 20, 2022 at 6:53 AM Ayush Saxena <ayush...@gmail.com> >> wrote: >> > > >> > > > Hi Denys, >> > > > Flaging the version stuff here what we discussed offline. >> > > > >> > > > The version 4.0.0 was used prior the decision to rename it >> 4.0.0-alpha1 >> > > > was taken, but the rename was not done on the Jira. >> > > > >> > > > It still shows around 3K tickets resolved on version 4.0.0, which >> got >> > > > released already as part of the last 4.0.0-alpha1 release[1] >> > > > >> > > > We should rename it in the Jira to avoid issues with building >> Release >> > > > Notes for our next 4.0.0 release >> > > > >> > > > A simple INFRA ticket or anyone with Hive Jira Admin rights should >> be >> > > able >> > > > to do so. >> > > > >> > > > [1] >> > > > >> > > >> > >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%204.0.0 >> > > > >> > > > -Ayush >> > > > >> > > > >> > > > > On 19-Oct-2022, at 9:09 PM, Denys Kuzmenko < >> dkuzme...@cloudera.com >> > > .invalid> >> > > > wrote: >> > > > > >> > > > > Hi Team, >> > > > > >> > > > > Branching for Hive *4.0.0-alpha-2* was done today: >> > > > > https://github.com/apache/hive/tree/branch-4.0.0-alpha-2 >> > > > > >> > > > > The next development version is *4.0.0-SNAPSHOT* >> > > > > >> > > > > *alpha-2 *branch would be open for commits until Monday. If you >> would >> > > > like >> > > > > to include something major in it, but need more time, please let >> me >> > > know. >> > > > > >> > > > > Best regards, >> > > > > Denys >> > > > >> > > >> > >> >
