On Thu, 2014-12-04 at 13:24 +0100, Karol Lewandowski wrote:
> On 2014-12-03 12:03, Patrick Ohly wrote:
> > And last but not least, this alignment is *not* permanent. There will
> > continue to be per-project git trees which will allow using different
> > versions in Tizen than used in Yocto. But how often that is done is not
> > just a technical question (which we can discuss here) but also a
> > business decision (which needs to be decided elsewhere) because it
> > introduces additional maintenance costs.
>
> Is Yocto release schedule going to affect us in future?
It'll probably be useful to rebase onto the latest Yocto release, simply
to get newer upstream code into Tizen without having to update all
packages ourselves.
> Who is going
> to make these binding decisions?
As before: the owners of Tizen Common, in coordination with the steering
committee and other stakeholders.
> What's Tizen's benefit in all of this?
I think it'll make maintenance of Tizen less costly. There's just no
point in maintaining an entire distro when others are already doing the
job.
> Tizen.Org was supposed to place where we can do "next-get" platform
> devlopment, distant product from product development schedules.
I beg to differ here. Tizen IVI is treated as a product with a schedule,
and it is done on tizen.org. That means tizen.org is not a dumping
ground for experimental changes. There must space for that, but also for
stabilization.
> Bringing in non-transparent ("decided elsewhere") business decisions
> doesn't seem like recipe for success for me.
>
> Not that everything is 100% transparent right now, question is if
> this is step in right direction.
That and your questions about the business impact is for people who are
probably not following this list.
--
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
