I work out of head and I'm happy with not branching unless head is in a state that allows us to release. But what happens to changes that come in and actually throw us back again in our "time to release" ?
How do we define the feature freeze. You should not prevent people to write on new things only because some others want to release software. Where shall their code go to in the meantime. I think working off from a seperate repository and doing vendor imports of OpenACS is too much of a fuzz for most developers which is the reason why I think quite some of us still work out of OpenACS repository.
Again, personally I'm in for releasing the way we do and concentrating on bug fixing instead of new features once we have a feature freeze. But I would like to see ways for others that are not commited to release to continue working. After all, what happens if we fail to release quickly.
Unless we don't TIP this and get an agreement on what the steps are going to be when we release, we are stuck dead in the water. As Joel is the release manager it would be great if he could TIP whatever he thinks works out best and let the OCT vote on it. Then at least all of us know what is coming up, how do deal with it aso.
