Issue 171 in metacello: Critical Warning for missing versionString in baseline project reference

Status: Accepted
Owner: [hidden email]
Labels: Type-Feature Priority-Medium Product-Core Milestone-1.0-beta.32

New issue 171 by [hidden email]: Critical Warning for missing  
versionString in baseline project reference
http://code.google.com/p/metacello/issues/detail?id=171

Eventually, we will require a versionString in a project reference, so it  
is probably a good idea to add the critical warning now to get folks used  
to the idea:)

#noVersionSpecified warns of no version being specified in the version, but  
no specific warning has been defined for the baseline.

I suggest that we use #missingRecommendedProjectSpecField for the time  
being.

Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.32

Comment #1 on issue 171 by [hidden email]: Critical Warning for  
missing versionString in baseline project reference
http://code.google.com/p/metacello/issues/detail?id=171

fixed in Metacello 1.0-beta.32 (dkh.674)