All,
Again, I was assuming that it would be one or two months to CVS release. The
CVS release in necessary for the build to work on more platforms, a good
advertising ploy.
I think the only question is do we keep /classic and CVS inline for the
couple of months?
In within that couple of months, I will have to think up a way of updating
an old systems with the new cvs built stuff. I think I will use Izpack Java
installer for this.
Steve.
-----Original Message-----
From: Starlink development [mailto:[log in to unmask]] On Behalf Of
Alasdair Allan
Sent: 19 April 2004 14:43
To: [log in to unmask]
Subject: Re: CVS Java stuff tag, testing-USSC219
> > > "After the release it will be redundant" - why? We're still a long
> > > way off having everything in CVS, and we will continue to need
> > > /classic until the conversion is complete.
> >
> > No, I don't think so...
> >
> > Basically we're going to move to CVS, the next release isn't until the
> > autumn. If we don't have the classic software in CVS before then we
> > may as well all give up and go home. The next release will be CVS
> > based, why put effort into something that won't get used.
>
> Because we need to be able to create and distribute usable systems in
> between full releases. What if someone (e.g. JACH) requests urgent new
> features - do we say "sorry you can't have them until the next official
> full release - and maybe not even then if problems crop up with the new
> system (which you have got to admit is not unlikely)"?
Pretty much, yes (sorry Tim)... if they're going to cut our funding to
this level we're going to have to cut some corners, this is a corner that
needs cutting. If we all concentrate on it we can get everything into CVS
inside a month.
> I do not think we should pull the carpet out from underneath us until we
> have a working, fully implemented carpet to *immediately* put in its
> place.
I think we have to concentrate all our efforts to create the new carpet,
and forget about keeping the old one clean.
Policy decision I think...
Al.
|