Add new comment

Posted on by Steve Martini (not verified).

Hi Katherine,

You mention you were drawn to the BPF model because of the level of control it gives you regarding what you do and do not include in a given release, and it ties in well with your use of Jira for issue tracking. Were these the reasons why git-flow did not suit your workflow, or were there other reasons why git-flow was not right for you?

Was there some apprehension when you started using the BPF model about merging into the QA branch and not running automated tests?

Do you feel like you've given up any capabilities moving away from git-flow or added any unexpected consequences?

Thanks

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.