Add new comment

Posted on by Oyunokata (not verified).

You say that moved to this model and away from git-flow because "We were drawn to this model because of the level of control it gives us over what we do and do not include in a given release, and it ties in well with our use of Jira for issue tracking"

Just curious as to how git-flow did not provide this functionality and control. We are using git-flow and Jira at my company and I have not had any issues of this sort. Can you please elaborate?

How to bug fixes (not hotfixes) get incorporated. Are bugs treated the same as features? If someone is in the middle of a feature and finds that they need a certain bug fix how are you handling this? Cherry-picking? merge, integrate, re-branch?

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.