> On Mar 20, 2019, at 11:25 PM, Daniel Shahaf wrote:
>
> I think wuzhouhui wasn't asking about branching models in general, but
> specifically about what model the Subversion project uses for versioning
> its own source code (https://svn.apache.org/repos/asf/subversion/).
Right, this is what I
limitations-not-in-git/>].
>
> On Wed, Mar 20, 2019 at 6:43 AM wuzhouhui
> wrote:
> > Hi,
> >
> > This question is unrelated to Subversion's usage or issues, but
> > related to version control model of Subversion source code. Let
> > me explain in
git/>
].
On Wed, Mar 20, 2019 at 6:43 AM wuzhouhui
wrote:
> Hi,
>
> This question is unrelated to Subversion's usage or issues, but
> related to version control model of Subversion source code. Let
> me explain in detail.
>
> As far as I know, new code is committed
* wuzhouhui:
> As far as I know, new code is committed to trunk firstly, then
> cherry-picked to release-branch in necessary [...] And tags are
> always created on release-branch.
It can be done this way, but that's not a requirement. One can also tag
'trunk', or any other branch.
-Ralph
Hi,
This question is unrelated to Subversion's usage or issues, but
related to version control model of Subversion source code. Let
me explain in detail.
As far as I know, new code is committed to trunk firstly, then
cherry-picked to release-branch in necessary, so the branch-view
of Subve
