Hi Aparna, [email protected] wrote: > 1. There could be a great difference between latest version of the > upstream components and the version running on MeeGo in which case the > upstream version of the component may not even be compiling on the MeeGo > env. So are we expected to put our patch and work on OS where the latest > version can be compiled (like ubuntu, fedora etc).
MeeGo architects are working to ensure that developers are working with components close to the tip of upstream development. This *should* make it easier to patch both MeeGo and upstream with the same patch, at least for modules which are not changing at a very high rate. The expected workflow (as I understand it) is: 1. Prepare a patch for upstream (following upstream rules - either the latest upstream release or the tip of the main devel branch may be accepted) 2. Back-port this patch to MeeGo If the patch is delayed for any reason (missing review, for example) then the patch to MeeGo *might* be accepted if there is a reasonable expectation that the upstream patch will be accepted. If there are substantial changes required to the upstream patch, then you will probably have to fix issues and backport again, rather than having your original patch accepted in MeeGo. > 2. Is it possible that MeeGo branches from a specific upstream > version and we need to only work on the branched version? If yes is this > information going to be available somewhere? I'm not sure I understand the question. MeeGo will branch off upstream occasionally, but the rule is simple (even if the reality of applying it gets complicated): if you want a patch accepted into MeeGo, then the patch must be submitted to the upstream project in a form which can be accepted. If upstream accepts patches against older released versions, then fine. If upstream expects you to patch the tip of the main devel branch, then that's the standard. > 3. It will be good to have a page in wiki where list of MeeGo > components, their git links, bugzilla links, roadmap/plan links, branch > information is available. I agree :) Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
