Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MIGRATION: Update the documentation to include the new GitHub issue workflow #14822

Closed
5 tasks done
Tracked by #14542
AlenkaF opened this issue Dec 2, 2022 · 1 comment
Closed
5 tasks done
Tracked by #14542

Comments

@AlenkaF
Copy link
Member

AlenkaF commented Dec 2, 2022

Describe the enhancement requested

As we are moving towards GitHub issues for Arrow issue reports, the documentation needs to be updated so that the contributors have a place to look if they need the information about the workflow we are/will be having.

The issue will be divided into multiple subtasks (parts of the documentation) so that the review process will be easier:

Component(s)

Documentation

@AlenkaF AlenkaF self-assigned this Dec 2, 2022
@assignUser
Copy link
Member

Anyone can now self-assign issues by commenting "take": #14785

@AlenkaF AlenkaF changed the title [Docs] Update the documentation to include the new GitHub issue workflow MIGRATION: Update the documentation to include the new GitHub issue workflow Dec 6, 2022
jorisvandenbossche added a commit that referenced this issue Dec 8, 2022
This PR is part of the work to update the documentation as we are moving from Jira issue tracker to GitHub issues:
#14822

cc @ thisisnic 

closes #14854

Lead-authored-by: Alenka Frim <frim.alenka@gmail.com>
Co-authored-by: Alenka Frim <AlenkaF@users.noreply.github.com>
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Co-authored-by: Nic Crane <thisisnic@gmail.com>
Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
jorisvandenbossche added a commit that referenced this issue Dec 22, 2022
…b) (#14889)

This PR is part of the work to update the documentation as we are moving from Jira issue tracker to GitHub issues:
#14822

Closes #14885
* Closes: #14885

Lead-authored-by: Alenka Frim <frim.alenka@gmail.com>
Co-authored-by: Alenka Frim <AlenkaF@users.noreply.github.com>
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
jorisvandenbossche pushed a commit that referenced this issue Dec 22, 2022
… -> GitHub) (#14919)

This PR is part of the work to update the documentation as we are moving from Jira issue tracker to GitHub issues:
#14822
* Closes: #14918

Lead-authored-by: Alenka Frim <frim.alenka@gmail.com>
Co-authored-by: Alenka Frim <AlenkaF@users.noreply.github.com>
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
EpsilonPrime pushed a commit to EpsilonPrime/arrow that referenced this issue Jan 5, 2023
… GitHub) (apache#14889)

This PR is part of the work to update the documentation as we are moving from Jira issue tracker to GitHub issues:
apache#14822

Closes apache#14885
* Closes: apache#14885

Lead-authored-by: Alenka Frim <frim.alenka@gmail.com>
Co-authored-by: Alenka Frim <AlenkaF@users.noreply.github.com>
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
EpsilonPrime pushed a commit to EpsilonPrime/arrow that referenced this issue Jan 5, 2023
… (Jira -> GitHub) (apache#14919)

This PR is part of the work to update the documentation as we are moving from Jira issue tracker to GitHub issues:
apache#14822
* Closes: apache#14918

Lead-authored-by: Alenka Frim <frim.alenka@gmail.com>
Co-authored-by: Alenka Frim <AlenkaF@users.noreply.github.com>
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
@AlenkaF AlenkaF closed this as completed Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants