New issue reporting on Jira has just been disabled.
Thank you all for participating and Todd for setting this up.

Rok

On Fri, Dec 16, 2022 at 5:02 PM Rok Mihevc <rok.mih...@gmail.com> wrote:

> Raul opened these issues to track required changes to the release scripts:
> * [Release][Archery] Update archery release curate to support GitHub
> issues [1]
> * [Release][Archery] Update archery release changelog to support GitHub
> issues [2]
> * [Release][Archery] Update archery release cherry-pick to support GitHub
> issues [3]
>
> We also had a chat on Zulip and Raul pointed out that it would make sense
> to do full refactoring of these scripts after Jira has been completely
> locked down as all of the Jira logic could be removed from these scripts at
> that point.
>
> [1] https://github.com/apache/arrow/issues/14997
> [2] https://github.com/apache/arrow/issues/14999
> [3] https://github.com/apache/arrow/issues/15002
>
> On Fri, Dec 16, 2022 at 3:31 PM Rok Mihevc <rok.mih...@gmail.com> wrote:
>
>> Thanks for bringing that point up Raul!
>> Would a good workaround be to open the required Jira issues now, before
>> we lock the Jira?
>>
>>
>> On Fri, Dec 16, 2022 at 1:42 PM Raúl Cumplido <raulcumpl...@gmail.com>
>> wrote:
>>
>>> Thanks Rok for looking into this.
>>>
>>> I am ok migrating to GitHub but I want to mention that there are some
>>> archery related commands like `archery release curate`, `archery release
>>> changelog` and more importantly `archery release cherry-pick` that must
>>> be
>>> updated in order to work with GitHub.
>>>
>>> For the release curate and changelog we could "easily" extract the GH
>>> issues parsing the commit titles but at the moment the cherry-pick
>>> command
>>> won't work. This is used to cherry pick the commits that have been tagged
>>> on JIRA with the corresponding version into the maintenance branch once
>>> the
>>> code freeze has been done. At the moment the cherry-pick command is only
>>> able to cherry pick commits that are tagged with the corresponding
>>> version
>>> on JIRA not on GitHub and are not already on the maintenance branch. If
>>> we
>>> fully migrate to GitHub before this is updated the Release Manager will
>>> have to take that into account on the release, cherry-picking commits
>>> from
>>> GH will have to be done manually. I am happy to work on updating those
>>> scripts, I already have them on my TODO list for next year, but I am
>>> probably not going to have time before the next release.
>>>
>>> I also think this is not a blocker for moving to GitHub but worth
>>> mentioning as it will require some extra effort until this is fixed.
>>>
>>>
>>> El vie, 16 dic 2022 a las 8:28, Alenka Frim (<ale...@voltrondata.com
>>> .invalid>)
>>> escribió:
>>>
>>> > Thank you for working on this Rok 🙏
>>> >
>>> > On Fri, 16 Dec 2022 at 01:21, Rok Mihevc <rok.mih...@gmail.com> wrote:
>>> >
>>> > > The vote is now 8 +1 votes, 1 +1 "when the merge scripts are ready"
>>> and 1
>>> > > -1 vote "until the labels are ready".
>>> > >
>>> > > Please correct me if I'm wrong, but I believe merge scripts and
>>> labels
>>> > are
>>> > > now ready. If that is the case we can tally this vote as 10 +1 votes
>>> and
>>> > > proceed with disabling ASF Jira issue reporting. I'll wait 24 hours
>>> if
>>> > > there are objections and then ask Infra to disable creating new
>>> issues.
>>> > >
>>> > > Rok
>>> > >
>>> > > On Mon, Nov 28, 2022 at 4:58 PM Matthew Topol
>>> > <m...@voltrondata.com.invalid
>>> > > >
>>> > > wrote:
>>> > >
>>> > > > +1
>>> > > >
>>> > > > On Fri, Nov 25, 2022 at 10:31 AM Alessandro Molina
>>> > > > <alessan...@voltrondata.com.invalid> wrote:
>>> > > >
>>> > > > > +1 as far as for "now" we actually mean "as soon as the necessary
>>> > > scripts
>>> > > > > have been ported to github"
>>> > > > >
>>> > > > > I mean, I doubt the plan is to disable jira before we can
>>> actually
>>> > ship
>>> > > > PRs
>>> > > > > from github issues and thus block development.
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > Il Mer 23 Nov 2022, 22:37 Todd Farmer
>>> <t...@voltrondata.com.invalid>
>>> > > ha
>>> > > > > scritto:
>>> > > > >
>>> > > > > > Hello,
>>> > > > > >
>>> > > > > > I would like to propose that issue reporting in ASF Jira for
>>> the
>>> > > Apache
>>> > > > > > Arrow project be disabled, and all users directed to use GitHub
>>> > > issues
>>> > > > > for
>>> > > > > > reporting going forward. GitHub issue reporting is now enabled
>>> [1]
>>> > in
>>> > > > > > response to a recent Infra policy change eliminating
>>> self-service
>>> > > user
>>> > > > > > registration for ASF Jira accounts. The Apache Arrow project
>>> has
>>> > > > already
>>> > > > > > voted in support of migrating issue tracking from ASF Jira to
>>> > GitHub
>>> > > > > issues
>>> > > > > > [2], and migration work is ongoing [3].
>>> > > > > >
>>> > > > > > Disabling ASF Jira issue reporting will move all such work to
>>> > GitHub
>>> > > > > > issues. I expect that usage of this new platform by all
>>> > participants
>>> > > -
>>> > > > > not
>>> > > > > > just new community members lacking ASF Jira accounts - will
>>> > expedite
>>> > > > > > further discovery and improvements to this platform.
>>> Furthermore,
>>> > > this
>>> > > > > will
>>> > > > > > prevent new users from being routed to a new, and potentially
>>> > > "lesser",
>>> > > > > > issue reporting experience.
>>> > > > > >
>>> > > > > > Please note that this proposal does NOT move work on existing
>>> ASF
>>> > > Jira
>>> > > > > > issues to GitHub - that work should continue in Jira until
>>> issues
>>> > are
>>> > > > > > migrated and the Jira system set to read-only. There will be a
>>> > > separate
>>> > > > > > discussion when that activity is ready.
>>> > > > > >
>>> > > > > > The vote will be open for at least 72 hours.
>>> > > > > >
>>> > > > > > [ ] +1 Disable issue reporting on ASF Jira for the Apache Arrow
>>> > > project
>>> > > > > > [ ] -1 Leave issue reporting enabled on ASF Jira for the Apache
>>> > Arrow
>>> > > > > > project because...
>>> > > > > >
>>> > > > > > [1] https://github.com/apache/arrow/issues/new/choose
>>> > > > > > [2]
>>> > https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb
>>> > > > > > [3]
>>> > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> https://docs.google.com/document/d/1UaSJs-oyuq8QvlUPoQ9GeiwP19LK5ZzF_5-HLfHDCIg/edit?usp=sharing
>>> > > > > >
>>> > > > > > Todd Farmer
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>

Reply via email to