Alex,
My view is that "jira + branch" is more concrete documentation than
discussion on dev list - It could be always wonderful addition.
Additionally making some things on feature branches is definitely for
committers who are more experience. I would not push such requirements who
just join us
Hi Piotr,
What is the advantage of this documentation?
IMO, we need to get as much work done with the resources we have.
Introducing more overhead for the most active committers doesn't help,
especially since I don't see a lot of folks switching over to these
feature branches to help validate the
I think pushing any kind of features through "jira + branch" has also some
documentation purposes, so even if you not breaking anything it is worth to
do this.
Second thing if you do exactly same branches for Compiler and typedefs you
will have it automatically in Maven build which generally build
I just looked at what you did there. Makes sense.
I think we should have some kind of consensus on what should be done in feature
branches and should there be some kind of naming convention for these branches.
For example, I’m writing some code for browser and version detection. (Browser
bugs R
