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 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.
I'm new to svnsync - but I think that would work.
Hen
