When we enable the usage on regexp on branches and tags to define fine-grained permissions on git repositories, the syntax of the regexp to use is not clear.

The documentation talks about regex and links the gitolite documentation that uses regular expressions. The sample provided just after uses glob expression (like when we don't use regular expressions).

If I use a regex in the rule expression, I can see, in the gitolite configuration file of the repository that the expression is converted by Tuleap from glob to regex: .*$ becomes ..*$.

We should not talk about regex if a glob is expected by Tuleap. The regex concept seems to only be a technical consideration. Functionally, with or without the "extended expressions" enabled, Tuleap seems to expect globs in both cases.

Furthermore, the usage of glob expressions restricts to a subset of the scope covered by regex expressions. This should be clear for the user that will wrote expressions.

So, either we chose to use glob and we shouldn't talk about regexp that may result on unwanted behaviors and open a non-existing larger functional scope. Either, we accept regex without modify them in background.