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 "ApexProposal" by AmolKekre
Date Wed, 12 Aug 2015 01:07:35 GMT
Dear Wiki user,

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

The "ApexProposal" page has been changed by AmolKekre:
https://wiki.apache.org/incubator/ApexProposal?action=diff&rev1=34&rev2=35

Comment:
Added apex-

     * JIRA Project Malhar (APEX-MALHAR)
  
  === Other Resources ===
-    * Means of setting up regular builds for Apex on builds.apache.org
+    * Means of setting up regular builds for apex-core on builds.apache.org
-    * Means of setting up regular builds for Malhar on builds.apache.org
+    * Means of setting up regular builds for apex-malhar on builds.apache.org
  
  === Rationale for Malhar and Apex having separate git and jira ===
  We managed Malhar and Apex as two repos and two jiras on purpose. Both code bases are released
under Apache 2.0 and are proposed for incubation. In terms of our vision to enable innovation
around a native YARN data-in-motion that unifies stream processing as well as batch processing
Malhar and Apex go hand in hand. Apex has base API that consists of java api (functional),
and attributes (operability). Malhar is a manifestation of this api, but from user perspective,
Malhar is itself an API to leverage business logic. Over past three years we have found that
the cadence of release and api changes in Malhar is much rapid than Apex and it was operationally
much easier to separate them into their own repos. Two repos will reflect clear separation
of engine (Apex) and operators/business logic (Malhar). It will allow or independent release
cycles (operator change independent of engine due to stable API). We however do not believe
in two levels of committers. We believe there should be one community that works across both
and innovates with ideas that Malhar and Apex combined provide the value proposition. We are
proposing that Apache incubation process help us to foster development of one community (mailing
list, committers), and a yet be ok with two repos. We are proposing that this be taken up
during incubation. Community will learn if this works. The decision on whether to split them
into two projects be taken after the learning curve during incubation.

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


Mime
View raw message