Henri Yandell wrote:
On 1/18/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
All,
I just wanted to give a heads up that I am currently thinking that
blogs.sun.com could use its own place in Roller subversion for
branching/tagging our own releases. The basic situation is that we
develop and deploy at a faster rate than the project releases happen and
often times we deploy from builds of the active trunk. Up until now we
have tried to manage any branching/tagging for releases on our own side,
but it would make things a lot easier to branch/tag directly in the
Roller repository.
So, would anyone object to me creating a separate area in Roller svn for
maintaining up to a handful of BSC branches/tags?
-1.
I understand the desire - I'm maintaining patches for open source
projects locally for some projects and it can get painful. But this
would be a very bad precedent, only the PMC make releases. Also it'd
definitely be bad for it to be a branch rather than a tag, effectively
a private fork within the project. This came up previously, though I
don't remember what the project was and the opinion was definitely
negative.
I probably didn't explain what I needed properly, but I think you make
it sound worse than it is. The only thing this would be used for is to
be able to branch certain revisions of the trunk for short periods of
time. There is no forking or developing planned to happen in these
copies, they are merely meant to be there as a way to mitigate the
potential problem that can be caused when we plan to make use of a
certain revision of the trunk for a deployment while other folks may be
continuing to commit things.
I don't think you really need it either. How about using svnsync to
have a locally updated copy of Roller's trunk, and then tagging it
locally (or branching and adding whatever local patches might be
needed). It should be much the same as maintaining the branches within
Roller's repository.
Yes, but it seems to me that the point of having a repository is for
doing things like this.
I'm new to svnsync - but I think that would work.
Lots of things will work, but why not use the repository for what it's
meant for? I am not proposing that I am going to keep dozens of custom
releases around or maintain a fork of Roller in its own repository. I
only need the ability to maintain some level of stability to the trunk
at certain times.
So for example, I have a need to deploy basically what is currently in
the trunk. However, Dave and Mitesh are working on some things which
are hacking away at the backend and I don't want to have that work
disrupt my deployment. So, what you normally do is create a branch and
then I can merge in whatever changes I want until the trunk stabilizes
again.
Is there really something wrong with that?
-- Allen
Hen
