There is no API but it might help users if the the 'fluo-yarn' command and fluo-yarn.properties file followed semver.
On Mon, Jul 17, 2017 at 5:01 PM Keith Turner <[email protected]> wrote: > On Mon, Jul 17, 2017 at 4:55 PM, Mike Walch <[email protected]> wrote: > > I am not 100% sure about the versioning scheme but I don't think it > should > > match Fluo. The version is at 0.8.0 right now. I would like to make it > > 1.0.0 for first release and have the scripts and configuration files > follow > > semver. > > I like ver 1.0.0 for the first release. For semver, what will you > define as the API? > > > > > > On Mon, Jul 17, 2017 at 4:48 PM Christopher <[email protected]> wrote: > > > >> Ah, I see. Seems like a good idea. Out of curiosity, what kind of > >> versioning scheme did you have in mind? > >> > >> On Mon, Jul 17, 2017 at 4:38 PM Mike Walch <[email protected]> wrote: > >> > >> > Yes. Fluo-yarn will be on a different release schedule. A new > release > >> of > >> > Fluo should in most cases not require a new release of fluo-yarn. New > >> > releases of fluo-yarn will most likely be necessary to upgrade Apache > >> Twill > >> > to support newer releases of Hadoop YARN. > >> > > >> > On Mon, Jul 17, 2017 at 4:26 PM Christopher <[email protected]> > wrote: > >> > > >> > > Is the idea to have fluo-yarn on a different release cycle? > >> > > > >> > > > >> > > On Mon, Jul 17, 2017 at 3:52 PM Mike Walch <[email protected]> > wrote: > >> > > > >> > > > I would like to create new repo (called 'fluo-yarn') using Gitbox > to > >> > hold > >> > > > code for launching Fluo applications in YARN. This is related to > my > >> > > recent > >> > > > pull request [1]. Does anyone have any objections to this? > >> > > > > >> > > > [1]: https://github.com/apache/incubator-fluo/pull/883 > >> > > > > >> > > > >> > > >> >
