On Sat, 2001-11-10 at 11:11, David Chart wrote: > I suggest we don't branch until 1.0 is out, so that the developers can't do > new features while they're supposed to be squashing bugs. Otherwise, I like
The new features are only added by those who have an itch. Having a branch that will lead to 1.0.x will allow those who have more kicks out of new features to work, while the rest of us concentrate on making 1.0.0 A ok on that branch. :) Forcing everyone on the same thing will not help the project at all. It is in the nature of free software development to hack our itches. If one's itch is a certain new feature, holding it off tree untill 1.0.0, then theres a probability that that person may eventually loose interest. Branching will allow those who care about the bugs to work on them without worrying about changes for post 1.0.0. It will also allow those who care about new features to work on them without worrying whether they will break the bug hunt, because it is in a different branch. This is not a division of the current work force. I think that we are mostly concerned about the bugs, right now. This is just a way to do things that will allow to do both things. If a person doesn't get a kick at solving bugs, it's not forcing him to fix bugs that will help the project! Hugs, rms -- + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Ghandi + So let's do it...?
msg19621/pgp00000.pgp
Description: PGP signature
