Re: For discussion - CVS at sourceforge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


--- In script-fu@xxxxxxxxxxxxxxx, Ismael Valladolid Torres 
<ismaeval@xxxx> wrote:
> lasm.rm wrote:
> >   it started when Ismael posted the Analogize script, then i 
> > he had a German web page in some kind of source forge-like 
> > management system... which set me thinking ... hmm... how about 
> > giving source forge a try and see what it is like ?
> It's not that I have a german web page. [1]BerliOS is kind of a
> [2]Sourceforge clone, with kind of an european scope. I like it 
> for some reasons: Runs faster, it's less overbloated than 
> and each project gets a wiki at [3]OpenFacts.
   Agree with you.. Sourceforge is like a maze, if you are first
time user, getting lost in the complex menu is expected.. Now i have 
a better understanding how it works.. The menu navigation is a 
pain in the unspeakable @#$^%:-) No wonder so many projects die
even before it started... !! The developers probably got overwhelmed 
in the maze..

> > 1) still need to keep different version names to store in the 
> > archive at yahoogroup, otherwise the version is not apparent 
> > you open the file to look..
> But that's a plus! Even using CVS, you'll need to release a stable
> snapshot of your work some time. CVS handles internal revision 
> for all your files, then you decide what version to give to the 
> blunde.

Yes. What i meant was outside of CVS, you need to invent
something like filename-1-0, and the translation between that
and filename is not automatic, if you need to archived it
like in the Files section of yahoogroups..

i was a little surprised that backups are the responsibility
of the project owners !! i thought they should take this 
pain away and make it easier for projects to survive there ??

> The definitive plus for CVS is how it handles multiple developers
> editing the same code. If modifications done by both don't 
> everything's all right. If they do, when committing they're 
presented a
> list of conflicts so they can resolve them before getting 
something that
> works.

Yes... If the developers know what they are doing, it should
work out fine.. Communication is important..

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page

Yahoo! Groups Links

<*> To visit your group on the web, go to:

<*> To unsubscribe from this group, send an email to:

<*> Your use of Yahoo! Groups is subject to:

[Index of Archives]     [Gimp Developers]     [Gimp Users]     [Yosemite News]     [Epson Inkjet Printers]     [Scanners]     [Gimp's Home]     [Steve's Art]

&hbsp; Powered by Linux