Pharo Issue Tracker - FogBugz (Case [Issue]20004) Kernel - SnapshotDone should be not announced on every image startup or should be after all startup actions

FogBugz Notification

	Denis Kudryashov edited Case 20004: SnapshotDone should be not announced on every image startup or should be after all startup actions: Bug in Kernel: 1. Pharo Image • You are subscribed to this case

After opening issue I see that SnapshotDone have state isNewImage. But there are no users of it while there are subscribers (Epicea).
So I am not sure about this case.

Also question: is it right to announce this event before any start up action. In this state (just after image start) system can be not in valid state, something important to subscribers can be not initialized yet.
So probably we should announce it after new session started when every startup action is done and system is ready.
I changed title of case to mention it.

Title changed:
SnapshotDone should be not announced on every image startup

SnapshotDone should be not announced on every image startup or should be after all startup actions

	Priority: 5 – Fix If Time		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo6.0

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want FogBugz notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker