[
https://issues.apache.org/jira/browse/SOLR-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875482#comment-16875482
]
Jason Gerlowski commented on SOLR-13537:
----------------------------------------
I've merged Marcus' PR to master. I was thinking about copying this back to
other branches {{branch_8x}} etc, but after considering it a bit, I'm less sure
that's a good idea. {{master}} is the branch where the build-badges are most
visible. It's also the branch used most by novice developers- the ones most
likely to get use out of the build-badges. (Typically, new contributors offer
patches/PRs against master and it's up to the committer to work with other
branches from there.)
Anyway backporting the build badges to other branches offers less value, and it
also carries a bit more risk. The {{master}} build jobs will be around
indefinitely, since our branching model has us always working off of
{{master}}. Other branches aren't as "sticky" - eventually jobs for other
branches will stop running and get deleted indefinitely, so unless we're going
to remember to remove the badges later it's probably not worth adding them to
{{branch_Yx}} branches.
Unless anyone makes a good argument for porting this to other branches, I'll
close this ticket out. Thanks for the idea and the legwork Marcus.
> 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
> Assignee: Jason Gerlowski
> Priority: Trivial
> Attachments: Markdown Preview Of Build Status README.png, Simple
> Artifact Build Badge.png, Simple Artifact Build Badges.png, Single Line
> Badges.png
>
> Time Spent: 40m
> 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
