| Re: Coyote Library Updates [message #87381 is a reply to message #87373] |
Wed, 29 January 2014 08:22   |
![Paul Van Delst[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Paul Van Delst[1] is currently offline")
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Hello,
On 01/28/14 15:18, David Fanning wrote:
> Helder writes:
>
>> given the fact that I have no idea what is happening when I daily
>> execute my svn checkout, it seems like I was using a different command
>> and things where working. So, I'm using:
>>
>> svn checkout http://idl-coyote.googlecode.com/svn/trunk/coyote E:\Where_I_Put_My_Stuff_On_My_PC
>>
>> Now the question is: Should I use the address:
>> http://idl-coyote.googlecode.com/svn/tags/coyote/coyote_libr ary_6.0
>> or
>> http://idl-coyote.googlecode.com/svn/trunk/coyote
>>
>> I have implemented this operation in my task scheduler not to forget checking for updates.
>
> No, you are doing things exactly right. :-)
>
> You start your day the way I do. (Of course, we have good and bad days,
> but hopefully more good than bad.) Paul wants a "stable" release. I'm
> never sure exactly what that means, because I update these files
> frequently (at least once a week and sometimes several times a day).
I want something that I can tell other people about. E.g. "before you
can use this software I gave you, you need to install vX.Y.Z of the
coyote library. Here's the URL..."
The tag specifies that release snapshot. It specifies it today. And it
specifies it a year from now. However, the trunk, sans a specific,
non-people-friendly revision number, is whatever the latest version that
has been committed (which may or may not work right. You're very good,
David, but, as you say, not poifect :o)
> But, if a few days to go by and I haven't made any changes and Coyote
> remembers to remind me, I make a tagged release.
>
> I do try very hard to have the main repository in good shape at the end
> of every day. I'm not perfect, but my score is pretty high.
>
> I know it annoys people to have a lot of these files "retired". But, it
> is a lot of work to get all the documentation changed over to the IDLDOC
> style that I can have on my web page. I do it a little at a time now,
> and only when I find I am using a particular program. Name space is
> getting crowded, and I would like to have all my programs with the "cg"
> prefix. Eventually, I might get there. When I do make a change, I make
> sure all my Library files reflect the change and all the articles on my
> web page reflect the change. This is a BIG job, which is another reason
> I'm not anxious to do it often. Even a simple change to a routine that
> is not used much takes an hour or so to effect. Most changes take most
> of an afternoon. Mistakes can be made. I typically wait a couple of days
> to make a tagged release after a major upset. I've learned the hard way
> to test documentation headers before I commit the files. :-)
It's hard work maintaining software. "Eight is a lot of legs, David"
ha ha.
cheers,
paulv
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
