commit SimRel change

RELEASE.md

@@ -130,7 +130,8 @@ The actual steps to release
       - This will trigger the [Repository Validator](https://ci.eclipse.org/releng/view/Publish%20to%20Maven/job/RepositoryValidator/) job which will then trigger [Publish JDT to Maven](https://ci.eclipse.org/releng/view/Publish%20to%20Maven/job/PublishJDTtoMaven/), [Publish PDE to Maven](https://ci.eclipse.org/releng/view/Publish%20to%20Maven/job/PublishPDEToMaven/) and [Publish Platform to Maven](https://ci.eclipse.org/releng/view/Publish%20to%20Maven/job/PublishPlatformToMaven/).
     - Once the three publish jobs complete successfully log into https://oss.sonatype.org/#stagingRepositories and close the Platform, JDT and PDE repositories.
       - If you do not have an account on oss.sonatype.org for performing the rest of the release request one by creating an issue like https://issues.sonatype.org/browse/OSSRH-43870 to get permissions for platform, JDT and PDE projects and tag an existing release engineer to give approval.
-  * **Contribute to Simrel**
+  * **Contribute to SimRel**
+    - If SimRel is not updated before the I-builds are cleaned up (specifically the build for RC2/GA) it will break. 
 
 **Wednesday**  
 The release is scheduled for 10AM EST. Typically the jobs are scheduled beforehand and run automatically.