[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Please upload cups 1.7.1-5



Till,

Le vendredi, 14 février 2014, 17.31:01 Till Kamppeter a écrit :
> I have committed changes on CUPS to GIT, adding features for running
> the CUPS daemon on-demand, once to trigger cupsd via Upstart's socket
> bridge and second, to automatically shut down CUPS when it gets idle
> (no jobs, no shared printers).

First, please make sure to adhere to the source policy [0] which I 
mentioned to you multiple times already:

* one commit per change, no changelog entry committed
* DEP-3 headers in all patches
* one commit per release with the full polished changelog entry

In this one single commit, you have added _three_ patches (none of which 
have been reported upstream) and released a new version; then you just 
come and request that Debian includes your invasive patches in a new 
upload to our development release without preliminary discussion at all.

Doing things "Debian first" shouldn't mean "discuss things on Ubuntu-
devel without including the Debian maintenance team, then prepare 
invasive patches, dump them on the packaging repository and file a 
ticket on their list to have them upload it for you".

I would have preferred if debian-printing had been informed of the 
discussion I then found today on ubuntu-devel. I would also have 
preferred if you had dumped such invasive patches on a master-ubuntu 
branch and uploaded preliminary packages to Ubuntu's development 
distribution: there are things that are worthwhile to do "Debian first" 
(most things that are _not_ Ubuntu specific should be done together and 
in coordination with Debian), but you can't rely on volunteers to upload 
your R&D work in a timely manner to Ubuntu through Debian.

So, for now, I'm quite annoyed and have other things to do in the next 
days, so don't expect an upload from me right now. Feel free to upload 
this to Ubuntu first, I will likely backport most of it at a later 
point.

OdyX

[0] Sure, it's unwritten (yet), but if you look at the history you can 
get it, I'm sure.

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: