Let's not dismiss this quite so handily.
Sean, Jason, and Stack replied on HADOOP-11656 pointing out that while we
could make classpath isolation opt-in via configuration, what we really
want longer term is to have it on by default (or just always on). Stack in
particular points out the practical
In general +1 on 3.0.0. Its time. If we start now, it might make it out by
2016. If we start now, downstreamers can start aligning themselves to land
versions that suit at about the same time.
While two big items have been called out as possible incompatible changes,
and there is ongoing
Thanks for reviving this on email, Vinod. Newer folks like me might not be
aware of this JIRA/effort.
This would be wonderful to have so (1) we know the status of release
branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
Jonathan's or Matt's proposal for including branch name
Hi all,
I'd like us to revive the effort at
https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit builds
being able to work with branches. Having the Jenkins verify patches on branches
is very useful even if there may be relaxed review oversight on the said-branch.
Unless there
+1
If we can make things look like HBase support for precommit testing on
branches (HBASE-12944), that would make it easier for new and occasional
contributors who might end up working in other ecosystem projects. AFAICT,
Jonathan's proposal for branch names in patch names does this.
On Wed,
Might I have some comments for this, just providing my thought. Thanks.
If we start now, it might make it out by 2016. If we start now,
downstreamers can start aligning themselves to land versions that suit at
about the same time.
Not only for down streamers to align with the long term
Thanks Vinod for the hints.
I have updated the both patches aligning with latest codes, and added more unit
tests. The building results look reasonable. Thanks anyone that would give them
more review and I would update in timely manner.
Regards,
Kai
-Original Message-
From: Vinod
On Wed, Mar 4, 2015 at 10:46 AM, Stack st...@duboce.net wrote:
In general +1 on 3.0.0. Its time. If we start now, it might make it out by
2016. If we start now, downstreamers can start aligning themselves to land
versions that suit at about the same time.
While two big items have been called
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit testing against branch-2 as the default
too like that against trunk?
On 3/4/15, 1:47 PM, Sean Busbey bus...@cloudera.com wrote:
+1
If we can make things look like HBase support for precommit
One of the questions that keeps popping up is “what exactly is in trunk?”
As some may recall, I had done some experiments creating the change log based
upon JIRA. While the interest level appeared to be approaching zero, I kept
playing with it a bit and eventually also started playing with
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/122/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 10607 lines...]
11 matches
Mail list logo
