Date: Mon, 08 Dec 2008 11:25:17 -0500 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: Aristedes Maniatis <ari@ish.com.au> Cc: freebsd-stable Stable <freebsd-stable@freebsd.org> Subject: Re: visibility of release process Message-ID: <1228753517.56532.25.camel@bauer.cse.buffalo.edu> In-Reply-To: <B167228B-64FA-49D7-8AF7-55F5E4852EA0@ish.com.au> References: <B167228B-64FA-49D7-8AF7-55F5E4852EA0@ish.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-T13Ak8JHVDjXOAVCf97N
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Mon, 2008-12-08 at 20:57 +1100, Aristedes Maniatis wrote:
> I've resisted sending this email for a while since I really don't want =20
> to start a bikeshed nor a flame. However there comes a time to express =20
> my thoughts over the lack of visibility of the release process for =20
> FreeBSD 7.1. Here are the resources I am aware of:
[ Readers' Digest Version: Known problem. Unfortunately very slowly
being worked on... ]
Bottom line is my communication skills suck and of the bazillion other
things I could do with my time these sorts of housekeeping chores wind
up at a low enough priority they don't get done. But as you and others
have made clear the priority needs to get raised and I need to deal with
it. That's the part being worked on.
> I'd like to make several suggestions which could improve the =20
> transparency of the release process:
>=20
> 1. Short term fix: re could make a progress announcement on the =20
> appropriate lists every 14 days during the release process. Just a =20
> short summary of URLs pointing to the bug tracker.
That's what I'll be working on fixing short-term. Weekly status reports
here. One coming tomorrow (not coincidentally likely to include 7.1-RC1
is ready, that's why its not coming today; if you look around you can
probably find it but a few misc. tidbits aren't ready yet).
> 2. Some web based friendly end-user visibility on the commit process, =20
> per branch. People can see what is going in and being fixed, but not =20
> what is left outstanding. Fisheye is an option because it costs =20
> nothing except the small load on the svn server.
>=20
> 3. Improvements to the bug tracker. Personally I'd love to see =20
> something like Jira used [4] with all the sophistication of workflow, =20
> release notes, voting for bugs, etc, etc.
Those aren't really something I'd be likely to address any time in the
near future mostly because there are other folks around who are involved
in those areas. They both look like they require hooks into the guts of
various systems I'm more than happy other folks are much more involved
in. So comments on those likely need to come from someone else(s).
--=20
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
--=-T13Ak8JHVDjXOAVCf97N
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)
iEYEABECAAYFAkk9SmUACgkQ/G14VSmup/ZmEQCbBMxOYN7l5W9EhcAFHmrkKoml
32sAn2WI5C6NnAKkP+U6avUtt84/YUzt
=EF4W
-----END PGP SIGNATURE-----
--=-T13Ak8JHVDjXOAVCf97N--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1228753517.56532.25.camel>