 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40084e3d@news.povray.org> , "Andrew Coppin v2"
<and### [at] btinernet com> wrote:
> Just been reading a book about "the role of CVS in opensource development".
> Anyway, I was just wondering loosely how work on the POV-Ray source code is
> organised. Do you folks use something like CVS/RCS/etc? Or do you have some
> other method? Just curiouse.
The POV-Team uses Perforce, a commercial source code management system.
While CVS might be nice for a small project, it lacks many features
mandatory for professional development (just compare CVS and Perforce
feature lists). Note that this is not the exclusive opinion of the
POV-Team. Another very popular example is the Linux kernel, whose source
code is managed with the commercial source code management system BitKeeper
rather than CVS.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 17 Jan 2004 00:57:11 +0100, "Thorsten Froehlich"
<tho### [at] trfde> wrote:
>The POV-Team uses Perforce, a commercial source code management system.
>...Another very popular example is the Linux kernel, whose source
>code is managed with the commercial source code management system BitKeeper
>rather than CVS.
What do you think, how does Perforce compare to BitKeeper for medium-
to large-sized commercial projects feature-, useability- and
price-wise? IOW, if the Team were offered donated copies of BitKeeper
as well as Perforce, which one would you choose? :)
Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <arbi00t3asdfc5hljm3vvl8b0b7kne4k3j@4ax.com> , Peter Popov
<pet### [at] vipbg> wrote:
>>The POV-Team uses Perforce, a commercial source code management system.
>>...Another very popular example is the Linux kernel, whose source
>>code is managed with the commercial source code management system BitKeeper
>>rather than CVS.
>
> What do you think, how does Perforce compare to BitKeeper for medium-
> to large-sized commercial projects feature-, useability- and
> price-wise? IOW, if the Team were offered donated copies of BitKeeper
> as well as Perforce, which one would you choose? :)
I can only speak for myself...
I would choose Perforce over BitKeeper because of the way BitMover
(BitMover, Inc. is the company behind BitKeeper) has a website with a lot of
FUD and there is no transparent pricing information at all either. In
general, I am very skeptical of companies engaging in such pricing and
information practices and if there is another choice I will avoid them if
possible at all.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I wonder why CVS seems to be the only (free) choice for a versioning
system which people ever talk about.
We use PRCS at work, and it works quite ok. (I'm not saying it's better
than CVS, I'm just wondering why people only talk about CVS, as if it
was the only choice.)
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I wonder why CVS seems to be the only (free) choice for a versioning
> system which people ever talk about.
> We use PRCS at work, and it works quite ok. (I'm not saying it's better
> than CVS, I'm just wondering why people only talk about CVS, as if it
> was the only choice.)
Mmm... well, Microsoft Word is about the only work processor that you ever
hear anybody talking about. It's not that it's the only one there is (or the
best one there is), it's just the only one most people have heard of.
(I emphasise: *most* people...)
But anyway, for me, I was looking at SourceForge and trying to figure out,
like, what it IS. They had a link to a document about CVS, so I read it.
(I've tried to use CVS before, and it's a tad puzzling.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I wonder why CVS seems to be the only (free) choice for a versioning
> system which people ever talk about.
I've tried Subversion (http://subversion.tigris.org/) and it seems to work
nicely .. it's a replacement for cvs (people used to cvs should have no
problem to switch) fixing some of its weakness (see their web site for a
list of features)
M
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> The POV-Team uses Perforce, a commercial source code management system.
> While CVS might be nice for a small project, it lacks many features
> mandatory for professional development (just compare CVS and Perforce
> feature lists).
OK, fair enough...
I presume the source code download on the website is for v3.5, as released.
Is the current development source availible only to "official" developers?
(Not that it makes any difference to me - I wouldn't understand the source
anyway! - I'm just curiouse...)
Thanks.
Andrew.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <400c4968$1@news.povray.org> , "Andrew Coppin v2"
<and### [at] btinernetcom> wrote:
> I presume the source code download on the website is for v3.5, as released.
> Is the current development source availible only to "official" developers?
Indeed, source code access is by invitation only.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > I presume the source code download on the website is for v3.5, as
released.
> > Is the current development source availible only to "official"
developers?
>
> Indeed, source code access is by invitation only.
OK. (Presumably to prevent a "too many cooks" situation?)
But anyone who wants to can download and alter the source? (Subject to the
license terms of course.)
Sorry to be nosy!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <400d9330$1@news.povray.org> , "Andrew Coppin v2"
<and### [at] btinernetcom> wrote:
>> Indeed, source code access is by invitation only.
>
> OK. (Presumably to prevent a "too many cooks" situation?)
No, to prevent people distributing non-time limited versions of development
code. So happened a long time ago (I have been told an almost as long time
ago)...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
