Create Task
Maniphest T5840

Providing PIM 16.12.3 stack for Zesty 17.04 release
Closed, ResolvedPublic
Actions

Description

So post release, or even maybe on release day, it would be good to have PIM 16.12.3 stack available in a ppa for whoever may want to add that to their Zesty install over 16.04.3.

The question in my mind is more where to provide this?

  • In backports ppa?

Pros = obvious place.
Cons = people may add that on zesty release to get PIM, but may not necessarily be up for getting updated plasma/frameworks, digikam, kdevelop etc....

  • Updates ppa?

Not really the place officially, but should mention it anyway.

  • A separate ppa just for the backports of the PIM stack this time?

Pros = people could opt just for that and be done with it.
Cons = we risk separating things out to much and having issue on dependencies, whereas everything in backports lives and builds together.

rikmills created this task.Apr 7 2017, 2:23 PM
rikmills renamed this task from Providing PIM 16.12.3 stack for Zestyu 17.04 release to Providing PIM 16.12.3 stack for Zestyu17.04 release.
rikmills renamed this task from Providing PIM 16.12.3 stack for Zestyu17.04 release to Providing PIM 16.12.3 stack for Zesty 17.04 release.Apr 7 2017, 2:25 PM
valorie added a subscriber: valorie.Apr 12 2017, 10:11 PM

I vote for a separate PPA just for testing PIM. If it passes testing, we can put it in backports PPA.

rikmills added a comment.Apr 18 2017, 3:32 PM

backports-landing is a separate ppa, so that would be the logical place.

Or to we want to land this for testing somewhere completely different?

rikmills moved this task from Backlog to Ready 4 Work on the Kubuntu board.Apr 22 2017, 11:17 AM
rikmills added a comment.EditedApr 22 2017, 11:29 AM

I would like to suggest a slight change in plan for shipping these updates based on 2 usage cases:

  • Case 1 - A user or organisation who wants to update to PIM 16.12.3, who is happy to add the backports ppa, and is happy to receive further updates/backports of other applications (Plasma, apps, FW. digikam, krita) though the normal backports ppa.
  • Case 2 - A user or organisation who wants in the majority to use the default Zesty, but is missing the update to PIM 16.12.3 and would like to add just this.

Case 1 is obviously served by adding the normal backports ppa and leaving that enabled.

Case 2 could be served initially by the normal backports ppa, as long as the user is instructed to and remembers to disable the ppa after updating.

However, they would:

  • (a) not get any bugfixes to 16.12.3 PIM should we find the need to push those (security updates etc), and
  • (b) in the case of someone installing Zesty afresh in a few months or weeks time, when we may have pushed additional packages to backports, it would be difficult for such a user to just get the PIM update they want and nothing else.

Therefore to serve Case 2 I would suggest that we make a separate ppa (say backports-pim) for zesty and copy just PIM to that, in addition to having it in the normal backports ppa as well.

rikmills closed this task as Resolved.May 3 2017, 12:38 AM
rikmills claimed this task.