Old files removed

[dnash86]

Old SLHA files removed, new ones in https://github.com/cms-data/Configuration-Generator/tree/53X_incremental

[cmsbuild]

A new Pull Request was created by @dnash86 for CMSSW_5_3_X.

Old files removed

It involves the following packages:

Configuration/Generator

@vciulli, @cmsbuild, @covarell, @bendavid, @thuer can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@smuzaffar you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

[bendavid]

@dnash86 can you confirm this removes ALL files from Configuration/Generator/data which are now present in the external?

[dnash86]

@bendavid The list of files to remove matched the list sent by the requesters that the new requests run on. The other procedure could be to list those present in the external, and remove the filenames matching those, but I thought the easiest/best guarantee was to take the list of updated files provided by the analyzers themselves for removal.

[bendavid]

Can you explicitly check that there are no other duplicates compared to what is in https://github.com/cms-data/Configuration-Generator/tree/53X_incremental ?

[dnash86]

I checked, via this procedure:

git clone -b 53X_incremental git@github.com:dnash86/Configuration-Generator.git Configuration-Generator
ls Configuration-Generator/ > FilesToRemove.txt

I then tried to remove everything in that list from the directory I sent the pull from, and commit changes, and got a "nothing to commit" message.

[dnash86]

I will shortly be setting up a PR to the cms-data repository, with the updated slha files.

[dnash86]

PR to cms-data is set up, so we are ready to request a new CMSSW_5_3_X release, please advise on what else can be done to help.

[bendavid]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_5_3_X IBs once checked with relvals in the development release cycle of CMSSW or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar

[cmsbuild]

+1
Tested at: 531cb91
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9701/186443/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_5_3_X IBs once checked with relvals in the development release cycle of CMSSW (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-9701/186443/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_5_3_X IBs once checked with relvals in the development release cycle of CMSSW (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar

[davidlange6]

+1