In general we try to run syncs every 2 weeks. Sometimes if there's known issues or other activities going on it can stretch out to a month or so between syncs.
If you'd like a package to be in the next sync, please make an effort to push it out as soon as it's ready such that it will get soak time in the testing repository before being deployed.
The goal of having the periodic syncs from testing to main is that the code gets time to be tested. So we don't want the sync announcements to trigger a flurry of releases. As such as soon as we start preparing for a sync optimally there would be no new packages released except for fixes to regressions identified in testing. We generally don't enforce this, but practice this for core packages doing our best to make new releases shortly after syncs to give as much testing time as possible before the full public release.
---
[Visit Topic](
https://discourse.ros.org/t/preparing-for-indigo-sync-2-in-2017-06/1953/2) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)