On Thu, 22 Mar 2001, Craig R. McClanahan wrote:
> On Thu, 22 Mar 2001, Ted Husted wrote:
>
> > So, I've got an application that I'm working on that I'd like to check
> > into the sandbox CVS, so I can share it with some other Jakartians.
> >
>
> For sandbox, I don't think we need any hard and fast rules. It's an
> experimental playground, after all.
I agree we don't need hard rules, but I don't agree with "experimental
playground", as you know. The fact that it's open to all commiters doesn't
mean it's experimental, and for each component in the sandbox that is
included in a project the same review and voting rules apply.
Since sandbox components have a much bigger pool of reviewers and
participants probably the code that'll be picked up by projects will be
"less" experimental than what we see in many projects.
Ted - I think using the author name is not a good idea. Maybe something
based on the component functionality or some neutral name.
If you expect the component to be shared and other people to participate
and later to be included in a project or in commons, I think you should
use one of the existing layouts ( like taglibs, etc ).
> > Is the idea that I should create a branch for this, so it doesn't get
> > mixed in with other people's project?
> >
>
> In sandbox, there are no releases, right? Therefore, no need for
> branches. Even if there were multiple "projects" in the same CVS
> repository, branches won't typically be required because people will be
> building from specific subdirectories anyway.
Branches will be needed if a component is included in multiple project
releases, but at the component level ( i.e. each component will have
a tag and a potential branch for each release that it is part of )
Costin
