incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Trivial Update of "August2014" by SteveLoughran
Date Tue, 05 Aug 2014 19:59:02 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "August2014" page has been changed by SteveLoughran:
https://wiki.apache.org/incubator/August2014?action=diff&rev1=23&rev2=24

Comment:
rm a duplicate word from slider report

  
  How has the community developed since the last report?
  
- We're getting some independent users/developers on our list, including some initial minor
contributions and some bug reports. As an example, we have some contributed some logos ...
which is now going to trigger a competition/vote for a slider logo.
+ We're getting some independent users/developers on our list, including some initial minor
contributions and some bug reports. As an example, we have some contributed logos ... which
is now going to trigger a competition/vote for a slider logo.
  
  The main external developer adoption is not in actual contributions for the core slider
engine, but from a few people writing slider application-packages to deploy their own applications.
This is a good first step -we have to work with them to get them through this process, note
and address issues they have -as well as encouraging them to contribute a bit themselves.
There's a tradeoff there: we don't want to dismiss all issues with "file a patch with the
JIRA" -maybe there's an intermediate step of "let's work on this, can you take this branch
and verify it works for you?"
  
@@ -885, +885 @@

  
  The switch to 2.6 will mean that this code would be developer only, as it would only work
against non-production Hadoop clusters. Yet we need this for the forthcoming features: the
Credential provider, service registry, Yarn node labeling and other features we need to integrate
with.
  
- That's a fairly exclusionary move for potential users: the current plan is to make a release
in sync with Hadoop 2.5, which will be the last Hadoop 2.4/2.5 compatible version. Yet it
not only gives us those new features, it helps tune those features and find bugs in their
implementation. As an example, one fix in Hadoop 2.4 is related to an Application Master failure
and restart problem which we'd found, a problem which, if we'd switched to Hadoop 2.4-SNAPSHOT
earlier,
+ That's a fairly exclusionary move for potential users: the current plan is to make a release
in sync with Hadoop 2.5, which will be the last Hadoop 2.4/2.5 compatible version. Yet it
not only gives us those new features, it helps tune those features and find bugs in their
implementation. As an example, one fix in Hadoop 2.4 is related to an Application Master failure
and restart problem which we'd found, a problem which, if we'd switched to Hadoop 2.4-SNAPSHOT
earlier, would have been found and fixed in the 2.4 release.
- would have been found and fixed in the 2.4 release.
  
  Date of last release:
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message