Update TaggerType Enum

To prepare a larger MR in Phys/ we need an updated version of the TaggerType enum. Ping @bkhanji @sakar @vibattis

We mistakenly used the dev-flavtag-master and dev-flavtag-update branches for further development, so these should not be used anymore.

Why is this WIP? Any reason why it can't be applied straightaway?

If you want to suppress use of dev-flavtag-master and dev-flavtag-update branches, why don't we just delete them from the repository?

Just for my understanding, I guess these changes will be needed also moving forward, so also in master and 2018-patches branches? If so I will cherry pick also to those branches when this MR is merged.

True, the WIP tag is probably too protective.

We still need to keep the dev-flavtag-X branches because we are referencing those in some git lb-checkout manuals. I'll delete these branches as soon as all manuals have been updated.

Yes these changes should propagate to master and 2018-patches at some point. I was not aware that you would need to cherry-pick these changes manually. If you prefer to merge this into master and the commits will still end up in 2017-patches, I can also open an MR into master. Otherwise I will remove the WIP tag.

unmarked as a Work In Progress

I've removed the WIP. In fact the propagation 2017-patches to master is semi-automatic, then manual to 2018-patches. I'll deal with both once this is merged (probably tomorrow if there are no issues in the nightly)

Ok, thanks a lot!

• [2017-11-10 00:04] Validation started with lhcb-2017-patches#199

merged

mentioned in commit e916da37

mentioned in merge request !946 (merged)

mentioned in commit 4cac9d42

mentioned in merge request !947 (merged)

mentioned in commit f34d647a

mentioned in commit e2503d86