 |
 |
Well, not sure ReWeight should be tagged as 3.0.2. Keeping the Generator and ReWeight version numbers the same, is not as great idea as it might look. What if we find a bug and need to produce a new ReWeight version? Do we also produce a clone Generator release with a new tag, only so that we can keep tag numbers in sync? Do not like the potential proliferation of tags, without it being warranted by code changes, only so that all products can be kept in sync. What if we consider Comparisons and Tuning too? Do we keep everything in sync, tagging all 4 products together? Or do we introduce variations to the numbering scheme (3.0.2a etc)? Isn’t 3 numbers just enough info for organising releases? What is wrong with a simple table associating supported combinations of products. The goal with the document is that it precedes the release. Not knowing whether more commits will follow today does not sound like a robust starting point for deciding that we have a release tomorrow? Are there residual problems or not? cheers C -- Dr. Costas Andreopoulos, FHEA Associate Professor University of Liverpool and STFC/RAL http://costas.andreopoulos.eu Sent from my iPhone > On 28 Nov 2018, at 16:40, Dytman, Steven A <[log in to unmask]> wrote: > > Generator release will be 3.0.2, not sure about ReWeight release. > We should keep numbering similar, how about also using 3.0.2? > > Steve > >> On 11/28/2018 10:26 AM, Steven Dytman wrote: >> Robert, Steven G, and I have been making small changes to Generator >> and ReWeight. >> Some commits have already been made, perhaps more today. Our goal is >> to have >> new release tomorrow. >> >> We will put together a small document and post it to docdb. >> >> regards, >> Steve >> >>> On 11/26/2018 10:27 AM, Costas Andreopoulos - UKRI STFC wrote: >>> Same as always? Guess we are talking strictly about a bug-fix >>> revision of the Generator (3.0.2) or the first tag of ReWeight >>> (effectively, a bug-fix revision of what we would have already >>> released in October had it still been part of the Generator). >>> So, some documentation of the bug fixes (eg a DocDB document, or info >>> submitted together with a pull request - whatever is most appropriate >>> given the scale and scope of changes) + some validation showing the >>> bug was fixed and nothing else was screwed by mistake. Then we can >>> take it from there. >>> C >>> >>>> On 26 Nov 2018, at 16:03, Dytman, Steven A <[log in to unmask]> wrote: >>>> >>>> ok, we have important deadline very soon. What is procedure for >>>> agreeing >>>> on a release? >>>> >>>> Steve >>>> >>>>> On 11/26/2018 10:40 AM, Costas Andreopoulos - UKRI STFC wrote: >>>>> I can not connect on Wedns. I am teaching and then I am travelling >>>>> to IFIC. >>>>> C >>>>> >>>>> On 26 Nov 2018, at 14:12, Dytman, Steven A >>>>> <[log in to unmask]<mailto:[log in to unmask]>> wrote: >>>>> >>>>> excellent idea, is that all right with you, Costas? >>>>> >>>>> On 11/26/2018 7:54 AM, Marco Roda wrote: >>>>> Hi Steve, >>>>> >>>>> ok, no problem. >>>>> Maybe we could use the time slot we had this summer for the tuning: it >>>>> was Wednesday at 10 am Chicago time. >>>>> >>>>> Cheers, >>>>> Marco >>>>> >>>>> Il giorno lun, 26/11/2018 alle 13.41 +0000, Dytman, Steven A ha >>>>> scritto: >>>>> There is a significant snow storm in the Chicago area, not sure what >>>>> to do. >>>>> Researchers here coming back from elsewhere surely have lots of >>>>> trouble >>>>> yesterday and today. Those of us here have up to 1 ft=30 cm of snow. >>>>> >>>>> Meeting is postponed, but we still have to decide when we are done >>>>> with >>>>> changes to reweighting. I'm thinking midweek, we'll have to stay in >>>>> touch >>>>> via email & slack. Steven and I are still doing tests and Robert >>>>> was >>>>> supposed >>>>> to have info on splines early this week. >>>>> >>>>> Steve >>>>> >>>>> ##################################################################### >>>>> ### >>>>> >>>>> To unsubscribe from the NEUTRINO-MC-CORE list, click the following >>>>> link: >>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jiscmail.ac.uk%2Fcgi-bin%2Fwebadmin%3FSUBED1%3DNEUTRINO-MC-CORE%26A%3D1&data=02%7C01%7Cdytman%40pitt.edu%7C892f14d4573c4dcd1c5c08d653bc2048%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C0%7C636788464802973660&sdata=gCZNprjdR5tPIivPrWxqr%2F%2FydwuTaMBbyubd7zreA4I%3D&reserved=0 >>>>> >>>>> >>>>> >>>>> ######################################################################## >>>>> >>>>> >>>>> To unsubscribe from the NEUTRINO-MC-CORE list, click the following >>>>> link: >>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jiscmail.ac.uk%2Fcgi-bin%2Fwebadmin%3FSUBED1%3DNEUTRINO-MC-CORE%26A%3D1&data=02%7C01%7Cdytman%40pitt.edu%7C892f14d4573c4dcd1c5c08d653bc2048%7C9ef9f489e0a04eeb87cc3a526112fd0d%7C1%7C0%7C636788464802973660&sdata=gCZNprjdR5tPIivPrWxqr%2F%2FydwuTaMBbyubd7zreA4I%3D&reserved=0 >>>>> >>>>> >> > > > ######################################################################## > > To unsubscribe from the NEUTRINO-MC-CORE list, click the following link: > https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=NEUTRINO-MC-CORE&A=1 ######################################################################## To unsubscribe from the NEUTRINO-MC-CORE list, click the following link: https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=NEUTRINO-MC-CORE&A=1