Branch merges made it hard to access change history on subversion sometimes.
You can read the tale of woe here:
http://programmers.stackexchange.com/questions/206016/maintaining-svn-history-for-a-file-when-merge-is-done-from-the-dev-branch-to-tru
Excerpt:
"prior to Subversion 1.8. The files i
Allen Wittenauer created HADOOP-11723:
-
Summary: automate and markdownify changelog and release notes
Key: HADOOP-11723
URL: https://issues.apache.org/jira/browse/HADOOP-11723
Project: Hadoop Commo
+1 for automating the information contained in CHANGES.txt. There are some
changes which go in without JIRAs sometimes (CVEs eg.) . I like git log because
its the absolute source of truth (cryptographically secure, audited,
distributed, yadadada). We could always use git hooks to force a commit
I took the liberty of adding line breaks to Joep's mail.
Thanks for the great feedback Joep. The goal with 3.x is to maintain API
and wire compatibility with 2.x, which I think addresses most of your
concerns. A 2.x client running on JDK7 would then still be able to talk to
a 3.x server running on
Here are some of our thought on the discussions of the past few days with
respect to backwards compatibility.
In general at Twitter we're not necessarily against backwards incompatible
changes per se.
*It depends on the "Return on Pain". While it is hard to quantify the
returns in the a
Arun Suresh created HADOOP-11722:
Summary: Some Instances of Services using
ZKDelegationTokenSecretManager go when old token cannot be deleted
Key: HADOOP-11722
URL: https://issues.apache.org/jira/browse/HADOOP-11
[
https://issues.apache.org/jira/browse/HADOOP-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth resolved HADOOP-11638.
Resolution: Fixed
Fix Version/s: 2.7.0
I committed this to trunk, branch-2 and bran
Sean Busbey created HADOOP-11721:
Summary: switch jenkins patch tester to use git clean instead of
mvn clean
Key: HADOOP-11721
URL: https://issues.apache.org/jira/browse/HADOOP-11721
Project: Hadoop C
+1 for generating CHANGES.txt from JIRA and/or git as part of making a
release. Or just dropping it altogether. Keeping it under version
control creates lot of false conflicts whenever submitting a patch and
generally makes committing minor changes unpleasant.
Colin
On Sat, Mar 14, 2015 at 8:36
Akira AJISAKA created HADOOP-11720:
--
Summary: [JDK8] Fix javadoc errors in hadoop-streaming
Key: HADOOP-11720
URL: https://issues.apache.org/jira/browse/HADOOP-11720
Project: Hadoop Common
I
10 matches
Mail list logo