-
Notifications
You must be signed in to change notification settings - Fork 36
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
[MPIR-454] Upgrade to Doxia 2.0.0 Milestone Stack #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asfgit
force-pushed
the
doxia-2.0.0
branch
4 times, most recently
from
December 3, 2022 22:02
a9bdd3a
to
a28d16b
Compare
asfgit
force-pushed
the
doxia-2.0.0
branch
3 times, most recently
from
February 11, 2023 22:07
60126b1
to
c99984b
Compare
asfgit
force-pushed
the
doxia-2.0.0
branch
3 times, most recently
from
March 20, 2023 20:26
c3618e0
to
2a507cc
Compare
asfgit
force-pushed
the
doxia-2.0.0
branch
2 times, most recently
from
June 5, 2023 19:16
455b27d
to
563c3b8
Compare
asfgit
force-pushed
the
doxia-2.0.0
branch
2 times, most recently
from
October 21, 2023 19:31
c61e13c
to
79f39d9
Compare
asfgit
force-pushed
the
doxia-2.0.0
branch
3 times, most recently
from
December 16, 2023 12:51
817650a
to
230348e
Compare
michael-o
changed the title
Prepare for Doxia 2.0.0
[MPIR-454] Upgrade to Doxia 2.0.0 Milestone Stack
Dec 25, 2023
asfgit
pushed a commit
that referenced
this pull request
Dec 25, 2023
asfgit
pushed a commit
that referenced
this pull request
May 20, 2024
asfgit
pushed a commit
that referenced
this pull request
May 29, 2024
asfgit
pushed a commit
that referenced
this pull request
Jun 2, 2024
asfgit
pushed a commit
that referenced
this pull request
Jun 2, 2024
asfgit
pushed a commit
that referenced
this pull request
Jun 2, 2024
michael-o
added a commit
that referenced
this pull request
Jun 14, 2024
asfgit
pushed a commit
that referenced
this pull request
Jun 23, 2024
asfgit
pushed a commit
that referenced
this pull request
Jun 23, 2024
asfgit
pushed a commit
that referenced
this pull request
Jul 11, 2024
asfgit
pushed a commit
that referenced
this pull request
Jul 20, 2024
asfgit
pushed a commit
that referenced
this pull request
Aug 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following this checklist to help us incorporate your
contribution quickly and easily:
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.
[MPIR-XXX] - Fixes bug in ApproximateQuantiles
,where you replace
MPIR-XXX
with the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verify
to make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
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.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.