On Thu, 2005-07-07 at 14:32, Cyril Plisko wrote:
> > - managing integration branches of some sorts, eg. Solaris (vs.
> > opensolaris)
>
> Should be easy with SVN.
even if that integration branch shouldn't be public
(ie. not even stored on an opensolaris.org server)?
> > reasonably fast, by having a local storage to put their changes
> in
> Should be _really_ easy with SVN.
committing without connection to the server? or even without an
account on the server with write-access?
some definition of "commit" might be necessary, a proposal:
to commit is to
- create a snapshot or changeset that describes the new tree state
which can include a description, author, date, so that
- this snapshot/changeset can later be applied to other checkouts,
however it gets there (via some server, mail, peer-to-peer exchange,
..).
- that action should be possible to do for everyone using the same
tools
(ie. "second class developers" without write-access don't have to use
"inferior" tools)
> Hm, why do you think svn wouldn't be helpful in these cases ?
it's centralized. my claim is that, while centralization is necessary -
so that there's
a single tree where improvements end up, it should happen because people
want to ("I
want to get my changes into the common tree"), not by technical
limitations ("the only
way to work comfortably with the tree is to have write access to that
server - or to fork"),
where write access may require that you have a good relationship to
those managing the server.
patrick mauritz
_______________________________________________
opensolaris-discuss mailing list
[email protected]
