I suggest to introduce an additional milestone (e.g. milestone/ready) with optional dependencies on all "system" services, roughly matching the time when rc3 is run.
By convention, all non-system services would be (strongly) recommended to depend upon this service. This would also make application specific services more rubust. I've seen a couple of examples where SMFs would, depend upon filesystem/local and network/physical, but fail if the user configured the application to use an NFS mountpoint, for instance. This would also facilitate the introduction of additional services which are a requirement for all applications in the general case. In the current context, this milestone (and the requirement for all user apps to depend upon it) would provide a way to make sure patching is done at the right time. Does this help? Nils
