[openbeos] Re: SourceForge & CVS
- From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 08 Sep 2001 05:15:10 -0400
First off, IMO, source control layouts are like coding standards, bellybuttons,
editors, etc.
Every one has a favorite and no one elses is as good. A religious arguement.
Having said that:
I never liked having versions in the source tree. To me, the thing is evolving,
so when is version 0.1 closed off and a new one made?
I dunno. Let me counter propose:
openbeos
kernel
docs (internal only)
source (approved only)
test
app_kit
...
media_kit
etc.
openBeBook
>Sounds reasonable to me. How about a structure like this:
>
>openbeos
> ver 0.1
> kernel
> docs
> internal
> public
> source
> approved
> ... current build files...
> submitted
> ... files submitted for approval...
> app-server
> docs
> internal
> public
> source
> approved
> ... current build files...
> submitted
> ... files submitted for approval...
>
> ...etc (for each module)
>
>
>The root would presumably be an ftp site.
>
>What about protection? I would suggest that all directories and files
>be viewable by anyone except 'docs/internal' and 'source/submitted'
>(since these are 'in-progess' files that wouldn't benefit from public
>comment). But no uploading w/o password. Each module directory would
>have a different password supplied by the project lead.
>
>New files would be uploaded to the 'submitted' directory. Someone --
>the project lead or perhaps someone else designated for the job --
>would do some basic checking on the submissions before moving them to
>the 'approved' directory. Only the designated person would access to
>this directory.
>
>Builds would be based on all the files in all the 'approved'
>directories. Builds could be conducted nightly.
>
>>
>>I have been trying to work with Sourceforge to do this. But Opera and
>SF
>>were not playing nicely together. Not sure what the deal was/is, but I
>will
>>try again today.
>>
>>I think what I want to do (and you can suggest otherwise, if you would
>like)
>>is create a repository with directories for each project, and a common
>dir
>>and allow the teams to keep things up under that as they wish.
>>
>>Also - does anyone object to using Be's makefile-engine?
>
>
Other related posts:
