Update label on Dynamic BuildGroups tab #2043
Conversation
|
Should this be merged into 3.3, given that we already have a few other things to get into that release? |
Yes. Merge to master first then backport, or vice versa? |
If we merge this into 3.3, we can then merge 3.3 into master quickly thereafter. The only time merging changes into the release branches is problematic is when those changes linger for months on end like what happened with the 3.2 release process. I've been trying to merge 3.3 into master every time I make a new release candidate, and I try to make a new release candidate at least weekly, which keeps master relatively up-to-date. |
Replace "build name contains" with "build name is" to more accurately reflect the functionality that was changed in
It was confusing to display this caption below the table it references.
zackgalbreath
force-pushed
the
update_dynamic_rules_label
branch
from
ea5c2f5 to
3f8a3a9
Compare
2 participants
No description provided.