These helpful hints will make sure that your update sites are friendly with Pulse and all Eclipse users.
Maintain at least one previous version on your site:
By keeping around one old version of your software on your site, you give users the option of rolling back if a new release breaks something unexpectedly (not that this would ever happen of course!). The older version also helps in that Pulse users who may be in the middle of downloading software or who choose not to immediately upgrade can still access your old software reliably too.
Use operating system filters in features and manifests:
When defining your software, be sure to use the appropriate operating system filters available in the feature.xml as well as MANIFEST.MF to ensure that Eclipse and Pulse can determine automatically what software is applicable to what operating system. When you do have OS-specific content, put it in an OS-specific bundle or fragment to avoid downloading on other platforms.
Let the delivery software handle dependencies:
If you need particular software to be present within the target Eclipse, make sure you specify the appropriate dependencies. To ensure a very clean experience, reference the required features you prefer to have (such as platform, JDT, etc.) from your own features ensuring your target installs have exactly the software you want! The reason for dependencies is to let us do the heavy lifting for you!
Hopefully these hints will keep everyone up to date and running smooth!