All,
I have now branched USSC218. I will test and wrap it for the CD over the
weekend, fingers crossed everything should be OK. Also, I have tried to
enable Watches on the CVS repository so that you should be able to do
something like
cvs -d :ext:[log in to unmask]:/cvs watch add package-list
to get E-mail notification of changes to the package-list file, say.
It would be good if we could do this to watch the whole USSC218 branch, but
I do not know if this would work for a whole branch?
Steve.
-----Original Message-----
From: Rankin, SE (Stephen) [mailto:[log in to unmask]]
Sent: 13 June 2003 13:20
To: [log in to unmask]
Subject: Re: Repository status
Here is an outline of the commands/procedure for a branch at release time.
First get the current java stuff (for me)
cvs -d :ext:[log in to unmask]:/cvs checkout -d starjava-USSC218
java
cd starjava-USSC218
Now tag/branch it (me)
cvs -d :ext:[log in to unmask]:/cvs tag -b USSC218
Command for people to get the branch,
cvs -d :ext:[log in to unmask]:/cvs checkout -d starjava-USSC218 -r
USSC218 java
Command to commit changes to the branch for the release,
cvs -d :ext:[log in to unmask]:/cvs commit -m "Bug fix comment" -r
USSC218
If you have done a checkout of the branch and made changes in that version,
then a commit will only update the branch, you do not need to add the "-r
USSC218".
I am not keen on merging the branch back into the main tree, as it may cause
allot of conflicts. I think it would better if programmers just submit the
branch changes to the main tree when they feel like it.
I will do the branch a 3.00pm today if there are no objections.
Steve.
-----Original Message-----
From: Giaretta, DL (David) [mailto:[log in to unmask]]
Sent: 13 June 2003 12:16
To: [log in to unmask]
Subject: Re: Repository status
Mark
all constructive criticism is welcome and gentle digs at Martin are allowed.
Cheers
...David
-----Original Message-----
From: Mark Taylor [mailto:[log in to unmask]]
Sent: 13 June 2003 10:58
To: [log in to unmask]
Subject: Re: Repository status
On Fri, 13 Jun 2003, Rankin, SE (Stephen) wrote:
> Mark,
>
> As it got pointed out to me, this release time has been difficult due to
the
> need for software to be in place that is required for more pressing
issues.
> I suppose this made exact dates hard to determine this time. The next
> release should be more organised I hope, especially now that I have a
> complete overview of the procedures. Hopefully the classic starlink will
be
> under CVS control for next time, which should make thing easier for
everyone
> if we have the procedures for dealing with CVS in place.
Yes, I understand that exact dates are hard to do and there are
usually complicating factors of ones sort or another, it's just
a request that if there are dates/plans which you/RAL have, then
they get communicated out to the rest of us.
I didn't mean to sound too critical by the way, the system certainly
seems to be more under control than it was a couple of years back.
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] 0117 928 8776 http://www.star.bris.ac.uk/~mbt/
|