Charles Plessy schrieb am Wednesday, den 30. June 2010: Hi,
*snip* > Thanks for the fast answer! > > First of all, I would like to make clear that I am not trying to bikeshed > xulrunner: I am more self-centered than this and was only thinking on how to > use backports.debian.org for the Debian Med packages (this is why I opened a > separate thread). > > When I asked about relaxing the rules, I was in particular thinking about > upload of backports prepared by the original maintainer, before testing > migration. For instance in some cases, it is crystal clear from the debdiff > and > the maintainer's tests on his computer that some changes uploaded to unstable > will not introduce new bugs. Updating the backport at the same time would save > some time and simplify our schedules (no upload echo 10 days later). The other > constraint that I would be interested to be lifted is the passage through the > NEW queue when the backport maintainer is the original maintainer, but if it > requires toolchain development, I understand that this would not be done > (again > the goal is to remove issues from the radar after upload). I'm strongly against that. I want packages properly tested and in your own interest you should wait for testing migration of your packages. (of course there can be exception, but not in general). I want well tested packages in bpo (which means tested by users, not uploaders). > I think that backports.debian.org will be a tremendous addition to our > distribution, that will distinguish us from many others, and I thank you for > all the hard work and perseverence that lead to this. Since it opens many > possibilities, I think that it is important to have a discussion in advance to > make sure that the vision of the uploaders and the administrators fit well. In > particular, I think that the question of whether backports should only exist > for packages that are aimed at a stable release is a very important one. For > some of the packages I maintain, I predict that my users will be much more > interested in snapshots (to be consistent over a project) or backports of the > main package. In that sense, although the package in stable may be released > and > maintained with care, it will be more a byproduct than the real aim. I have the vision of well tested packages, maintained by experienced developers users can trust in. This is how I run backports.org and I plan to continue it. I don't want backports as a place for snapshot or to deliver development packages to users. > By the way, will the backports.debian.org uploads archived on > snapshots.debian.org? This is already done for backports.org and will be continued if the service is offical. Alex -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100630105824.gc6...@hawking.credativ.lan
