RTMLandingApproaches

Differences between revisions 3 and 4
Revision 3 as of 2014-08-26 17:33:49
Size: 3390
Editor: sil2100
Comment:
Revision 4 as of 2014-08-26 17:52:56
Size: 3547
Editor: strehl-t
Comment:
Deletions are marked like this. Additions are marked like this.
Line 62: Line 62:


== FAQ/Problems ==

  * Adding RTM ppa doesn't work: adding the landing ppa will still fall back to utopic. Edit /etc/apt/sources.list.d/... manually

Possible ways to land changes to ubuntu-rtm

This place tries to overview some of the possible methods of landing your Ubuntu changes to Ubuntu-RTM. As everyone knows, currently ubuntu-rtm is should be our main development focus - with a requirement that every change first lands in Ubuntu. This can be troublesome and we, the Landing Team, are trying to figure out possibilities of how to make this easier for everyone.

Some approaches are still in the works. We expect things to be much easier once changes in the infrastructure are finished.

Manual dual landings for both using source-package copies (default)

Who is it for?

This approach is perfect for those that want all of their changes in ubuntu-rtm. Perfect for projects that only want to have one branch (trunk) for both ubuntu and ubuntu-rtm.

Requirements

Only one bzr development branch. Ubuntu and ubuntu-rtm in sync.

How to request such a landing?

Currently this will be the default approach, so any landing that's submitted for ubuntu will have an ubuntu-rtm silo prepared. We will make sure that the silo will be propagated with latest source packages from the ubuntu counterpart whenever requested. No additional action from the lander required. Please inform the trainguard whenever you want more up-to-date packages copied into the ubuntu-rtm silo.

If you do not want this mode to be used, please let us know beforehand when filling in the landing (in the comment field for instance).

Overview

This means that everything that you build in your ubuntu silo will be synced up into the ubuntu-rtm silo. With this, basically, both landings will happen more or less simultaneously. Currently this is sadly a manual process, but once the CI Train bits are ready, dual-landing support will be the way.

Separate branches, separate landings

Who is it for?

This approach is ideal for those projects that are not only focused on ubuntu-rtm or only some commits made to the development branch are safe enough for RTM.

Requirements

A different bzr branch for ubuntu-rtm features. Common naming scheme: ubuntu -> lp:foo, ubuntu-rtm -> lp:foo/rtm-14.09

How to request such a landing?

Please mention explicitly in the landing that you do not want a source-copy ubuntu-rtm silo, and that you will fill in a separate landing with different MP for the ubuntu-rtm bits. 'Target distribution' field mentions if the landing is for ubuntu or ubuntu-rtm.

Overview

The first announced landing method. See https://lists.launchpad.net/ubuntu-phone/msg09565.html for more details.

Dual synchronized landings (TODO)

Who is it for?

This approach is perfect for those that want all of their changes in ubuntu-rtm. Perfect for projects that only want to have one branch (trunk) for both ubuntu and ubuntu-rtm.

Requirements

Only one bzr development branch. Ubuntu and ubuntu-rtm in sync.

How to request such a landing?

Currently in the works, not available yet. Landings will be marked as 'dual' in 'Target distribution'.

Overview

This is the currently worked-on approach that will become the recommended way soon. Every press of the 'Build' button on the ubuntu silo will cause the build of the very same sources in the ubuntu-rtm silo as well.

FAQ/Problems

  • Adding RTM ppa doesn't work: adding the landing ppa will still fall back to utopic. Edit /etc/apt/sources.list.d/... manually

citrain/RTMLandingApproaches (last edited 2014-11-04 12:28:21 by sil2100)