flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harbs <harbs.li...@gmail.com>
Subject Feature Branches (was Re: TLF Branch merged back)
Date Mon, 03 Jul 2017 15:26:21 GMT
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 REALLY
suck. I discovered today that Chrome introduced a new bug where an opaque background is drawn
on nested SVG elements which have a blend-mode applied.) Anyway, it’s a new feature, but
VERY unlikely to break anything. Should that go into a separate branch or should I not bother?

My preference is to only bother with feature branches for changes that have a decent chance
of breaking things. I don’t really care about naming convetions, but naming a branch with
a JIRA id for cross-referencing JIRA fixes makes sense.


> On Jul 3, 2017, at 4:29 PM, piotrz <piotrzarzycki21@gmail.com> wrote:
> Harbs,
> In case of your TLF my thoughts was always that it would be good if we will
> have it in develop, cause you are fixing a lot of things not only related to
> TLF. - Personally I don't have anything against that you are putting all to
> develop.
> But if someone is going to do some other feature - it would be good to have
> jira + separate branch placed in feature folder, as I did it with
> DropDownList for MDL.
> That is mine view.
> Thanks for merge!
> Piotr
> -----
> Apache Flex PMC
> piotrzarzycki21@gmail.com
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-Branch-merged-back-tp62779p62780.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

View raw message