[Dh-make-php-devel] Re: [Dh-make-php-commits] r209 - branches

[Charles Fry]

> > > 0.2.0 won't be released soon. I'm not that familiar with svn, but
> > > wouldn't it make more sense to take the R-0-1-1 release and use
> > > it as a base for R-0-1-2. pre-0-2-0 includes changes for
> > > R-0-2-0 already.
> > 
> > That's exactly what I thought I did. What changes from R-0-2-0 made
> > their way into pre-0-2-0?
> Back off. I was looking at the wrong file. pre-0-2-0 is ok, though
> the name still confuses me. I can take pre-0-2-0 for the release
> but we have to make sure everbody can checkout the sources of this
> release later. How is that accomplished? Tagging? If yes, then
> branches appear to me like a very temporary thing.

We can easily rename it. You choose the name you prefer. :-)

Tagging is indeed the means by which the source can be checked out
later. In fact, normally svn-buildpackage will tag for you (build with
--svn-tag), but as this is a branch, you need to do it yourself.

In general (outside of this project) tagging is static, it indicates
something that doesn't change (like a release that already happened).
Branching is dynamic, it tracks a different direction of development.
That is why it makes sense for us to have a single branch of all
development based on 0.1.0 but before 0.2.0. That single branch will
progress from 0.1.1 to 0.1.2 and possibly on, with each release being
separately tagged so that we can retrieve it later.

Is that clear? Does it sound like a reasonable plan to you? I certainly
don't mind doing something different if you prefer.

cheers,
Charles

-- 
Bridge prize
For men
Just half a buck
Try it, hostess
Change your luck
Burma-Shave
http://burma-shave.org/jingles/1933/bridge_prize
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/dh-make-php-devel/attachments/20060606/4de4a6da/attachment-0001.pgp