Re: [cross-project-issues-dev] Declaring Neon M7 staging repository comp

["David M Williams" <david_williams@xxxxxxxxxx>]

It is worth considering. (Though, doubt
I'd have time to work on it any time soon).

Accordingly, to track the suggestion
I have opened 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=493044

The long term goal is that each project
can run their own reports. 
This is actually possible to do now.
I have not advertised this much because
1) still quite a few limitations with doing so, but mostly 2) must be "run
as an Eclipse application" (instead of, for example, a maven plugin).

For those interested in being on the
leading-edge and running these reports in your own builds, the way I do
it in our Platform build is coded in a bash script in 
http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/production/createReports.sh
This could serve as a "getting
started" example for other projects. Your details would vary. 

In general, questions about these reports
and running them for individual projects can be addressed to the cbi-dev
list, since these reports are now part of the CBI (Common Build Infrastructure)
project. 

Thanks, 





From:      
 Konstantin Komissarchik
<konstantin.komissarchik@xxxxxxxxxx>
To:      
 David M Williams/Raleigh/IBM@IBMUS,
"cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>,
Date:      
 05/04/2016 11:48 PM
Subject:    
   Re: [cross-project-issues-dev]
Declaring Neon M7 staging repositorycomplete
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Would it be possible to convert reports
to e-mail alerts sent to project’s mailing list? I suspect we’d get better
compliance that way.
 
Thanks,
 
- Konstantin
 
 
 
From: David
M Williams
Sent: Wednesday, May 4, 2016 5:42 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: [cross-project-issues-dev] Declaring Neon M7 staging repositorycomplete
 
The iron is cooling and the last Git commit
is the last one in "recent changes" so I am assuming all is done
for M7. 

While EPP packages are being created and tested, be sure to sanity check
"staging", which is (still) at 

http://download.eclipse.org/releases/staging/

In parallel, this is a good time for project leads to look through the
most important "repo reports". (There are too many violations
for me to open bugs on them all). 

http://download.eclipse.org/releases/staging/buildInfo/reporeports/?d

Lots of unsigned jars: (the primary "third segments" are andmore,
eef, and  m2m. 

http://download.eclipse.org/releases/staging/buildInfo/reporeports/reports/unsigned8.txt

A surprising number of features and bundles missing legal files: (primarily
in what are new this release: cft and wst.jstd and wst.json) 

http://download.eclipse.org/releases/staging/buildInfo/reporeports/reports/layoutCheck.txt

Other reports are interesting and important for professional looking software,
but not as "blocking" as the two reports above will become. 

Unless blocking problems are found soon, this staging repo will be promoted
to .../releases/neon on Friday morning, approximately 10 AM (Eastern).

As usual, I have temporarily paused the Hudson jobs to avoid confusion
(except for the Gerrit triggered one) and will re-enable them the first
of next week.

Thanks, 
 _______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev