MIGRATION: Update the documentation to include the new GitHub issue workflow #14822
Assignees
Comments
|
Anyone can now self-assign issues by commenting "take": #14785 |
This was referenced Dec 6, 2022
AlenkaF
changed the title
This was referenced 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 <[email protected]> Co-authored-by: Alenka Frim <[email protected]> Co-authored-by: Joris Van den Bossche <[email protected]> Co-authored-by: Nic Crane <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
This was referenced Dec 8, 2022
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 <[email protected]> Co-authored-by: Alenka Frim <[email protected]> Co-authored-by: Joris Van den Bossche <[email protected]> Co-authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
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 <[email protected]> Co-authored-by: Alenka Frim <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
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 <[email protected]> Co-authored-by: Alenka Frim <[email protected]> Co-authored-by: Joris Van den Bossche <[email protected]> Co-authored-by: Raúl Cumplido <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
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 <[email protected]> Co-authored-by: Alenka Frim <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Joris Van den Bossche <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
Tracked here: https://issues.apache.org/jira/browse/ARROW-18363
ARROW-18363: [Docs] Include warning when viewing old docs (redirecting to stable/dev docs) arrow-site#275
ARROW-18363: [Docs] Include warning when viewing old docs (redirecting to stable/dev docs) #14839
Component(s)
Documentation
The text was updated successfully, but these errors were encountered: