On Thu, 11 Dec 2014 09:08:06 -0800 Thiago Macieira <[email protected]> said:
> On Thursday 11 December 2014 16:11:33 Carsten Haitzler wrote: > > where is this release date documented? i have heard a mountain of tizen > > 3 "releae dates" come and go over time. there is nothing on the tizen 3 > > wiki indicating this. where is this officially agreed on in some formal > > way? and please don't say inside some jira tickets somewhere, some email > > sent (of whihc i can find none in the past few months with any subject > > on tizen 3 release), or some tsg meeting minutes which aren't exactly > > shared widely and prominently. > > > > my information atm as to tizen 3 release schedules is mid 2015. > > Good question. I don't know where it is documented. I know of that because > Tizen IVI 3.0 has a target release date for the end of the year (and no, I > don't know where that is documented either). Since IVI releases 3.0, we > conclude that Tizen:Common for the 3.0 branch must be feature-frozen, if not > deep-frozen. Thus, if you want to enforce things like "sorry - kdbus is too late now as release is N weeks away" policies, this should be documented. I know that most people around me see mind 2015 as a target for Tizen 3.0 and so are working with that date in mind, thus happily stuffing kdbus related patches in, upgrading efl even as we speak right now, etc. etc. etc. Since tizen 3 common is ... common ... it's expected that changes all profiles would share are going to get put into there... and it's going to happen and keep happening unless things like release dates, freeze periods etc are clearly communicated and up in "blinky lights". :) I think that perhaps our model for doing releases is a bit broken. Given the disparate needs of Tizen profiles, maybe Tizen common should be more of a rolling release. Maybe every 3 months it pops out a stable release that then is picked up by whatever profiles want it at that time. A regular release schedule will then reduce confusion over release dates. It's predictable. This will also work well with those that care about commercial schedules. There are well known dates for trhe next stable release from common to merge into their profile. One last thing - kdbus has been held up as a major feature of Tizen 3.0 for a very long time now. Core feature. If it's taking longer, then Tizen 3.0 takes longer. Same as Crosswalk - would you do Tizen 3.0 without crosswalk if it was late? As best I know Tizen hasn't taken the position of doing timed releases where "if a feature isn't ready yet, it doesn't go in that release". It is doing feature releases. A Tizen version X has features A, B and C. That means Tizen X waits for A, B and C. I don't remember any discussion, communication etc. about Tizen switching release models. Again - communicate, document etc. -- Carsten Haitzler (The Rasterman) <[email protected]> _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
