IRC: Drop the Kubuntu beta backports

[OneLine]

Now

“Package Archives for Kubuntu” team

Now there are: https://launchpad.net/~kubuntu-ppa

Kubuntu Backports
Kubuntu Beta Backports
Kubuntu Experimental
Kubuntu Updates
Kubuntu Package Staging (DON'T USE)

The beta backports now: http://www.kubuntu.org/news/kde-sc-4.8.90

Packages for the release of the KDE Plasma Workspaces, Applications and Platform 4.8.90 are available for Kubuntu 12.04. You can get it from the Kubuntu Beta Backports PPA. They are also in our development release...

Future ?

Kubuntu devel irc:
http://irclogs.ubuntu.com/2012/06/18...ntu-devel.html

Riddell I'm mindful that backports take a lot of time to do and are only used by the sort of people who could upgrade to the development release 16:31

yofel well, we could drop the beta backports? Those happen during the times when we don't really have time for them. Backporting a stable release once a month for including ~2 point releases is ok IMHO 16:33
...
Riddell Mamarok as a non-dev how would that make you feel? to get beta from neon and devel release rather than beta backports 16:51
...
Mamarok so yes, dump the beta backports, since we have an alterantive 17:04
...

[claydoh]

its just a discussion right now, but you snipped out some of the thought processes in the discussion namely Neon as an alternative for testing beta versions of KDE.

Trying to reduce the work loads is a good thing (though I would miss the beta-backports personally), those who want the latest non-final KDE stuff would probably have a better experience running the latest non-final Kubuntu as well, overall.

[OneLine]

Preliminary discussion, white paper, blue prints, etc...

A thumb rule: All plans are subject to revision.




Quotes

Another thumb rule: Examine the source material - it has the truth and the whole truth...


More propositions

https://mail.kde.org/mailman/listinfo/
--> http://lists.kde.org/?t=133976177000003&r=2&w=2

Subject: Proposed adjustments to our release cycles

Hi all,

During our sprint in Pineda de Mar, we sat down and thought about how our
release cycles relate to the structures in our software, we came up with the
following proposal we'd like you to consider and provide feedback about.

Starting with KDE Frameworks 5, we will release Frameworks, Workspaces and
Applications each with their own release cycles. Each of these releases would
be a set of tarballs of the latest stable versions of the application (or
codebase in more general).
As an example, Frameworks could release updates every 2 months, while our
application collection is updated monthly. New iterations of the workspaces
come every four months. (These numbers are completely arbitrary, and here only
for illustration purpose!)

More specifically for the Workspaces, we would like to release all workspaces
at the same time...