Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Declaring Neon M7 staging repositorycomplete

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,

 


Back to the top