I went to the AMPG meeting this evening. The basic plan was to recap where we were and
figure out what tasks we wanted to tackle in the next iteration. Thomas brought in the code from
last time and everybody started messing around with it on their own machine, trying to get it
set up so it could be demo'd. I thought this was kind of silly, because we only needed to have
it working on one machine, but oh well. We're programmers - we gotta have our fingers in the code.
I figured it would be easier if we set up a CVS repository
and had everybody sync to that. Thomas was planning on doing that as a task in the next iteration,
but I had started working on it and there's not that much to it. We spent more time trying
to set up the file sharing than anything else. Setting up a CVS repository ends up being one of
those things where you just have to know the magic incantation (or look it up in the online docs,
which is what I do). However, I do have my own method for doing the initial import which is
different from what is in the docs. If you follow the docs, you get this wierd initial
"vendor branch". Don't use cvs import. Instead, create the top level folder
in the repository by hand, do cvs update in a temp folder
to create a local workspace, copy the CVS folder from the temp folder to where your
source doe is currently living, then use cvs add to add all the files and subfolders
to the repository.
[
< Prev
|
Calendar
|
Next >
]
C o m m e n t s :
(nothing yet)