On Thu, Feb 24, 2005 at 05:18:04AM -0500, Donavan Stanley wrote:
> We all understand the "best pratices" of corporate software
> development, we're all professional programmers. The more rigid
> proceedures get put into place, the lesslike a hobby and more like
> work it becomes. And for every developer we'd gain under the new
> system we'd lose two more because it wasn't a fun project to work on.
I would hope that the two most common suggestions here would not make
the project any less fun.
a) There's a period of about 1-2 weeks every few months between
release candidate and release where new features are not checked in,
only fixes
and/or
b) Somebody trusted steps up to the plate to be a release handler who
volunteers to move any significant bug fixes from post release into
the release branch, and works with the binary packagers to get
these fixes into those packages. Also works with them to make
release candidate binary packages.
The only burden this places on me as a coder is the short period where
I can't check in my hot new feature. And of course the need for somebody
to volunteer to be that release handler. If nobody wants to do that, the
question is moot. That is a task not for somebody just coding for the
joy of coding, but instead for the desire to get their work used by lots
of users. There are, as we know, both types of folks out there.
There is a magic point of balance somewhere that makes the project the
most fun for everybody participating. It's not at ignoring the users --
you want their testing and their feedback and some developers want their
appreciation etc. And it's not at following a commercial software
production schedule. It's somewhere in the middle.
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
