Subject: |
Re: Release Numbers |
From: |
[email protected] |
Date: |
Wed, 23 Nov 1994 13:01:21 -0700 |
Nick writes:
> Firstly I am sure single letters will not suffice in the long term.
>
> Secondly whilst accelerator sites are fairly independent (and so having
> different release numbers for each site make sense), astronomy sites
> are not! Thus RGO and ROE have site letters, R and E, but they develop
> software for many end users, including our site, which supports two
> telescopes, each of which has different software architectures. In
> future we will support a third telescope, Gemini (site letter G). What
> I want to ensure is that software developed at other sites slots neatly
> into our release when it arrives. Having separate releases does not
> address this, and I think that we may have to think more about it,
> particularly the astronomy sites.
And, of course, to complicate matters, portions of RGO and ROE will be doing
development for Gemini whose site distribution (x.xx.G.x) is controlled
by the Tucson International Project Office. Not to mention the vast numbers
of controls and instrument work package developers located at distinct sites.
I agree that a single letter is not enough. I think we could already have
a conflict for 'R' - what will the RHIC use for example? I propose we use the
entire site/project name or common abbreviation:
LANL
ANL
CEBAF
:
GEMINI
KECK
JCMT
UKIRT
:
Peregrine
- Navigate by Date:
- Prev:
Re: digitizer boards Ned Arnold
- Next:
Infrequent I/O hardware Ric Claus
- Index:
<1994>
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Release Numbers Ric Claus
- Next:
Re: Release Numbers Bob Dalesio
- Index:
<1994>
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|