[Komport-devel] CVS is live and usage ...

[Mark <m....@sh...>]

To start this discussion regarding CVS usage and tagging of files, my 
experience from some experienced individuals is to keep commits specific 
to a change if possible.  Searching the comments can help find the 
change or future issues.  (Radical rewrites of course do not count and 
might be a reason to branch at some point?)  The key they feel is to 
make sure that whatever is in CVS compiles.  (Again another case for a 
branch of the code in CVS if/when necessary.)

My goal at some point is to get the tagging of every release made and 
see whatever else I can do with what SF allows.  (Already behind with 
0.5.9, I know)  My thought on releasing an 'unstable' version is to hold 
off for right now.  If someone is interested, they can checkout from 
anonymous CVS the latest which may or may not work ("unstable").

As you may or may not have noticed, the packaging source has not been 
added to CVS.  If someone could send me at least some of the files to 
have a base with, I will tag appropriately to move on.  (Thought I sent 
an e-mail to Steven but might have been bounced?)

Mark

Mike Sharkey wrote:
> Hi All,
> 
> I think I've successfully committed the changes to bring the repository up to 
> the latest 0.5.9 version (I had to make a few bug fixes after 0.5.8). People 
> should now be able to build the latest from the repository.
> 
> Let me know how it goes, please.
> 
> Everyone involved in the project should have write access to the repository. 
> Please let me know if you need an adjustment to your privileges.
> 
> Mark, I'm hoping you will keep everyone in line with respect to repository 
> discipline. Maybe you could draft a set of basic guidelines.
> 
> What I would like is to be able to have tags or some mechanism to get to the 
> last buildable and runnable version. Anyone else have any input on repository 
> discipline?
> 
> Should we have a "stable" and "unstable" branch perhaps? I don't know, I'm 
> asking the CVS experts.
> 
> In any case, I will be working from CVS from now on. Any of you who are 
> interested in doing some KDE/C++ programming, please by all means feel free. 
> :)
> 
> A few house keeping chores and some TODO items I think we should get done over 
> the next little while:
> 
> * Put all string constants into one header file to simplify localization as 
> per Robert's earlier suggestion.
> 
> * Update the ChangeLog, AUTHORS, README, TODO files to contain useful 
> information.....
> 
> * Get package files (.spec, etc...) into repository.
> 
> I'll work on the TODO list next, as I think that's my biggest task right now 
> is to prioritize coding items for the 0.6 release.
> 
> Well, it's really looking good, thanks everyone for helping out!
> 
> Cheers all!
> 
> --Mike