Le lundi 19 décembre 2011 à 21:24 +0400, Aleksey Bragin a écrit :
On 19.12.2011 21:02, Cameron Gutman wrote:
The only problem I have with delaying the release
is that we're getting more and more out of date with Wine and some great patches are
waiting on the release. My vote would be to branch now, run 0.3.14 tests on the branch,
then resume trunk development as if we had just released (Winesyncs, big patches, etc).
After the Mm bug is found, we can either rebranch 0.3.14 if trunk is stable or merge the
fix back and release the previous branch.
What's the point of branching then,
if it's going to be abandoned (you
didn't specify a scenario when the branch gets released)?
The same for many branches: having a snapshot of ReactOS state at a
revision.
So, if after the bug is fixed, but other stuff got broken due to sync,
patches, implementations, whatever, we can just backport the fix to the
branch and release 0.3.14 with the branch.
And if trunk is stable enough, then, we drop the branch, and start again
with something fresh.
So, I support this idea.
And once more: I don't agree with a release shipped with mshtml bug.