On Tuesday 22 February 2005 07:50 pm, Brad Templeton wrote: > Well, there are indeed many motivations for coding. I'm coding features I > want for myself, but I polish and document them because I want other folks > to use them too. You have a "production" system as well as a dev system, > but you are the lead developer. Most people don't, and so are scared of > risks that will make them miss their favourite show -- such is the problem > when people come to depend on software.
I actually rarely test things on my 'dev' system, aside from (very) basic video recording and playback. Actual testing happens on my 'production' system - the only real distinction is that the 'production' system is only hooked up to the projector, so it's slightly harder to code on. =) > Anyway, you can arrange releases the way you like of course. I'm just > trying to expand on various motivations people have. It's also the case, > as you have no doubt read, that many people get a different interpretation > from the word "release" and so some of this might be solved just be being > clearer that the MythTV way of releasing is to declare a snapshot when > things seem stable enough. I thought that that's what the '0.' in front of the '17' meant. > > No, it's more - "If you want to ensure that bugs get fixed, use CVS." I > > can't quite fix bugs that don't ever happen to me and aren't reported. > > If people don't test CVS, then they're not going to report bugs until a > > release is made. > > And I do run and test from CVS, and so do many others, but many more run > from binary packages, and we want their testing too. That's all. And we're getting their reports - they just have to wait for the next release to see the fruits of their testing, is all. Isaac _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
