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 them before they get merged. As long as folks make decisions based on their impact to the community, and are quick to pull out something that isn't right, we should have to make feature branches a requirement. My 2 cents, -Alex On 7/3/17, 8:17 AM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >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 building >framework >code + examples. > >Piotr > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FTLF-Branch-merged-back-tp62779p62782 >.html&data=02%7C01%7C%7C1555d87302be43f90aae08d4c229204c%7Cfa7b1b5a7b34438 >794aed2c178decee1%7C0%7C0%7C636346929274582640&sdata=ksjt2OAn9ShjxBtqMwYwY >bA8wm1QykQE3PBywtIvWg4%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
