Vadim Belman

It already feels like too many roles, but 'release manager' is actually two roles: 'Rakudo release manager' and 'Raku language release manager'. Otherwise feels right but dangerously bureaucratic... > *...

As far as I know, `-dev` mailing list is pretty much not used anymore. Therefore this channel might not work as expected. Possible variants for this are: 1. Re-vivify the...

Following a [IRC note](https://colabti.org/irclogger/irclogger_log/perl6-dev?date=2019-08-27#l105). problem-solving is not reliable enough. Discussion/approval here and actual merge/commit are somewhat different events. Also, sometimes approvals are obtained by other means like IRC as the...

The question about `RAKUDOLIB` arises time after time. The support for the variable is in the code. But it's role and future are vague. @patrickbkr says it should be deprecated....

Quick `greppabale` over ecosystem brought up 5 modules for `:P5` and one entry in documentation for `:Perl5`. Those should not be a big deal to be fixed with Raku regexes....

For the record: [related IRC discussion](https://colabti.org/irclogger/irclogger_log/raku-dev?date=2019-11-26#l391). Looks like a vote to me...

@taboege a quick look into Raku `Grammar` tells me that `:p5` is being handled by `P5Regex` slang. So, I actually see no problem in plugging in whatever is desirable as...

@niner As it was said, we would keep support for older revisions. Newer ones can have it through a third-party module. This way back-compat would be kept up until we...

Ok, my personal bottom line for this would be: `:P5` stay intact, but we must document what compatibility does it provide explicitly so as to not produce extra expectations. It...

So, we actually facing two options here: either a hard decision of removing `P5` from `6.c` and `6.d` specs; or marking all `P5` roast tests as `TODO` hoping for future...