On Wed, 2014-11-26 at 16:02 +0100, Dominig ar Foll (Intel OTC) wrote: > The infra team has taken the time to document a model proposition and > would like to get all the feedback possible. > https://wiki.tizen.org/wiki/Tizen-Distro_Workflow
Before diving more into it, let's clarify some points: What does "the above automation" refer to in the last section? Just the "Syncing of external repositories" or everything? In the "RPM vs. BitBake packaging meta data" section, can you clarify which meta data can be edited manually? It just says "packaging updated" and it does not become clear which one that is. But as the flow diagram always ends up modifying the .spec file, I assume that only the .bb data may be edited. What happens when a change gets committed with modified .spec? Before people on the list get concerned by these questions and draw wrong conclusions, remember that it will be a per-package decision how the package gets maintained. The initial goal is to convert those packages that we haven't modified much in Tizen anyway and already are maintained by the core distro maintainers. So the number of developers who really need to get used to the new workflow will be small - at least initially. Long term we'll see how useful the new workflow is. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
