[ 
https://issues.apache.org/jira/browse/SOLR-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869799#comment-16869799
 ] 

Jason Gerlowski commented on SOLR-13537:
----------------------------------------

I'm considering committing this next week.

The build badges aren't as cool/meaningful as they could be if we had 
consistently passing tests, etc.  And I don't really buy that it provides any 
value for DevOps engineers (all of whom would be using formal releases vetted 
through other, stronger processes).  But there is at least one tangible benefit 
this patch offers: someone encountering a compile issue on {{master}} can look 
at the README for a clue to whether their local issue is a legit problem that 
the build slaves hit as well, or whether it's just a local environmental issue. 
 Since the risk of this change is super low, I think that's enough to make it 
worth committing.

Wanted to give this one last bump in case Jan or Shawn still had doubts about 
the value.

> Build Status Badge in git README
> --------------------------------
>
>                 Key: SOLR-13537
>                 URL: https://issues.apache.org/jira/browse/SOLR-13537
>             Project: Solr
>          Issue Type: Wish
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build, documentation
>    Affects Versions: master (9.0), 8.2
>            Reporter: Marcus Eagan
>            Priority: Trivial
>         Attachments: Markdown Preview Of Build Status README.png, Simple 
> Artifact Build Badge.png, Simple Artifact Build Badges.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In order to aid developers and DevOps engineers who are working in a 
> git-driven ecosystem, it would be helpful to see the status builds in the 
> README. This is a standard for many open source projects. I think one could 
> debate whether we should have a multi-line build badge visual in the README 
> because people need to know about the builds for various versions and 
> platforms in the case of Lucene/Solr because it is such a large and widely 
> used project, in a variety of environments. The badges not only celebrate 
> that fact, they support its persistence in the future with new developers who 
> look for such information instictively.
> I would recommend the active build pipelines (currently 8.x and 9.x) for each 
> platform, Linux, Windows, MacOSX, and Solaris.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to