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 wrote:
> I think at least we should add following informations on *master *branch
> READM
> as the entry page for a github project.
>
>- La
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
[
https://issues.apache.org/jira/browse/EAGLE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403466#comment-15403466
]
ASF GitHub Bot commented on EAGLE-403:
--
Github user haoch closed the pull request at:
Github user haoch closed the pull request at:
https://github.com/apache/incubator-eagle/pull/289
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
[
https://issues.apache.org/jira/browse/EAGLE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403462#comment-15403462
]
ASF GitHub Bot commented on EAGLE-403:
--
GitHub user haoch opened a pull request:
GitHub user haoch opened a pull request:
https://github.com/apache/incubator-eagle/pull/289
EAGLE-403 Support to delete site resources with uuid
https://issues.apache.org/jira/browse/EAGLE-403
You can merge this pull request into a Git repository by running:
$ git pull https://
Looking good, guys. Thanks!
On Monday, August 1, 2016, Hao Chen wrote:
> The twitter account (https://twitter.com/TheApacheEagle) has been updated
> with http://eagle.incubator.apache.org/ now.
>
> Thanks
>
> - Hao
>
> On Mon, Aug 1, 2016 at 5:24 PM, Julian Hyde > wrote:
>
> > Looks much better
[
https://issues.apache.org/jira/browse/EAGLE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403390#comment-15403390
]
Michael Wu commented on EAGLE-406:
--
I'll do the research for how to get icons for differen
[
https://issues.apache.org/jira/browse/EAGLE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403384#comment-15403384
]
Michael Wu commented on EAGLE-406:
--
Sure, there are a variety of usage upon the status ico
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: [![B
*Community Development at Beijing/Shanghai/San Jose.*
1) 2016/4/21-4/23 QCon by Chen, Hao (Beijing)
http://2016.qconbeijing.com/speakers/202018
2) 2016/5/12-5/14 DTCC2016 by Su, Liangfei (Beijing)
http://dtcc.it168.com/
3) 2016/5/28 JavaCon 2016 by Chen, Hao (Shanghai)
http://javacon.topgee
[
https://issues.apache.org/jira/browse/EAGLE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403345#comment-15403345
]
Hao Chen commented on EAGLE-406:
Could you add code coverage ICON like
https://github.com/
[
https://issues.apache.org/jira/browse/EAGLE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403310#comment-15403310
]
Michael Wu commented on EAGLE-406:
--
CI job for building upon develop branch on each check-
Michael Wu created EAGLE-406:
Summary: Add develop branch CI build status to README.md
Key: EAGLE-406
URL: https://issues.apache.org/jira/browse/EAGLE-406
Project: Eagle
Issue Type: Task
Awesome
On Sunday, July 31, 2016, Michael Wu wrote:
> Henry, it works now for me, thank you very much!
>
> On Sat, Jul 30, 2016 at 12:25 AM, Henry Saputra >
> wrote:
>
> > Seemed like the change has been merged. Could you give it a spin?
> >
> > - Henry
> >
> > On Thu, Jul 28, 2016 at 10:49 PM,
Good point on "steps to graduation". That should be something we
will/should do instead of something we have done to get Eagle graduated.
@Hao/@Ralph, can you add activities in China conferences in section of
"community development"? Looks you had some activities in last quarter.
Project name:
+1 to mention about graduation discussion.
- Henry
On Mon, Aug 1, 2016 at 12:14 AM, Julian Hyde wrote:
> I think you should mention that the community is discussing
> graduation, and that is completed the maturity assessment.
>
> Maybe revise the "steps to graduation" in the light of those
> di
[
https://issues.apache.org/jira/browse/EAGLE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401928#comment-15401928
]
ASF GitHub Bot commented on EAGLE-403:
--
Github user haoch closed the pull request at:
Github user haoch closed the pull request at:
https://github.com/apache/incubator-eagle/pull/288
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
[
https://issues.apache.org/jira/browse/EAGLE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401926#comment-15401926
]
ASF GitHub Bot commented on EAGLE-403:
--
GitHub user haoch opened a pull request:
GitHub user haoch opened a pull request:
https://github.com/apache/incubator-eagle/pull/288
EAGLE-403 Fix bad status text
https://issues.apache.org/jira/browse/EAGLE-403
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/haoch/incuba
The twitter account (https://twitter.com/TheApacheEagle) has been updated
with http://eagle.incubator.apache.org/ now.
Thanks
- Hao
On Mon, Aug 1, 2016 at 5:24 PM, Julian Hyde wrote:
> Looks much better, thanks.
>
> Someone should update the twitter account's description now that
> goeagle.io
Github user anyway1021 closed the pull request at:
https://github.com/apache/incubator-eagle/pull/269
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fe
Looks much better, thanks.
Someone should update the twitter account's description now that
goeagle.io has gone away: https://twitter.com/TheApacheEagle.
On Mon, Aug 1, 2016 at 2:16 AM, Michael Wu wrote:
> Hi there,
>
> Ticket Eagle-380 is closed, and eagle site has been updated with all the
> m
Hi there,
Ticket Eagle-380 is closed, and eagle site has been updated with all the
modifications. This time, in pages, we add footnotes to indicate some words
representing Apache projects, such as "hadoop", "hbase", "storm", etc, and
tag the corresponding footnote number at the top-right corner o
[
https://issues.apache.org/jira/browse/EAGLE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401740#comment-15401740
]
Michael Wu commented on EAGLE-380:
--
site has been updated with the modifications, so this
[
https://issues.apache.org/jira/browse/EAGLE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu closed EAGLE-380.
> fix eagle site/doc branding issue
> -
>
> Key: EAGLE-380
>
[
https://issues.apache.org/jira/browse/EAGLE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Wu resolved EAGLE-380.
--
Resolution: Fixed
> fix eagle site/doc branding issue
> -
>
>
I think you should mention that the community is discussing
graduation, and that is completed the maturity assessment.
Maybe revise the "steps to graduation" in the light of those
discussions. None of those 3 came up when I asked "What is left to do
before Eagle graduates?". I think Eagle is close
[
https://issues.apache.org/jira/browse/EAGLE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401625#comment-15401625
]
Hao Chen commented on EAGLE-405:
The problems happen when there are empty in some tag field
30 matches
Mail list logo