<div dir="ltr">First, let me link to the CI jobs view:<div><a href="https://ci.jboss.org/hudson/view/Richfaces/">https://ci.jboss.org/hudson/view/Richfaces/</a><br></div><div><br></div><div>Btw renaming to RichFaces (instead of Richfaces) would be nice, but I'm aware of legacy links which could potentially link to that.</div>
<div><br></div><div>----</div><div><br></div><div>Ad) BADGE</div><div><br></div><div>@Juraj, we can certainly publicize a link to Jenkins job which does smoke tests.</div><div><br></div><div>There are two requirements:</div>
<div><br></div><div><ul><li>the job should be satisfactory stable, which means it won't fail ocasionally (this does not work on TravisCI atm - stability is ~90%),</li><li>we can get feedback for a build as quickly as possible (in TravisCI we get feedback in 30mins, which is more than I like)</li>
</ul></div><div><br></div><div>I'm not aware of a way how to publicize the job stability "badge" from jenkins.</div><div><br></div><div>----</div><div><br></div><div>Ad) SUFFIXES</div><div><br></div><div>I would keep the names as short as possible while staying meaningful.</div>
<div><br></div><div>I won't expect anyone to navigate through structure of labels which no one can understand.</div><div><br></div><div>----</div><div><br></div><div>Ad) NAMES FOR PARTICULAR JOBS</div><div><br></div>
<div>
richfaces-4.3-qa</div><div>richfaces-5.0-qa</div><div><br></div><div>richfaces-5.0</div><div>(no need to add anything here, it's our basic job which developers suppose to check before comitting and their failure is considered as a build failure - the build does not pass criteria)</div>
<div><br></div><div>Otherwise I like all of your suggested names.</div><div><br></div><div>+ we have discussed removal of some jobs from this view: vdl-doc, checkstyle, parent, share-transofrmers</div><div><br></div><div>
+ we have discussed ftests for other major browsers (complete framework test run in phantomjs and hopefully chrome)</div><div><br></div></div>