Sakthi created HBASE-23883:
--
Summary: HBase Precommit builds are broken due to some docker/java
issue.
Key: HBASE-23883
URL: https://issues.apache.org/jira/browse/HBASE-23883
Project: HBase
Issue
Mark Robert Miller created HBASE-23882:
--
Summary: Scale *MiniCluster config for the environment it runs in.
Key: HBASE-23882
URL: https://issues.apache.org/jira/browse/HBASE-23882
Project: HBase
Whatever we write up in our contributors section is ultimately a
recommended workflow, not fixed in stone. Until such time as we automate
entirely the contribution process, there will always be an element of human
discretion involved.
That said, I generally echo Andrew's concern re: alert
+1 to the idea, having one contribution workflow instead of two is 50% less
confusing (or 100% depending how you count it).
> applying a patch for local evaluation is more tedious than checking out a
PR branch.
Except it's not necessary to download and apply the patch to evaluate it,
we have
Heya, and happy Friday.
I would like to propose that we drop support for receiving contributions by
way of attaching a patch file to a Jira issue. From my perspective, in the
face of modern interfaces for PR-style review, this is an "archaic" form of
contribution that is "actively harmful" to
[
https://issues.apache.org/jira/browse/HBASE-23863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-23863.
---
Assignee: Michael Stack
Resolution: Fixed
Resolving. Pushed on branch-2 only. Not on
Bharath Vissapragada created HBASE-23881:
Summary: TestShadeSaslAuthenticationProvider failures
Key: HBASE-23881
URL: https://issues.apache.org/jira/browse/HBASE-23881
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-23880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-23880.
---
Resolution: Incomplete
Resolving as 'incomplete' after reverting patch pushed yesterday.
:waves:
welcome!
On 2/20/20 9:41 PM, Mark Miller wrote:
Hey all,
Just wanted to introduce myself since I've been getting pulled into the
world of HBase tests.
I've been working around hdfs and distributed systems for a long while now
and a ridiculously huge percentage of my time has been
>
> It could work of course but has downsides. Email explosion. How do I as
> committer know what order to apply them in? Confusion as random reviewers
> see some of the changes in some of the PRs but miss other changes in others.
>
Was not suggesting it to be the norm, but something to keep as an
I don’t think a PR per JIRA per backport is what we want. It could work of
course but has downsides. Email explosion. How do I as committer know what
order to apply them in? Confusion as random reviewers see some of the changes
in some of the PRs but miss other changes in others.
> On Feb 21,
[
https://issues.apache.org/jira/browse/HBASE-23561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-23561.
--
Resolution: Fixed
Merged into master. Thanks for the contribution,
>
> we retain all of the individual commits (one-to-one with Jira sub-tasks).
> Mechanically this means something like the following:
> (1) squash together all commits that correspond with a single Jira
> sub-task, making the history into one commit for one sub-task.
>
How about also add the
13 matches
Mail list logo
