Hi everyone again, and welcome back at the second issue of transcode development report. We're working really hard to keep those reports aperiodic and irregular, as promised ;)
Summary: ======== 1. - Recent changes on CVS 2. - Future plans 3. - Bugs, patches and issues recap 4. - 1.1.x release status 5. - 1.0.x release status 6. - Help Needed! *** 1. Recent changes on CVS ---------------------------------------- All missing pieces are slowing coming in. Input rotation is on the way, with following main sub-components: - input enumeration code: how to express multiple input? How to handle them - multiple input handling code: existing import code need some fixes/enhancements - multiple input probing code: which probing strategy should be used? Properly explaining those arguments isn't feasible on this report. So, I've started to write some new, up-to-date, organized new technical documentation covering the most significant changes made so far during 1.1.x cycle. Of course, due to chronical time lacking, documentation is still far from being vaguely complete. Preliminary work can found on CVS-HEAD/docs/tech/html Interested reader is greatly encouraged to read those docs, report typos and/or errors and ask questions on transcode-devel. 2. Future plans ---------------------- There is no much more to say here, we're still stuck on plan outlined in former status report. Releasing 1.1.0 ASAP is still our top priority. 3. Bugs, patches and issues recap ------------------------------------------------- (see http://tcfoundry.hostme.it/mantis for the whole archive) Since userbase for 1.1.x start to grow, more bugs are obviously popping out. We have two notable bugs this time. First one is control socket misbehaviour, kindly reported by Jorn Reder. This bug is of course a blocker for 1.1.0, but unfortunately is still uninvestigated due to lack of time Another significant problem is compilation troubles on Mac Os X, most notably related to 1.0.x branch. Fixing this will be problematic since gaining access to OsX boxes (both PPC and Intel) is problematic. 4. 1.1.x release status -------------------------------- In approx. priority order, the schedule is: * decoder updates (on the way) * implement effective input rotation (on the way) * roll out alpha (make new branch on CVS) * improve and tweak import_x11 * merge patches * docs! docs! docs! * fix bugs * roll out beta * fix bugs 5. 1.0.x release status -------------------------------- 1.0.3 was released 20070417, containing all and only critical hotfixes. 1.0.4 will (maybe) start sometime in the future, but as stated multiple time, all effort is devoted to 1.1.0 now. 6. Help Needed! ----------------------- We *gladly* welcome new people interested in having fun hacking transcode. There is a plenty of small tasks avalaible. Most of them are programming tasks, but there also some documentation and testing tasks avalaible. Main requirement is some time avalaible, C programming knowledge, agreeing in our coding/STYLE rules and at least a tiny bit of transcode knowledge. Interested? Jump in into transcode-devel and ask! Questions? Thougths? Bests, -- Francesco Romani
