On Thu, Feb 17, 2011 at 03:08:15PM -0500, Barry Warsaw wrote: > On Feb 17, 2011, at 06:51 AM, Scott Kitterman wrote: > > >1. From the LEP: Disabling dput uploads is not a nice to have. It's a > >misfeature that violates (AIUI) one of the core assumptions given to Ubuntu > >developers when this project was started: That we are free to ignore it. I > >find it very troubling that it's listed as a goal of any kind (the discussion > >about being able to enforce the use of merge proposals convinces me this is > >not accidental). > > Are you saying that you want to preserve dput as an upload option forever? Do > you see a future where dput *isn't* the interface for uploading a new package? > Let's assume that all the current blockers are fixed, e.g. source packages are > fast to download, etc. > > I think at some point there should be only one way to do it.
Push to upload implies that it is practicle to move all packages into bzr. For large packages such as the kernel, libreoffice, X etc, where those are not in python that would imply we have to extract the intended state out of that and then commit it into another VCS just to trigger the upload? I would tend more to think of dput as the 'assembler' way of uploading, with pushing to a build branch being the 'best' way to do things. Generally you should not need to force a new way on people. If the new way is better people will switch and use it. Removing the old way should not be needed to achieve your goals should it? -apw -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
