On Fri, Nov 8, 2013 at 12:17 PM, Robert Park <firstname.lastname@example.org> wrote:
> On Thu, Nov 7, 2013 at 10:13 PM, Andrew Starr-Bochicchio
> <email@example.com> wrote:
>> * UDD
>> - bzr-builddeb hasn't seen any real development in some time. I've
> Hmmmm. bzr-builddeb works fine for me. The problem is with the UDD
> *branches*, which are an unmitigated disaster.
Sure. As I said, these are some topics that I'd personally bring up.
bzr-builddeb is in usable shape, but like any piece of software has a
number of bugs. Right now, the Launchpad team that has commit access
to it is ~bzr-builddeb-hackers, which is mostly made up of people who
have moved on to other things. If ~ubuntu-dev had commit rights, like
for ubuntu-dev-tools, there is potential to empower people who use it
day to day to fix the nagging little issues they hit and expand the
universe of people able to do code reviews.
I did originally have a second bullet point under that topic about the
general state of UDD, but I deleted it before sending. I didn't want
to open that can of worms myself as I don't have any real solutions.
It's unlikely that the well-known problems are going to be fixed
unless Canonical decides to reinvest resources into UDD. It seems
pretty obvious the community can't/won't take over driving it forward
(though I'd be happy to be proven wrong).
Though since we're talking about it, the one stop gap fix that would
make me happy would be if all Ubuntu Developers could trigger the
equivalent of the local 'requeue_package.py --full' command that UDD
admins can run. Some history might get lost, but at least out of date
branches could be made usable.
-- Andrew Starr-Bochicchio
Ubuntu Developer <https://launchpad.net/~andrewsomething>
Debian Developer <http://qa.debian.org/developer.php?login=asb>
PGP/GPG Key ID: D53FDCB1
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel