What criteria mark the closure of perl6 specification

[Richard Hainsworth]

When does the specification of perl6 come to an end? Are there criteria 
or milestones which define that the perl6 specification stage is at an end?

I can see that setting a time line is not easy because the effort is 
volunteer based, but what about a "conceptual" end?

Perhaps there could be a perl6.0 specification, with further changes 
(syntactic sugar, new operators, renaming operators, etc) being 
assigned/incorporated into a perl6.1 specification, etc.

I ask because I want to use perl6 for real things. Which means I need 
the help of tutorials and existing code to see how to use the richness 
of the language for the things I want, and to be able to use existing 
perl5 CPAN modules. For I am not a guru or lambdacamel, who can grok the 
C and Haskell and make things work that dont. But while perl6 continues 
its evolution, without a tangible end, few are going to dedicate time 
and effort to write documentation for such as me. (eg. How out of date 
are the Exegesis files?)

pugs is great, so far as it goes (only the simplest perl5 modules can be 
accessed and sometimes only in a roundabout way - I've written a simple 
test that kills pugs dead, which arose when I tried to use a perl5 module).

While perl6 remains unstable in its specification (or is perceived to be 
that way) and is looking (from outside a select group?) like a unending 
road, wont this act as a deterrent to those who want to help hack it 
into existence, usefulness and stability?

Richard