2011-06-16, 22:10
Memphiz Wrote:Tested it on ATV2 ... there are multiple issues ... its turned off by default though. So this needs some time to work properly ...
Thx for the report Memphiz!
I'm not sure if everyone understand how this process works so I thought I'd mention how I understand it:
(please anyone correct me if I'm wrong)
Code gets forked for new feature XYZ (usually a fairly sized feature, like audioengine, dirty region, pvr, etc)
Devs hack on code to put in new feature and test it. Sometimes they sync the master branch back to their fork to make sure it works good, other times no.
Once everyones happy with stability, they put a pull request in to be reviewed to be pulled into MASTER and it gets talked about throughout the team, depending on how deep the feature is.
Master, trunk, mainline, etc, all mean the same thing. This is the currently 'in the works' version, the place where everyone plays. Emphasis is put on stuff being feature complete, not break the build and generally be a 'good' addition for XBMC.
Once that process is vetted, someone approves it and merges it in.
Now, keep in mind the code could of been written for a codebase of weeks/months ago, and all the devs need to flesh out the 'little things' that the specific devs that worked on XYZ didn't have a chance to test/didn't notice.
Think of this as a 'burn-in' time for the code to 'settle' in.
This is where I do my builds from, an area, while can be quite stable, that's because we have an awesome dev team.
Very few projects run such a usable master branch.
But still, when stuff 1st gets merged in it will *never* be stable enough it use. We are literally using the future right now.
And once the dust settles and months goes by, trac tickets go down and someone decides its good enough for an official release.
So in the last 8 months we've had 3 parts:
Part 1: OMG the code works! Davilla and CO's hard work paid off and builds are completely functional, code is public, we can play!
Part 2: Merged the code into MASTER. 1 build environment for everything, no more worrying about 2 separate code branches.
Part 3: Where we are now, which is getting ATV2 up to speed and adding in general Eden features. Now when something like 'dirty region' is added, it works for all platforms.
Hope this helps!