Yes, I had used "git merge --no-ff" while merging ATSv2 to trunk.
Maintaining history I believe can be useful as it can make reverts
easier if at all required.
And can be an easy reference point to look at who had contributed what
without having to go back to the branch.
Regards,
Varun Saxena.
O
Thanks Sangjin for the link to the previous discussions on this! I think
that helps answer Steve's questions.
As decided on that thread [1], YARN-5355 as a feature branch was merged to
trunk via "git merge --no-ff" .
Although trunk already had TSv2 code (alpha1) prior to this merge, we chose
to d
The "git" way of doing things would be to rebase the feature branch on
master (trunk) and then commit the patch stack.
Squashing the entire feature into a 10 MB megapatch is the "svn" way of
doing things.
The svn workflow evolved because merging feature branches back to trunk
was really painful i
I recall this discussion about a couple of years ago:
https://lists.apache.org/thread.html/43cd65c6b6c3c0e8ac2b3c76afd9eff1f78b177fabe9c4a96d9b3d0b@1440189889@%3Ccommon-dev.hadoop.apache.org%3E
On Wed, Aug 30, 2017 at 2:32 PM, Steve Loughran
wrote:
> I'd have assumed it would have gone in as one
I'd have assumed it would have gone in as one single patch, rather than a full
history. I don't see why the trunk needs all the evolutionary history of a
build.
What should our policy/process be here?
I do currently plan to merge the s3guard in as one single squashed patch; just
getting HADOOP
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/508/
[Aug 29, 2017 11:21:14 AM] (sunilg) YARN-6386. Show decommissioning nodes in
new YARN UI. Contributed by
[Aug 29, 2017 11:36:22 AM] (aajisaka) HADOOP-14671. Upgrade to Apache Yetus
0.5.0.
[Aug 29, 2017 2:5
[
https://issues.apache.org/jira/browse/HADOOP-14671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reopened HADOOP-14671:
> Upgrade to Apache Yetus 0.5.0
> -
>
> Key: HADOO
Ernani Pereira de Mattos Junior created HADOOP-14821:
Summary: Executing the command 'hdfs
-Dhadoop.security.credential.provider.path=file1.jceks,file2.jceks' fails;
Key: HADOOP-14821
URL: http
[
https://issues.apache.org/jira/browse/HADOOP-14221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-14221.
-
Resolution: Works for Me
> Add s3guardtool dump command
>
>
Sivaguru Sankaridurg created HADOOP-14820:
-
Summary: Fix for HDFS semantics parity for mkdirs -p
Key: HADOOP-14820
URL: https://issues.apache.org/jira/browse/HADOOP-14820
Project: Hadoop Commo
Lukas Waldmann created HADOOP-14819:
---
Summary: Update commons-net to 3.6
Key: HADOOP-14819
URL: https://issues.apache.org/jira/browse/HADOOP-14819
Project: Hadoop Common
Issue Type: Sub-tas
[
https://issues.apache.org/jira/browse/HADOOP-14177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenxin He resolved HADOOP-14177.
Resolution: Workaround
> hadoop-build fails to handle non-english UTF-8 characters
>
Thanks Brahma for comment on this thread. To be clear, I always update branch
version just before RC kicking off.
For 2.8.2 release, I don't have plan to involve big top or other third-party
test tools. As always, we will rely on test/verify efforts from community
especially from large deployed
Wenxin He created HADOOP-14818:
--
Summary: Can not show help message of
namenode/datanode/nodemanager when process started.
Key: HADOOP-14818
URL: https://issues.apache.org/jira/browse/HADOOP-14818
Projec
14 matches
Mail list logo
