Revision Control for Waypointing
 

I am starting this thread so that waypointers and testers can discuss and define a comon revision notation in the absence of a proper revision control program like CVS. Even if somebody could set up a shared CVS we would still need a nav to text converter since CVS wont diff binary files intelligently.
This should help when reporting bugs especially when out in the wild on multiple servers.

Please keep this thread on topic,

Re: Revision Control for Waypointing
 

Crapshoot:
In the meanwhile an organizational suggestion to start with
With so many issues of fritzpak and no revision control system, I suggest adding some sort of note in the pk3 in the base directory and counting up a revision number. There are a hundered different ways to do a manual revision note. You could have one file or one file for every mapname. The rev number could be inside the file or in the name of the rev file. You could doc the changes in the file or just pipe a dir /s output into it with the file dates. Whatever you prefer for now Thanks

Re: Revision Control for Waypointing
 

I agree, version control is something that is needed. With the pending patch, all of the waypoints in the fritzPak will be put in to the fritz0.pk3 file though.

So for now, I'll just include a readme with version history.

Re: Revision Control for Waypointing
 

Here attached is the style I am using at this point.
Text file in \fritzbot directory of filename
README - <mapname> rev<Major digit>.<minor digits>.txt
Text in angle brackets<> to be filled in, stuff between square bracket[] optional. <mapname>, <your_name> etc could be automatically template replaced if people wanted to use a template capable editor (like Codewright), but I'll assume search and replace will be fine. You need pkunzip.exe in a command window to pipe the output and an editor with column select to quickly trim the unwanted stuff, but style under CONTENTS: is not critical (filename and date is enough). Note I am not 'touch'ing the files to the release date. I always thought the one filedate style of release wanting.
It looks like a lot of work but not really. Comments welcome.

Re: Revision Control for Waypointing
 

Was this adopted? It sounds like a really good idea, being that it's pretty hard to keep track of what is up-to-date.

Re: Revision Control for Waypointing
 

And where would the agency be located for adoptions?

Re: Revision Control for Waypointing
 

That's a tricky one, as it moves around a lot. Last I saw it, it was in the back corner of mp_beach. Look for their sign.