[Yaird-devel] setting up a repository [was: Re: Plugins feature for yaird.]

[Erik van Konijnenburg]

On Tue, Nov 15, 2005 at 04:07:26PM +0100, Jonas Smedegaard wrote:
> I have tried and failed to feel comfortable with TLA. I am not entirely
> against it, but fear that the use of an (for me) awkward VCS tool could
> slow down too much my being productive with actual packaging work.

Admittedly, it's not pretty...

> On the other hand I see no problem in the main yaird development using
> TLA or whatever, as long as I was told just the command for doing a
> checkout of up-to-date source.
> 
> I believe it makes good sense to keep upstream and Debian-specific work
> separately anyway - to allow upstream releases in different pace than
> Debian ones (it would seem odd to have a new release for Debian due to
> a bugfix only relevant for Redhat).

Agreed.

> I will now apply for SVN to be added to this yaird Alioth project.
> Flame me if this is a stupid move...

Perhaps it's stupid, but at least it's a move, and that's good.
Let's get something working; we'll need some idea about what to put in 
which branch for that, plus naming conventions for branch and tags.

As a checklist, here's a sketch of stuff I think the branch&tag model
should support.
* reconstruct exactly tarball 0.0.12
* reconstruct exactly debian 0.0.12-7
* quickly enter a bugfix to be part of 0.0.13
* backport the bugfix intended for 0.0.13 to 0.0.12-77
* do so without copying all the changes that have been made to the
  NEWS file already.
* develop eg swsusp during a number of versions,
  and still allow bugfixes to be added quickly to mainline
* enter changes in development tree *quickly*.  We would not want
  to save up changes and occasionally dump a batch of them in the
  repo.
* incorporate bugfixes from a mainline in a development branch
* merge back development to mainline eventually ...

Did I miss anything?  I'm starting to learn SVN, no clear picture
yet how easy it is to support the above.  Ideas?

Regards,
Erik