Issue 150 in metacello: #stable version shouldn't cause upgrade from project reference

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium Product-Core

New issue 150 by [hidden email]: #stable version shouldn't cause  
upgrade from project reference
http://code.google.com/p/metacello/issues/detail?id=150

a project reference of #stable, should only cause load activity when the  
target project is not present ... if the target project is present no  
upgrade should take place (it does presently)

A direct load of a #stable version should always load the specified  
version...

Project references have always been subject to the version comparison rule  
where the project is a) never downgraded and b) only upgraded if the  
specification is for a later version.

#stable implies an even looser coupling to the specified project, so I  
think it makes sense that a #stable project reference will only cause a  
version to be loaded if the project is not already loaded into the image

Updates:
        Labels: Milestone-1.0-beta.31.2

Comment #1 on issue 150 by [hidden email]: #stable version shouldn't  
cause upgrade from project reference
http://code.google.com/p/metacello/issues/detail?id=150

proposed fix in Metacello 1.0-beta.31.2 (dkh.655)

Updates:
        Labels: -Milestone-1.0-beta.31.2 Milestone-1.0-beta.32

Comment #2 on issue 150 by [hidden email]: #stable version shouldn't  
cause upgrade from project reference
http://code.google.com/p/metacello/issues/detail?id=150

(No comment was entered for this change.)

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

Comment #3 on issue 150 by [hidden email]: #stable version shouldn't  
cause upgrade from project reference
http://code.google.com/p/metacello/issues/detail?id=150

fixed earlier in Metacello 1.0-beta.31.2 (dkh.655)