Making it easier to hack on debian-cd

[Dimitri John Ledkov]

Hi,

Currently lp:debian-cd points at an obsolete SVN mirror of Debian's
debian-cd. They have moved to git on salsa.

The Ubuntu's debian-cd is branch is exposed as a mirror of a mirror
(?!) of a production checkout at lp:~ubuntu-cdimage/debian-cd/ubuntu
which is in bzr.

It makes it slightly harder to discover, and default merge proposals
end up being against dead-end lp:debian-cd.

Note, I do not know the deployment details, hence I have no idea if
the below things are at all feasible deployment wise, and/or would
make cdimage team's life harder.

Is it at all sensible to consider doing any of the below steps to ease
hacking on debian-cd by non-cdimage team members? For example:

* Register `ubuntu-cd` project, and make lp:ubuntu-cd the default branch

* Convert from git to bzr

* Split development branch tip and deployed branch tip into separate
bzr series or git branches (e.g. lp:ubuntu-cd or git `master` is
development tip, whilst lp:ubuntu-cd/ubuntu or `ubuntu` branch is what
is currently deployed on production)

Code changes

* Can we please rm old releases from the branch? E.g. debian only has
three dirs, and it makes grepping and comparing things easier, when
one doesn't have the clutter of every ubuntu release ever. After all,
the history will remain in the branch if fault-finding is needed.

* Hack in devel/ by default, with just a symlink e.g. `bionic`
pointing to it during development of `bionic`, and convert symlink to
stand alone directory post-release. This way, devel, would have all
the history accumulating, including sensible `log -p` and `blame`
commands working as expected, rather than constantly resulting in
`massive copy&paste to start new series`.

Let me know if any of the above crazy ideas are at all welcome to be
implemented. And if yes, I can help to make them true. Otherwise, I
shall continue to
$ bzr branch lp:~ubuntu-cdimage/debian-cd/ubuntu ubuntu-cd
to hack on our image sets.

-- 
Regards,

Dimitri.