> I superficially agree that trunk is a better place to do larger and > potentially less stable changes, but I think the problem is that it seems > that trunk is too far away from the stable branch and it just seems more > productive to "iterate" on both in parallel rather than do a lot of > iterating on trunk and then have to recreate a long iteration sequence on > the stable branch. The faster code gets into the stable branch, the faster > and more thoroughly people will test it out. >
This is what i cant stand: its not the purpose of a stable branch. One way i can stop people from committing half-baked shit to the stable branch is to make release candidates without warning. One way you can stop me from making release candidates without warning is to not commit half-baked shit to the stable branch. This is really simple, and I will make zero compromises here. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
