On , Thiago Macieira wrote:
On Tuesday 29 July 2014 07:56:16 Carsten Haitzler wrote:
remember that upstream efl master is being used daily by its own devs
- all
day, every day, and 100's of others via things like AUR efl/e git pkg,
so it
gets a fair bit of visibility, usage and testing as it goes, so issues
are
often caught quickly. so it's not as bad as it may seem.
But that might not be enough. Until you actually release, there may be
binary
incompatible changes, unfixed regressions, etc. I do use Qt every day
and so do
hundreds of people, and every single commit is tested with 15000 tests
-- no
regressions are accepted.
master branch is used for release? There is no release branch for
Tizen:common binary release? (it seems to be tizen branch)
In the git, master branch is used for development process. In the
reality, It can be hard to be stable before stabilization process.
Can we make upstream branch to track the opensource upstream master
up-to-date? Because someone in the tizen want to use state-of-the-art
features in the EFL. Also sync process
And we still find issues during the release process.
I do not recommend following an in-development version of a project
UNLESS
you've got someone who is quite an expert doing it and able to help
with
issues found. EFL is probably such a case for us in Tizen, as is
probably the
Linux kernel.
Still, it's up to the maintainer to decide.
My intention is not to treat EFL as other opensources in the Tizen
because we treat those opensources as forked version.
So I want to make a process to fix it in the opensource if there is any
problem and merge it into tizen.
But It's up to the maintainer in the Tizen.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
