Re: Debian Haskell Policy and group procedures
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
On 3 Jul 2009, at 23:11, Joachim Breitner wrote:
The debatable details are:
* Who sets the release to unstable, and when?
* Who sets the git tag and when?
With the proposed scheme, the release in the changelog indicates the
desired state (package ought to be uploaded), while the tag indicates
the real state (this is the state that has been uploaded).
In pkg-cli-*, which I'm also an active contributor in, the sponsor
does both of these. IMO if the contributor also has to RFS somewhere
it doesn't matter what the release is set to in the changelog, and
it's much easier for people to eyeball by just pulling and viewing the
changelog than comparing the latest version against what the tags say.
Really not a huge issue though. I'd prefer my way but either is fine.
* Who works out the binNMU requests?
Until we have a tool that does it for us, we need to do that by hand.
I’d say the member should prepare that, just as he prepares the rest
of
the upload. But the request should not be sent to d-release until the
upload is made. I’d say that when a non-DD prepares a package, he
assembles the binNMU commands and includes them in the request for
sponsoring. The sponsor then sends it to d-release when he does the
upload.
It's fair for the contributor to do this. There does need to be a
quick guide though.
Iain
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkpOpuoACgkQPy0SnCC/zce1NACdFKIjJpiklFdxYMwd11Zvrpc+
94AAniOUKmmaO6+ZeUPWbr2R2LDxYnoN
=2jrO
-----END PGP SIGNATURE-----
Reply to: