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 wrote:
> Raul opened these issues to track required changes to the release scripts:
> * [Release][Archery] Update archery release cura
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 su
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
wrote:
> Thanks Rok for looking into this.
>
> I am ok migrating to GitHub but I want to mention that there are some
>
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
Thank you for working on this Rok 🙏
On Fri, 16 Dec 2022 at 01:21, Rok Mihevc 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 t
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
+1
On Fri, Nov 25, 2022 at 10:31 AM Alessandro Molina
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.
+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 ha
scritto:
> Hello,
>
> I wou
+1
On Thu, Nov 24, 2022 at 1:38 PM Alenka Frim
wrote:
> +1
>
> On Thu, 24 Nov 2022 at 17:44, Anja wrote:
>
> > +1
> >
> > On Thu, 24 Nov 2022 at 11:23, Rok Mihevc wrote:
> >
> > > +1
> > >
> > > I would propose to also add a note about using tags (e.g.
> [C++][Parquet]
> > > before the issue n
+1
On Thu, 24 Nov 2022 at 17:44, Anja wrote:
> +1
>
> On Thu, 24 Nov 2022 at 11:23, Rok Mihevc wrote:
>
> > +1
> >
> > I would propose to also add a note about using tags (e.g. [C++][Parquet]
> > before the issue name) when opening a new issue.
> >
> > Rok
> >
> > On Thu, Nov 24, 2022 at 5:03 P
+1
On Thu, 24 Nov 2022 at 11:23, Rok Mihevc wrote:
> +1
>
> I would propose to also add a note about using tags (e.g. [C++][Parquet]
> before the issue name) when opening a new issue.
>
> Rok
>
> On Thu, Nov 24, 2022 at 5:03 PM Nic wrote:
>
> > +1
> >
> > On Thu, 24 Nov 2022 at 15:57, Joris Van
+1
I would propose to also add a note about using tags (e.g. [C++][Parquet]
before the issue name) when opening a new issue.
Rok
On Thu, Nov 24, 2022 at 5:03 PM Nic wrote:
> +1
>
> On Thu, 24 Nov 2022 at 15:57, Joris Van den Bossche <
> jorisvandenboss...@gmail.com> wrote:
>
> > +1
> >
> > On
+1
On Thu, 24 Nov 2022 at 15:57, Joris Van den Bossche <
jorisvandenboss...@gmail.com> wrote:
> +1
>
> On Wed, 23 Nov 2022 at 22:37, Todd Farmer
> wrote:
> >
> > Hello,
> >
> > I would like to propose that issue reporting in ASF Jira for the Apache
> > Arrow project be disabled, and all users di
I would be a strong +1 for using GitHub for all new top-level issues. We
already have a title formatting requirement on JIRAs (e.g., [R] Some issue
description) and so I don't see any reason why labels could not be added in
retrospect even if they don't exist yet.
On Thu, Nov 24, 2022 at 7:30 AM J
+1
On Wed, 23 Nov 2022 at 22:37, Todd Farmer wrote:
>
> 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
> respons
On Thu, 24 Nov 2022 at 11:31, Antoine Pitrou wrote:
>
>
> Are all the required labels ready? I don't seem to see the components
> in https://github.com/apache/arrow/labels. Also, we should curate the
> existing labels and namespace all the remaining ones so that the
> categories can be easily unde
Are all the required labels ready? I don't seem to see the components
in https://github.com/apache/arrow/labels. Also, we should curate the
existing labels and namespace all the remaining ones so that the
categories can be easily understood.
Besides, it seems the component lists in the issue tem
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
reg
18 matches
Mail list logo
