On 07/29/2014 07:12 PM, Philippe Coval wrote: > On 29/07/2014 12:05, Dominig ar Foll (Intel OTC) wrote: >> Hello; >> >> the strategy of Tizen has been so far to use the last Stable release >> when ever possible. > At this moment we're a litle late since upstream released a few > versions since > not the reason we did not upgrade at this time it was to keep common > aligned to ivi (or the opposite) ... > > Now It would also think it's a better timing to upgrade it > > Just need someone to propose this on jira > if noone is against for some reasons > then I can do that task if it helps > >> Following a daily of an upstream project is not the selected model. > this can be done in sandbox branches quiet easily > >> We have favoured stability and as far as I know that has not be been >> changed. > yes but sometime we need to make validate decisions on version jumps > > ie we have glib2 upgrade blocked for some time now : > https://bugs.tizen.org/jira/browse/PTREL-773 > > Regards > > ps: I upgraded the efl upstream branch and tags if it helps >
there is a general reason to upgrade efl - it has bugfixes your old version smapshot does not. we don't do bugfixes for older versions of efl for long. it even has secuurity fixes for lz4. it also has new features people will depend on soon enough and long nto the future. my advice is to track master until you get close to tizen common release. your release cycle is ~3 months (12 weeks). we release close to "like clockwork" so you can predict the release you want to then lock in before tizen common release and stick to that for tizen release. it will be easiest on everyone by a long shot. -- The above message is intended solely for the named addressee and may contain trade secret, industrial technology or privileged and confidential information otherwise protected under applicable law including the Unfair Competition Prevention and Trade Secret Protection Act. Any unauthorized dissemination, distribution, copying or use of the information contained in this communication is strictly prohibited. If you have received this communication in error, please notify the sender by email and delete this communication immediately.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
