Reactie toevoegen

Posted on by David_Rothstein (niet gecontroleerd).

Thanks!

Hm, I assumed that whenever a hotfix goes out, a new QA branch would be generated in response to that directly. I see what you are saying about developers committing code to a feature branch after it was merged in, though. (Although if the last feature to be merged in is the one where someone does that, it seems like you'd miss it anyway.)

I think in our case, it would not be too likely for developers to do that since we'd be planning to do as much QA as possible on the feature branch itself (and only use the actual QA branch for "final" QA, sanity checking, making sure all the features play nicely together, etc). This means than when a feature is merged in, the ticket in which it was implemented would have its status changed to something approximating "closed". So the developer would hopefully know they were doing something wrong by continuing to work on a closed ticket :)

Plain text

  • Geen HTML toegestaan.
  • Adressen van webpagina's en e-mailadressen worden automatisch naar links omgezet.
  • Regels en alinea's worden automatisch gesplitst.

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.
  • Adressen van webpagina's en e-mailadressen worden automatisch naar links omgezet.
  • Toegelaten HTML-tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Regels en alinea's worden automatisch gesplitst.
Bij het indienen van dit fomulier gaat u akkoord met het privacybeleid van Mollom.