[osflash] Using FAME w/ source control

[James]

Martin,  Aral, thanks for your replies.  I have another question after 
working with this some more.  It may be a matter of preference versus 
best practice, but I am new to source control.  Should we build locally 
and then publish to Test, UAT or production?  Or is there a method of 
building inside the test or UAT environment that I am missing?  I am 
experimenting more with Ant, is that what I should be using?  I 
appreciate your answers and experience, maybe it will help me avoid 
mutiny among the new crew.

James

Aral Balkan wrote:

> Hi James,
>
> I agree with Martin's points -- and will try to elaborate on some of 
> them:
>
>> get them to check out the core stuff and get it in their classpath.
>
>
> If your custom controls/libraries are to be used across projects, it 
> would make sense to have them in their own project/projects and, as 
> Martin pointed out, include them on your classpath (the worst thing to 
> do is to have a different copy of a library, etc. in each project as 
> these will drift out of sync in a heartbeat and leave many heads 
> a-scratchin' :)
>
>> then if they find a bug in the core code, they can always check it 
>> in, everyone else can do an update, and bingo...youre all working 
>> from the same codebase and can roll back any changes anyone makes..
>
>
> And remember that source control is not an alternative to 
> communication -- the old school way we've been communicating with 
> since we were swinging from the trees (or frolicking in Eden, if that 
> rocks your boat): With mouths, hands and funny faces :)
>
>> obviously after this point you get into the realm of managing 
>> check-ins, branching and other fun stuff.
>
>
> And subversion makes all this much easier (a branch, for example, is 
> just a copy of a folder -- as is a tag.)
>
>> btw i think this is the perfect place for this question judging from 
>> the traffic ive seen in the short time ive been here..
>
>
> Me too :)
>
>> p.s. also when you are adding new people to projects, its worth 
>> having some documents describing your coding conventions...you know 
>> people always have their own preference, but basically you have to go 
>> with the people running the show...
>
>
> And remember to make them as lightweight and simple as possible or 
> people will simply not use them. If you plan to write a 1000-page 
> magnum-opus, it will make a handy door stop :)
>
>> i might not like braces on the same line as statements (an ugly trend 
>> :) but if thats what the company uses, thats what i have to use
>
>
> That's the attitude :)
>
> Take care,
> Aral
>
> _______________________________________________
> osflash mailing list
> osflash at osflash.org
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>