Quality Assurance for the PPA
manu at seeta.in
Wed Oct 27 17:19:35 BST 2010
Yes. Makes complete sense.
Dipankar and Neeraj,
Any implementation issues with this workflow? Kindly share your feedback.
On Wed, Oct 27, 2010 at 9:47 PM, Luke Faraone <luke at faraone.cc> wrote:
> I've been hearing from a few people that recent updates in the PPA may
> have caused problems for users.
> I personally think we should, once we have more people who are part of
> the Ubuntu Sugar Package set (~ubuntu-sugar-uploaders), point people to
> a PPA in that restricted team, and upload to an "unstable" PPA
> maintained by ~sugarteam.
> In the interim, I'd prefer if we'd create a separate PPA for direct
> uploads, and have new uploads go there. We can then test them and
> collect feedback, copying over the packages to the main PPA (which has a
> lot of users) when we're verified that the packages won't cause problems.
> When possible, we should avoid using the PPA in general. It is
> preferable to do SRUs and backports to stable releases through official
> Ubuntu channels unless we *have* to ship something in the PPA. (Browse,
> for example)
> Does this make sense?
> │Luke Faraone ╭Debian / Ubuntu Developer╮│
> │http://luke.faraone.cc ╰Sugar Labs, Systems Admin╯│
> │PGP: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506 │
> Ubuntu-sugarteam mailing list
> Ubuntu-sugarteam at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ubuntu-sugarteam