All, as I was working on APEX-131 (integrate Travis CI) Thomas recommended I push to the `devel-3` branch rather than master (which I did). My only question, and wanted to raise it here for everyone, is what is the intended workflow going to be for contributors moving forward when submitting PR’s? Will pushing to the `devel-3` branch be standard?
I only ask because, as the community grows, I have a feeling that its going to create a lot of confusion and headache for new contributors to remember to target the `devel-3` branch rather than `master`. I’m assuming the `devel-3` branch is for all 3.x development and we’re back porting issues into `master` as necessary with large merges from `devel-3` into `master` at each RC (again, assuming). Like I said, just wondering for my own edification as this is a workflow I’m not too familiar with. Can someone explain what I’m missing? This also will help me with APEX-137 (dedicated page to apex site on how to contribute). Thanks! ________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. ________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
