Depends on your use case: There are two reasonably complete and stable Perl6 implementations - Rakudo on Parrot and Niecza on .NET/Mono.
What needs to be addressed before Perl6 can be recommended for arbitrary production use are modules and performance:
The module ecosystem[1] is somewhat ad-hoc and modules may have bit-rotten, so batteries are not included.
Rakudo is more feature-complete, but performance is less-than-awesome and Niecza might be a better choice if that's relevant and you're comfortable with the CLR. The performance issue can be somewhat mitigated by implementing critical code in C (in case of Rakudo) or C# (in case of Niecza), but that's more of a band-aid than a real solution.
You might also want to take a look at the Perl6 advent calendar[2] to gain some insights into the current state of Perl6.
[2] http://perl6advent.wordpress.com/2012/12/01/perl-6-advent-ca...