|
[Rivet] Work for Rivet 2.4.0 release: call for contributions!Holger Schulz hschulz at physik.hu-berlin.deWed Sep 23 16:52:27 BST 2015
Oh and can you please all remind me not to forget to react to two bug reports Christian G. sent me? Thanks, Holger On 23/09/15 15:54, Holger Schulz wrote: > On 23/09/15 15:50, Andy Buckley wrote: >> Is this that "enthusiasm" thing I've heard about? > Nah just way too much coffee :) > > HOlger >> >> Andy >> >> >> On 23/09/15 15:46, Holger Schulz wrote: >>> On 23/09/15 15:43, Andy Buckley wrote: >>>> Hi Holger, >>>> >>>> Timeline is given on the line in between the two times it says >>>> "Holger" ;-) End of this week / start of next. >>> Allright! >>>> >>>> Do you remember what happened to the CMS 1122847 analysis for version >>>> 2.3.0? Chris thought you were assigned to it somehow, but I have no >>>> mention of it (at least not via the Inspire ID) in my email. >>> Allright! >>>> >>>> I think that segfault thing has been dealt with. Please try the >>>> release-2-3-x branch and scream if it still crashes. And/or check the >>>> changelog. >>> Allright! >>>> >>>> Thanks, >>>> Andy >>>> >>>> >>>> >>>> On 23/09/15 15:16, Holger Schulz wrote: >>>>> On 23/09/15 15:03, Andy Buckley wrote: >>>>>> Hi all, >>>>>> >>>>>> An update on the Rivet 2.4.0 status. I've merged James Monk & Gavin >>>>>> Hesketh's patches, and done a few other tweaks such that the only >>>>>> thing remaining on the Trello board is "integrate new analyses". >>>>>> Good >>>>>> time for a new release. >>>>>> >>>>>> I've also "done" the two that were assigned to me, at least as >>>>>> far as >>>>>> was possible. Here's an updated assignment list, with one more >>>>>> for me, >>>>>> two for David G, and two "missing" ones tentatively assigned to >>>>>> Holger >>>>>> ;-) >>>>>> >>>>>> Getting these integrated by the end of the week would be ideal, >>>>>> so we >>>>>> can run the validation scripts over the weekend. >>>>>> >>>>>> >>>>>> Others... Holger? >>>>>> CMS_2013_I1122847 (missing since 2.3.0 cf. Xavier's email) >>>>>> D0_2000_I503361.tar.gz >>>>> >>>>> Can do. What's the timeline? >>>>> >>>>> Also, I noticed that the MC_ELECTRONS and MC_MUONS have a histo >>>>> initialisation >>>>> problem leading to segfaults in rivet 2.2.1 --- not sure if this >>>>> is has >>>>> been dealt with >>>>> since then. >>>>> >>>>> Holger >>>>> >>>>>> >>>>>> >>>>>> Cheers, >>>>>> Andy, de facto release coordinator :-P >>>>>> >>>>>> >>>>>> >>>>>> On 21/09/15 00:06, Andy Buckley wrote: >>>>>>> Hi Riveteers, >>>>>>> >>>>>>> Another call for volunteers to do some analysis merging. Come >>>>>>> on, we >>>>>>> decided during the June face-to-face meeting that this was how >>>>>>> it was >>>>>>> going to work... step up! >>>>>>> >>>>>>> >>>>>>> To get the ball rolling, here's a couple of first allocations: >>>>>>> >>>>>>> Chris P >>>>>>> ATLAS_2014_I1326641.tar.gz >>>>>>> ATLAS_2014_I1327229.tar.gz >>>>>>> ATLAS_2015_I1387176.tar.gz >>>>>>> >>>>>>> Andy B (lectures start next week otherwise I'd take more) >>>>>>> CMS_2014_I1305624.tgz >>>>>>> CMS_2015_I1310737.new.tgz / CMS_2015_I1310737.orig.tgz >>>>>>> >>>>>>> >>>>>>> Come join us! David, Holger, Frank, others... here's your updated >>>>>>> choice, don't make Chris & I do them all by ourselves: >>>>>>> >>>>>>> CMS_2015_I1327224.tgz >>>>>>> CMS_2013_I1122847 >>>>>>> CMS_2015_I1346843.tgz >>>>>>> D0_2000_I503361.tar.gz >>>>>>> TOTEM_2014_I1328627 >>>>>>> >>>>>>> Replies and action pronto, please ;-) >>>>>>> >>>>>>> >>>>>>> As far as procedure goes, in case you were wondering, please add >>>>>>> these >>>>>>> analyses into the release-2-3-x branch as if we didn't know that >>>>>>> there >>>>>>> were big enough core changes to justify a minor (as opposed to >>>>>>> micro/patch) release. We'll merge that branch to default before >>>>>>> releasing 2.4.0. >>>>>>> >>>>>>> Thanks, >>>>>>> Andy >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 10/09/15 17:19, Andy Buckley wrote: >>>>>>>> Hey everyone, >>>>>>>> >>>>>>>> A reminder that we agreed to increase the Rivet release frequency, >>>>>>>> and >>>>>>>> that the next analysis update release should happen before the >>>>>>>> end of >>>>>>>> this month. >>>>>>>> >>>>>>>> If we hadn't done any other development in the last couple of >>>>>>>> months, >>>>>>>> that release would be 2.3.1, but we have actually changed enough >>>>>>>> (in a >>>>>>>> stable and complete way) to justify version 2.4.0. >>>>>>>> >>>>>>>> Unless there are pressing bugfixes or developments that I'm not >>>>>>>> aware >>>>>>>> of, all that remains to be done before validation is to hook up >>>>>>>> the 8 >>>>>>>> new analysis codes in the contrib directory: >>>>>>>> >>>>>>>> ATLAS_2014_I1326641.tar.gz >>>>>>>> ATLAS_2014_I1327229.tar.gz >>>>>>>> ATLAS_2015_I1387176.tar.gz >>>>>>>> CMS_2014_I1305624.tgz >>>>>>>> CMS_2015_I1310737.new.tgz >>>>>>>> CMS_2015_I1310737.orig.tgz >>>>>>>> CMS_2015_I1327224.tgz >>>>>>>> CMS_2015_I1346843.tgz >>>>>>>> D0_2000_I503361.tar.gz >>>>>>>> (note that two of these are "new" and "orig" versions of the same >>>>>>>> analysis) >>>>>>>> >>>>>>>> We also said that we would distribute the work, to make new >>>>>>>> analysis >>>>>>>> releases unintimidating for developers... so, who wants to >>>>>>>> integrate >>>>>>>> which analysis codes? ;-) Add the new analyses on the >>>>>>>> release-2-3-x >>>>>>>> branch, and I will sync them into default before we make the >>>>>>>> release >>>>>>>> (cf. earlier discussions about what sorts of changes go on which >>>>>>>> branches.) >>>>>>>> >>>>>>>> Volunteers please... thanks in advance. >>>>>>>> >>>>>>>> Andy >>>>>>>> >>>>>>>> PS. Holger/David, the contrib dir needs some umask or similar >>>>>>>> permissions set so that the tarballs are group-writeable. >>>>>>>> Several of >>>>>>>> these new ones aren't, so intervention from root will needed to >>>>>>>> move >>>>>>>> them to the pre2.4.0 dir when we make it. Also, the email >>>>>>>> notifications >>>>>>>> about new tarballs seem to be broken (right?) >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> > > _______________________________________________ > Rivet mailing list > Rivet at projects.hepforge.org > https://www.hepforge.org/lists/listinfo/rivet
More information about the Rivet mailing list |