Joel as you can see from the CC: headers above this email is going out to more than just yourself. The point(s) I'm making below I consider to be important to the Debian project as a whole.
As can be seen from bug #23367, you sent me an email to tell me there was a newer version of gd than the most recent one I had released (as libgd, libgd-altdev, libgd1g, and libgd1g-dev). In the reply I sent to you I mentioned that I had only recently become aware of this new versionm and was in the process of preparing a package of it. I now see that you have uploaded a non-maintainer release of this new version to master.debian.org! To be blunt I'm pissed about this...indeed this is *not* the first time someone has decided to do a non-maintainer release of one of the packages I've been working on without checking with me first. I thought that a non-maintainer release was normally only done where either a security hole needed to be fixed quickly or where a serious problem existed with a package that the maintainer had not fixed for some time. <rant mode on> At this point in time I'm seriously considering if I want to remain a Debian developer if people are going to continue to tinker with and release updated versions of packages I'm maintaining without contacting me first. I know - why don't I decide to do a non-maintainer release of libc6 :-) At this stage I wondering whether I should drop work on all my packages (both released and unreleased) and either become just a Debian user or maybe even move over to a different distribution... <rant mode off> Ian, should non-maintainer releases be allowed into frozen/unstable without checking with the maintainer first? -- Dermot Bradley [EMAIL PROTECTED], [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
