Skip to content

Enable GitHub Issues #102

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

Merged
merged 1 commit into from
Feb 23, 2025
Merged

Conversation

slawekjaranowski
Copy link
Member

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MINSTALL-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MINSTALL-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@slawekjaranowski slawekjaranowski added the enhancement New feature or request label Feb 4, 2025
Copy link
Contributor

@Bukama Bukama left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Compared with our PRs like this. Only difference is that in some (for exmaple resources) a small PR_automation.yml was also added to label things. But I think it's not a must-have.

@slawekjaranowski
Copy link
Member Author

Compared with our PRs like this. Only difference is that in some (for exmaple resources) a small PR_automation.yml was also added to label things. But I think it's not a must-have.

added early #100, #101

@hboutemy
Copy link
Member

hboutemy commented Feb 5, 2025

we already have many Jira to GH Issues migration started https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching
can we share progress, learnings, remaining TODO before planning addition of new projects to the list, please?

@slawekjaranowski
Copy link
Member Author

we already have many Jira to GH Issues migration started https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching can we share progress, learnings, remaining TODO before planning addition of new projects to the list, please?

More of switched project is our internal, not widely used by external users.
I will see how users (and we as maintainers) will work with it.

on mentioned wiki - we have a progress, steps, used tools ...

I'm going to release projects with GitHub issues to see what we need updated in release procedure

@slawekjaranowski slawekjaranowski mentioned this pull request Feb 23, 2025
8 tasks
@slawekjaranowski slawekjaranowski merged commit c9a2d28 into apache:master Feb 23, 2025
8 checks passed
@slawekjaranowski slawekjaranowski deleted the gh-issues branch February 23, 2025 15:54
@github-actions github-actions bot added this to the 4.0.0-beta-2 milestone Feb 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants