Merging Moblin / Factory ... the plan.
Hi guys, So; we need to get all this stuff merged into Factory; of course, since we have few resource to do that, this is a great opportunity for people to get involved :-) a) first split off Moblin 2.1 in OBS (abock) + I believe this is done only internally + Aaron - can we do a copy here ? + otherwise, I'll just do a monster copypac across to there. --- at this point we can break M:F happily --- b) next - merge all -new- GNOMEish packages from into: GNOME:Apps and GNOME:Factory (as appropriate) + These versions should come from Moblin:Cleanup *BUT* + we need to check all recent fixes since Federico branched get included: sadly this is not at all easy with obs + manual .changes comparison is prolly the only way c) next - merge all cleaned up 2.28 patches into GNOME:Factory and GNOME:STABLE:2.28 with versioned links from GNOME:STABLE:2.28 back into Moblin:Factory + again these should come from Moblin:Cleanup where possible. d) rationalise non-GNOME packages, merge patches into: openSUSE:Factory (via their up-streams - if at all possible) e) build public Moblin:Factory vs. 11.2 only + built it vs. SLE11 [-SP1] only internally + provide public images from openSUSE:Factory / milestone builds. f) Development work to reconcile the mutter issue, and whatever else bites. How does that sound ? Regards, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
Le mercredi 17 février 2010, à 11:23 +0000, Michael Meeks a écrit :
Hi guys,
So; we need to get all this stuff merged into Factory; of course, since we have few resource to do that, this is a great opportunity for people to get involved :-)
a) first split off Moblin 2.1 in OBS (abock) + I believe this is done only internally + Aaron - can we do a copy here ? + otherwise, I'll just do a monster copypac across to there.
--- at this point we can break M:F happily ---
b) next - merge all -new- GNOMEish packages from into: GNOME:Apps and GNOME:Factory (as appropriate) + These versions should come from Moblin:Cleanup *BUT* + we need to check all recent fixes since Federico branched get included: sadly this is not at all easy with obs + manual .changes comparison is prolly the only way
c) next - merge all cleaned up 2.28 patches into GNOME:Factory and GNOME:STABLE:2.28 with versioned links from GNOME:STABLE:2.28 back into Moblin:Factory + again these should come from Moblin:Cleanup where possible.
d) rationalise non-GNOME packages, merge patches into: openSUSE:Factory (via their up-streams - if at all possible)
e) build public Moblin:Factory vs. 11.2 only + built it vs. SLE11 [-SP1] only internally + provide public images from openSUSE:Factory / milestone builds.
f) Development work to reconcile the mutter issue, and whatever else bites.
How does that sound ?
Let's do it. I'll start on Thursday, and will try to be full-time on it on Friday. I can help with b, c and f (f is just a matter of renaming the package to mutter-moblin and having some conflict between mutter and mutter-moblin). So if I understand things right, Moblin:Factory will be used to provide a "stable" build of Moblin (against 11.2), and all the real factory stuff will live in other projects. Is this right? Does that mean that the moblin team will push the fixes that will happen later (and the new packages that might appear) in the other projects too? Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
Hi Vincent, On Wed, 2010-02-17 at 12:37 +0100, Vincent Untz wrote:
Let's do it. I'll start on Thursday, and will try to be full-time on it on Friday.
Wonderful; thank you.
I can help with b, c and f (f is just a matter of renaming the package to mutter-moblin and having some conflict between mutter and mutter-moblin).
Ah - well, we have a mutter-moblin package that is the plugin for mutter already ;-) But, I tend to agree that it is a chunk of work reconciling those two, and perhaps one that we can't invest in now. So we need to think of a new name :-) As AJ suggests, these might be more elegant in a new devel project: Moblin:UI (?).
So if I understand things right, Moblin:Factory will be used to provide a "stable" build of Moblin (against 11.2), and all the real factory stuff will live in other projects. Is this right?
That was my plan ;-) perhaps it is the wrong one.
Does that mean that the moblin team will push the fixes that will happen later (and the new packages that might appear) in the other projects too?
Sure, I would hope so. Of course, the need to submit fixes to a plethora of different places is unpleasant; but - presuming we only get fixes into (say) a Factory branch of a Devel project, and M:F itself (where that is based on a 'STABLE' or 11.2 version), perhaps it is do-able. HTH, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Wednesday 17 February 2010 12:23:54 Michael Meeks wrote:
Hi guys,
So; we need to get all this stuff merged into Factory; of course, since we have few resource to do that, this is a great opportunity for people to get involved :-)
a) first split off Moblin 2.1 in OBS (abock) + I believe this is done only internally + Aaron - can we do a copy here ? + otherwise, I'll just do a monster copypac across to there.
--- at this point we can break M:F happily ---
b) next - merge all -new- GNOMEish packages from into: GNOME:Apps and GNOME:Factory (as appropriate) + These versions should come from Moblin:Cleanup *BUT* + we need to check all recent fixes since Federico branched get included: sadly this is not at all easy with obs + manual .changes comparison is prolly the only way
c) next - merge all cleaned up 2.28 patches into GNOME:Factory and GNOME:STABLE:2.28 with versioned links from GNOME:STABLE:2.28 back into Moblin:Factory + again these should come from Moblin:Cleanup where possible.
d) rationalise non-GNOME packages, merge patches into: openSUSE:Factory (via their up-streams - if at all possible)
e) build public Moblin:Factory vs. 11.2 only + built it vs. SLE11 [-SP1] only internally + provide public images from openSUSE:Factory / milestone builds.
f) Development work to reconcile the mutter issue, and whatever else bites.
How does that sound ?
I'm confused by the usage of repositories. Could you clarify the following (for after the change): * Where will Moblin UI packages get developed for openSUSE:Factory (what is the devel project) ? * What purpose will Moblin:Factory have? Thanks Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hi AJ, On Wed, 2010-02-17 at 13:20 +0100, Andreas Jaeger wrote:
* Where will Moblin UI packages get developed for openSUSE:Factory (what is the devel project) ?
Well; I guess inside the respective devel projects: In the absence of anywhere better I was planning to use GNOME:Apps and GNOME:Factory for the more gnome-ish new modules. We could of course use 'Moblin:UI' - or something; for the really new, clutter+stuff ones; perhaps a good plan.
* What purpose will Moblin:Factory have?
Well - we need to provide stable Moblin releases on the up-stream timeline, not that of openSUSE. So Moblin:Factory would be a place (I suggest) where the latest actually working version should live; and where we develop and test that stuff. But of course, that is just a stab in the dark; if you have a better design, that fits in better with openSUSE stuff - lets go for it. Bear in mind - that I have an almost total lack of experience of structuring this sort of parallel scheduled development, and/or deep understanding of the build-service and/or how -best- to avoid its many limitations. Indeed, that has been a substantial blocking factor in making any progress here. Thus your input now is much appreciated, and hopefully can help avoid problems in future. A focus (of whatever scheme) needs to be on ensuring that we have somewhere, that is not a wild-west of unstable versions, with uncontrolled updates; since we need to be able to have stable releases not based on the openSUSE time-line. I am also somewhat concerned that for a given change to Moblin:Factory (eg.) for a product, we would end up doing a submitrequest potentially to GNOME:Factory, GNOME:STABLE, Moblin:Factory, and potentially several repositories in ibs. This seems like a recipe for a horribly inefficient work-flow. That of course, could (perhaps) be avoided with un-versioned links; but this then makes tagging, snapshotting, or ever being able to reproduce a given build virtually impossible. Anyhow, better ideas much appreciated. Regards, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
Le mercredi 17 février 2010, à 13:20 +0100, Andreas Jaeger a écrit :
I'm confused by the usage of repositories. Could you clarify the following (for after the change):
* Where will Moblin UI packages get developed for openSUSE:Factory (what is the devel project) ? * What purpose will Moblin:Factory have?
This is what I understood after discussing on IRC: + Moblin:Factory aims to be a stable, usable Moblin for a released version of openSUSE (11.2 right now) + Moblin for Factory would come straight from openSUSE:Factory + Moblin:UI would be the devel project for the Moblin packages in openSUSE:Factory, but also for Moblin:Factory This now makes some sense to me, but I must admit I think it's still a bit confusing in some way, but mostly because it doesn't use the same terminology as other projects. This is what I would propose to make things clearer (it's not mandatory, and it requires a bit more work): + we have packages in openSUSE:Factory + Moblin:Factory is the devel project for the Moblin packages in oS:F (and nothing else) + Moblin:2.1 (and later M:2.2) is used to deliver the stable version of Moblin on released distributions (would build against 11.2 right now) => This would mean that the current content of M:F would be moved to M:2.1. + Moblin:UI disappears Most of the time, it will turn out that a package in Moblin:2.1 will be the same as the one in oS:F. In such case, we can use M:F as devel project for M:2.1 too. When Factory is frozen, M:F will also be frozen. However, work can continue in M:2.1 directly, and we'll sync packages once Factory gets unfrozen. (Or we could use a temporary Moblin:Unstable project to keep track of what changes, and make it easy to sync the packages later) Opinions? Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Wed, 2010-02-17 at 14:15 +0100, Vincent Untz wrote:
This is what I would propose to make things clearer (it's not mandatory, and it requires a bit more work):
+ we have packages in openSUSE:Factory + Moblin:Factory is the devel project for the Moblin packages in oS:F (and nothing else) + Moblin:2.1 (and later M:2.2) is used to deliver the stable version of Moblin on released distributions (would build against 11.2 right now) => This would mean that the current content of M:F would be moved to M:2.1. + Moblin:UI disappears
I like Vincent's naming scheme (i.e. this one) much better. It eliminates the mental switch required to do "Oh, Moblin:Factory is not based on openSUSE:Factory - what was it based on again?". Federico -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On 17 February 2010 20:25, Federico Mena Quintero
On Wed, 2010-02-17 at 14:15 +0100, Vincent Untz wrote:
This is what I would propose to make things clearer (it's not mandatory, and it requires a bit more work):
+ we have packages in openSUSE:Factory + Moblin:Factory is the devel project for the Moblin packages in oS:F (and nothing else) + Moblin:2.1 (and later M:2.2) is used to deliver the stable version of Moblin on released distributions (would build against 11.2 right now) => This would mean that the current content of M:F would be moved to M:2.1. + Moblin:UI disappears
I like Vincent's naming scheme (i.e. this one) much better. It eliminates the mental switch required to do "Oh, Moblin:Factory is not based on openSUSE:Factory - what was it based on again?".
Federico
-- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
One question I have is, how do we deal with GNOME packages that are used by Moblin but are heavily patched to get them to work how they need to? Can those patches be submitted up to openSUSE Factory or are they being taken on by upstream in which case this becomes an invalid question? My dodgy memory seems to vaguely recall a discussion about this but I can really remember. -- Andrew Wafaa IRC: FunkyPenguin PGP: 0x3A36312F openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
On Wed, Feb 17, 2010 at 02:25:17PM -0600, Federico Mena Quintero wrote:
On Wed, 2010-02-17 at 14:15 +0100, Vincent Untz wrote:
This is what I would propose to make things clearer (it's not mandatory, and it requires a bit more work):
+ we have packages in openSUSE:Factory + Moblin:Factory is the devel project for the Moblin packages in oS:F (and nothing else) + Moblin:2.1 (and later M:2.2) is used to deliver the stable version of Moblin on released distributions (would build against 11.2 right now) => This would mean that the current content of M:F would be moved to M:2.1. + Moblin:UI disappears
I like Vincent's naming scheme (i.e. this one) much better. It eliminates the mental switch required to do "Oh, Moblin:Factory is not based on openSUSE:Factory - what was it based on again?".
I like it too. It also makes the kernel stuff easier for me to track as well, because I am doing something like that already in our kernel git tree. Oh, that's also what these repos are for, we need different kernel packages, and I can't mess up the O:F kernel repos with the moblin kernel packages, people would start yelling at me that their machines were booting faster, and we can't have that :) thanks, greg k-h -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
Hi there, On Wed, 2010-02-17 at 14:25 -0600, Federico Mena Quintero wrote:
On Wed, 2010-02-17 at 14:15 +0100, Vincent Untz wrote:
+ we have packages in openSUSE:Factory + Moblin:Factory is the devel project for the Moblin packages in oS:F (and nothing else) + Moblin:2.1 (and later M:2.2) is used to deliver the stable version of Moblin on released distributions (would build against 11.2 right now) => This would mean that the current content of M:F would be moved to M:2.1. + Moblin:UI disappears
I like Vincent's naming scheme (i.e. this one) much better. It eliminates the mental switch required to do "Oh, Moblin:Factory is not based on openSUSE:Factory - what was it based on again?".
Ok - I like this too; but there is one tweak. If we start deleting / moving packages from Moblin:Factory we have serious problems; Federico's Moblin:Cleanup work is branched from there, and will immediately break and/or loose a lot of context. Secondly Aaron doesn't want to break the flow there for our engineers, some of whom are on vacation, without having something else to use. Thus - I think we need to use Moblin:UI as the devel project for oS:F. So - I'll write a new mail with a consolidated plan in it, that is hopefully complete. HTH, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: opensuse-goblin+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-goblin+help@opensuse.org
participants (6)
-
Andreas Jaeger -
Andrew Wafaa -
Federico Mena Quintero -
Greg KH -
Michael Meeks -
Vincent Untz