Hi Klaus
I read yesterday a part of your answer mail to a question of vdr user:
In VDR version 1.4 the CA_PMT records (that's the data a CAM needs in order to know which PIDs it shall decrypt) are sent to all CAMs in one CI device. I know that this can be a problem, and that's why I'm going to address this first thing in the upcoming 1.5 developer version.
I like to know if you have create a to-do-list for new developper release...
thanks for your work on vdr
bye kikko77
tinconn@virgilio.it wrote:
Hi Klaus
I read yesterday a part of your answer mail to a question of vdr user:
In VDR version 1.4 the CA_PMT records (that's the data a CAM needs in order to know which PIDs it shall decrypt) are sent to all CAMs in one CI device. I know that this can be a problem, and that's why I'm going to address this first thing in the upcoming 1.5 developer version.
I like to know if you have create a to-do-list for new developper release...
Yes, I have a TODO list - but I'm not publishing it ;-)
Klaus
For now or for a long time? like when vdr-1.6 is release?
Klaus Schmidinger wrote:
tinconn@virgilio.it wrote:
Hi Klaus
I read yesterday a part of your answer mail to a question of vdr user:
In VDR version 1.4 the CA_PMT records (that's the data a CAM needs in order to know which PIDs it shall decrypt) are sent to all CAMs in one CI device. I know that this can be a problem, and that's why I'm going to address this first thing in the upcoming 1.5 developer version.
I like to know if you have create a to-do-list for new developper release...
Yes, I have a TODO list - but I'm not publishing it ;-)
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
We haven't even gotten to 1.5 yet so I wouldn't expect a release date for 1.6!
Klaus, any particular reason you're not releasing the TODO list?
VDR User wrote:
Klaus, any particular reason you're not releasing the TODO list?
Probably to keep expectations down. If feature X is on the todo list, then it might be implemented next week. Or next month. Or next year. Or in 5 years. Or never. But people will for sure ask every week 'when will feature X be ready?'... ;)
I too would love to help planning and improving new features at an early stage. The more heads, the better. But thats life. There can be only one Klaus. ;)
Cheers,
Udo
Udo Richter wrote:
VDR User wrote:
Klaus, any particular reason you're not releasing the TODO list?
Probably to keep expectations down. If feature X is on the todo list, then it might be implemented next week. Or next month. Or next year. Or in 5 years. Or never. But people will for sure ask every week 'when will feature X be ready?'... ;)
That pretty much sums it up ;-)
I simply want to have the freedom to work on whatever seems like fun at any given time. With a public TODO list we would end up discussing when which feature will come and why this one is more important than that one...
Klaus
You could always just include a disclaimer in the list and refer people to it any time they ask questions like those. :)
On 8/11/06, Klaus Schmidinger Klaus.Schmidinger@cadsoft.de wrote:
Udo Richter wrote:
VDR User wrote:
Klaus, any particular reason you're not releasing the TODO list?
Probably to keep expectations down. If feature X is on the todo list, then it might be implemented next week. Or next month. Or next year. Or in 5 years. Or never. But people will for sure ask every week 'when will feature X be ready?'... ;)
That pretty much sums it up ;-)
I simply want to have the freedom to work on whatever seems like fun at any given time. With a public TODO list we would end up discussing when which feature will come and why this one is more important than that one...
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
VDR User wrote:
You could always just include a disclaimer in the list and refer people to it any time they ask questions like those. :)
It would not help, the list would still be full of whinings and moanings that, "why *my* important stuff has not been done" (replace *my* with your name) Security through obscurity works here :)
On Fri, Aug 11, 2006 at 10:13:22PM +0200, Klaus Schmidinger wrote:
Udo Richter wrote:
VDR User wrote:
Klaus, any particular reason you're not releasing the TODO list?
Probably to keep expectations down. If feature X is on the todo list, then it might be implemented next week. Or next month. Or next year. Or in 5 years. Or never. But people will for sure ask every week 'when will feature X be ready?'... ;)
That pretty much sums it up ;-)
I simply want to have the freedom to work on whatever seems like fun at any given time. With a public TODO list we would end up discussing when which feature will come and why this one is more important than that one...
well, I think that is one of your freedoms as free software developer, to decide what you do with your time, and if somebody disagrees with your priorities (which will for sure happen, sooner or later) that person can go ahead and implement that feature in a personal tree and submit it for inclusion ...
I don't think that a public TODO list would change that, nor the expectations folks have, it would just give an idea what _you_ personally consider interesting areas to work on.
but if you think that such a list would restrict your 'freedom' in working on whatever seems like fun to you, I'm perfectly fine with that too ...
have fun! Herbert
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr