Hey folks,
There's been a bit of off-list discussion about this, so I wanted to
clarify a few points about the development style for this branch,
since I think there was some confusion.
First, a little bit about the motivation for following something
closer to CTR rather than RTC on the branch:
I've created this branch "HDFS-1073" as discussed. In this branch there's a
new CHANGES.HDFS-1073.txt file -- please add entries into this file rather
than CHANGES.txt if you commit stuff to the branch. This will simplify our
merges later on, I think. We'll transfer the changes back into CHANGES.tx
+1 for creating a branch.
Agree with Jakob this should not mean less intensive reviewing.
--Konstantin
On Mon, Mar 28, 2011 at 4:39 PM, Jakob Homan wrote:
> Doing this work on a branch makes sense. +1.
>
> However, the patches that have been committed so far required
> extensive review and revi
Doing this work on a branch makes sense. +1.
However, the patches that have been committed so far required
extensive review and revision, and in one case, an addendum patch.
Additionally, the patches in related JIRAs such as HDFS-1557 and
HDFS-1572 have required multiple revisions and corrections
+1. I think this will be very helpful in moving the design forward quickly.
-dhruba
On Mon, Mar 28, 2011 at 1:14 PM, Todd Lipcon wrote:
> Hi all,
>
> I discussed this with a couple folks over the weekend who are involved in
> the project, but wanted to let the dev community at large know:
>
>
Hi all,
I discussed this with a couple folks over the weekend who are involved in
the project, but wanted to let the dev community at large know:
I'm planning on creating a new SVN branch for HDFS-1073 and its subtasks.
For those not aware, HDFS-1073 is a rethinking of how the NN, 2NN, and
Backup
