Closed GoogleCodeExporter closed 9 years ago
I propose:
* latestVersion -> stableVersion
* lastVersion -> bleedingEdge
Updated mczs attached
Original comment by sean.p.d...@gmail.com
on 17 Aug 2010 at 8:31
Attachments:
Sounds good to me ... I have updated the tutorial to use the new protocol ... I
plan to defer deprecation until post-1.0, just to avoid potential noise ...
Running tests and plan to release this as part of 1.0-beta.27.4
Original comment by henrichs...@gmail.com
on 30 Aug 2010 at 8:01
Excellent!
Original comment by alexandr...@gmail.com
on 30 Aug 2010 at 8:24
Name: Metacello-Core-DaleHenrichs.365
Author: DaleHenrichs
Time: 08/30/2010, 13:27:40
UUID: d718a09d-2a5b-4e27-8699-62e1acbcefbd
Ancestors: Metacello-Core-DaleHenrichs.364, Metacello-Core-SeanDeNigris.364
Name: ConfigurationOfMetacello-DaleHenrichs.338
Author: DaleHenrichs
Time: 08/30/2010, 13:31:57
UUID: 096fe968-68fc-436f-b32c-9cd4f1dd012b
Ancestors: ConfigurationOfMetacello-DaleHenrichs.337
Original comment by henrichs...@gmail.com
on 30 Aug 2010 at 8:32
After playing with this, it seems that there are 3 options:
1. load the latest stable version based on the blessing - #stableVersion
2. load the latest version, regardless of blessing -> #bleedingEdge
3. load the latest version of each package, regardless of whether there's a
version method mentioning them -> (ConfigurationOfXxx project version:
'x.x-baseline') load
Is that correct? And, is #2 really the "bleeding edge," or is #3? I'm unclear
on the difference in use case for #2 and #3.
Thanks.
Sean
Original comment by sean.p.d...@gmail.com
on 7 Sep 2010 at 8:41
bulk verify
Original comment by henrichs...@gmail.com
on 18 Apr 2011 at 5:32
Original issue reported on code.google.com by
alexandr...@gmail.com
on 12 Aug 2010 at 9:42