[kubuntu-devel] Discussing an "Official" Kubuntu PPA scheme

[Antonio Augusto (Mancha)]

On Mon, Apr 27, 2009 at 11:07, Clay Weber <claydoh at midmaine.com> wrote:
> On Monday 27 April 2009 9:28:28 am Jonathan Riddell wrote:
>> On Thu, Apr 23, 2009 at 02:27:35PM -0400, Jonathan wrote:
>> > Hey all,
>> >
>> > Congrats on the release, etc. I think this is really going to be a good
>> > one.
>> >
>> > :)
>> >
>> > More to the point, I would like to discuss/propose a scheme for the
>> > "official" PPAs that Kubuntu uses. Currently we have four or five PPAs
>> > lying around, which is confusing for everyone. We have:
>> >
>> > - Kubuntu-members (unused for a while)
>> > - Kubuntu-members-kde4
>> > - Kubuntu-experimental
>> > - Kubuntu-updates-testing
>> > - Kubuntu-ninjas (private, for staging new upstream releases that are
>> > embargoed upstream)
>>
>> I believe that launchpad now supports multiple PPAs per team so maybe
>> we should use that.
>>
>> I think Kubuntu-updates-testing is needed for backporting beta
>> releases (e.g. KDE 4.3 beta will come out soon).  I think this is
>> different from experimental which we do use for genuinely experimental
>> packages (a new release of network-manager say).
>>
>> So I'm thinking create a team  kubuntu-ppa and PPAs in it
>>
>> - updates      for minor new releases such as 4.2.3 that haven't been
>>                tested enough to go to ubuntu updates
>> - backports    for new releases such as KDE 4.3.0 that haven't been
>>                tested enough to be moved to Ubuntu backports
>> - beta         for backports of KDE 4.3 beta
>> - experimental for random new packages and also used for building
>>                non-embargoed packages before moving to backports or
>>                beta
>> - kubuntu-ninjas  embargoed packages
>>
>> This doesn't reduce the number of PPAs but they did all exist for a
>> reason.  Possibly beta and backports can be one, if you don't want
>> beta you can just not add the archive until the .0 comes out.
>>
>> Jonathan
>
> My thinking on this, from a more end-user point of view:
>
> updates, backports(ppa) and normal backports (Unsupported Updates) will be a
> little confusing I think, though I am sure the descriptions on each ppa would
> clarify that.
>
> I agree on -experimental and -beta  being merged, or perhaps have one called -
> bleeding-edge or something along those lines, though I realize that is just
> semantics
>

Clay, for what I get these reps won't be publicly announced. They will
be used for developing the next software that will go to Kubuntu, and
should be used only by experienced people willing to take part of the
development process.

KM