On 19 Jul 2016, at 11:56, Dean Troyer wrote:
> On Tue, Jul 19, 2016 at 12:27 PM, John Dickinson wrote:
>
>> Overall, using long-lived upstream feature branches has been very helpful
>> for us and overall a positive experience.
>>
>> I've seen some other teams debate and discuss
On Tue, Jul 19, 2016 at 12:27 PM, John Dickinson wrote:
> Overall, using long-lived upstream feature branches has been very helpful
> for us and overall a positive experience.
>
> I've seen some other teams debate and discuss using a feature branch for
> their work but wonder about
Swift has now used 4 feature branches and landed 3 of them:
* feature/sp -- for storage policy functionality (landed)
* feature/ec -- for erasure codes (landed)
* feature/hummingbird -- for golang WIP
* feature/crypto -- for at-rest encryption (landed)
Overall, using long-lived upstream