That is a nice change, very informational. Thanks.

Thanks
Edward

On Tue, Aug 2, 2016 at 7:49 PM, Michael Wu <[email protected]> wrote:

> Guys,
>
> I've updated README.md by adding a "Status" section that holds build
> status, latest release info. Taking this, PR #291
> <https://github.com/apache/incubator-eagle/pull/291> is opened towards
> develop branch, and PR #292
> <https://github.com/apache/incubator-eagle/pull/292> is opened towards
> master branch.
>
> Please help review them if you have the bandwidth. Thanks.
>
> Michael
>
> On Tue, Aug 2, 2016 at 2:58 PM, Michael Wu <[email protected]> wrote:
>
> > Agree with you, I think we do need to have a new section to clarify
> > different branch on different build status.
> >
> > On Tue, Aug 2, 2016 at 2:52 PM, Hao Chen <[email protected]> wrote:
> >
> >> I think at least we should add following informations on *master *branch
> >> READM
> >> as the entry page for a github project.
> >>
> >>    - Latest released version, link, say Latest Released Version is
> >>    [0.4.0](tags/0.4.0), [Build Passed]
> >>    - Latest development version, link, status, say Latest Development
> >>    Branch is [0.5.0-SNAPSHOT](branch/develop), [Build Passed]
> >>
> >> - Hao
> >>
> >> On Tue, Aug 2, 2016 at 1:30 PM, Michael Wu <[email protected]> wrote:
> >>
> >> > Hi guys,
> >> >
> >> > As once discussed, we may need to check build status on develop
> branch.
> >> > I've created a CI job that builds upon develop branch, triggered by
> any
> >> > check-in operation towards develop branch.
> >> >
> >> > CI job is here:
> https://builds.apache.org/job/incubator-eagle-develop/
> >> > Build Status icon url is: [![Build Status](
> >> >
> >> >
> >>
> https://builds.apache.org/buildStatus/icon?job=incubator-eagle-develop)](https://builds.apache.org/job/incubator-eagle-develop/
> >> > )
> >> > Jira ticket is: https://issues.apache.org/jira/browse/EAGLE-406
> >> >
> >> > We need to discuss what, how, where we'd like it to show up for eagle.
> >> Your
> >> > great thoughts will be appreciated.
> >> >
> >> > Michael
> >> >
> >>
> >
> >
>

Reply via email to