Before today, Case 11908 "Need to show warning when no .changes file found" was tagged
Milestone=Pharo3.0
Priority=2-Really-Important

Case 12885 "Fix ChangesFileLoaderTest to not use FileSystemForTesting" tagged
Milestone=Pharo4.0
Priority=4-Would-be-nice
today changed status to "Fix Review Needed" thanks to Guille, Pablo and Martin.
I was going to try doing a review but philosophically my limited time would be better spent on Pharo3.0 milestones.

More importantly, Case 12885 was added as a subcase of 11908 and at the same time the 11908 Milestone changed to Pharo4.0. Was that intentional? Or an artifact of Fogbugz rules ? (which does make sense that a parent cant be delivered before a dependent subcase is fixed).

cheers, Ben