Release Schedules and Feedback on Fixes

[Ruslan Zasukhin]

On 12/06/16 1:10 AM, "Robert Brenstein" <rjb at robelko.com> wrote:

> Ruslan, you seem to think that cvs will be something extra to do on
> top of what you do now. In reality, cvs should and will replace
> and/or modify what you do now.
> 
> All you need is to setup a decent server for cvs or subversion or
> whatever versioning software you choose, with raid and external
> backup system. 

We have all this last 4 years.

> One-time setup effort, and then it runs pretty much on
> its own, with ocassional system and cvs/subversion upgrades, of
> course. All your sources are on that server. The storage is very
> efficient because cvs stores diffs. Each developer checks code out
> for working and in when they are done. Checkin's automatically
> document the code changes. It does not matter whether your team
> members sit in the same room or are at different locations. The
> computers used for building actual ADK's just update their local copy
> of files from that server and then run compiling and linking. This
> can probably be also automated.

Robert, we have CVS of course :-)
 
> It seems to me that the biggest effort will be for you and your team
> to adjust to the cvs ways of thinking and functioning and set things
> up to get moving.

Yes, change mind.
 
> Most developer tools, including Xcode, have hooks for working with
> cvs and subversion. There was actually a nice, basic introduction to
> cvs in Oct 2006 issue of MacTech magazine and intro to subversion in
> their Nov 2006 issue. Check them out. If you don't subscribe to
> MacTech, I can scan these articles and send to you. They describe
> both pros and cons so you get a good overview.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]