[ros-release] check_blocking_repos script

[Jon Binney]

Right now the packages I want to release are blocked by not having TF
released yet, which in turn is blocked by not having the orocos KDL
packages released. If those can be released, a lot of others should follow
quickly. Does anyone know the status of those packages?

Jon

On Wed, Mar 23, 2016 at 2:17 PM, Dirk Thomas via ros-release <
ros-release at lists.ros.org> wrote:

> And for completeness the the following repositories can be release into
> Kinetic "now". If you are the maintainer of one / some of them please
> consider making a bloom release for Kinetic rather sooner then later. Thank
> you!
>
> ackermann_msgs
> ar_track_alvar_msgs
> async_web_server_cpp
> audio_common
> bfl
> camera_info_manager_py
> cartesian_msgs
> control_msgs
> convex_decomposition
> cram_3rdparty
> csm
> cv_backports
> cv_camera
> depthimage_to_laserscan
> dynpick_driver
> ecl_tools
> ecto
> euslisp
> executive_smach
> filters
> graph_msgs
> humanoid_msgs
> iai_common_msgs
> image_transport_plugins
> iot_bridge
> ivcon
> jsk_common_msgs
> keyboard
> korg_nanokontrol
> laser_proc
> leap_motion
> libccd
> libg2o
> librms
> lms1xx
> log4cpp
> lyap_control
> m4atx_battery_monitor
> marti_messages
> mav_comm
> mavlink
> md49_base_controller
> media_export
> mongo_cxx_driver
> moveit_resources
> nao_interaction
> nao_meshes
> naoqi_bridge_msgs
> naoqi_libqi
> navigation_msgs
> nerian_sp1
> nmea_msgs
> ntpd_driver
> object_recognition_msgs
> object_recognition_renderer
> octomap
> octomap_msgs
> ompl
> open_karto
> opencv_candidate
> openni2_camera
> openni_camera
> openrtm_aist
> openrtm_aist_python
> openslam_gmapping
> orocos_kinematics_dynamics
> pcl_msgs
> pepper_meshes
> pocketsphinx
> power_msgs
> pr2_mechanism_msgs
> pugixml
> python_ethernet_rmp
> python_qt_binding
> rail_manipulation_msgs
> rail_maps
> rail_user_queue_manager
> random_numbers
> realtime_tools
> rfsm
> rmp_msgs
> ros_emacs_utils
> rosauth
> rosdoc_lite
> rosh_core
> rospeex
> rospy_message_converter
> rtabmap
> rtctree
> rtsprofile
> rtt
> rwt_config_generator
> sbpl
> screen_grab
> serial
> shape_tools
> sicktoolbox
> smart_battery_msgs
> sophus
> srdfdom
> stage
> twist_mux_msgs
> ueye
> ueye_cam
> unique_identifier
> urg_c
> usb_cam
> uwsim_bullet
> uwsim_osgocean
> uwsim_osgworks
> visp
> vrpn
> warehouse_ros
> xacro
> youbot_driver
>
> Cheers,
> - Dirk
>
>
> On Wed, Mar 23, 2016 at 1:46 PM, Jackie Kay via ros-release <
> ros-release at lists.ros.org> wrote:
>
>> Good afternoon,
>>
>> I'd like to announce a script to help identify repositories that haven't
>> been released into an upcoming new ROS distribution that are blocking your
>> release.
>>
>> You can get it by cloning ros/rosdistro and looking in the scripts
>> directory.
>>
>>
>> https://github.com/ros/rosdistro/blob/master/scripts/check_blocking_repos.py
>>
>> Or you can simply wget the raw script:
>>
>> wget
>> https://raw.githubusercontent.com/ros/rosdistro/master/scripts/check_blocking_repos.py
>>
>> Right now the output is fairly minimal. For a set of input repository
>> names, it will tell you:
>>
>> - repos that have already been released into Kinetic
>> - repos that are unreleased and are blocked by other unreleased
>> packages/repos
>> - repos that are unreleased and are ready to be released, but do not
>> block other repos
>> - repos that are unreleased, are ready to be released, and are blocking
>> other repos
>>
>> The default set of inputs is all repositories that were released in the
>> last distribution (jade).
>>
>> The default dependency tree is determined by the dependencies in the last
>> distribution. So if your dependencies changed in Kinetic the output of this
>> tool will not reflect that.
>>
>> I like to run it with "python -i" to drop into the Python interactive
>> shell to further inspect the data sorted by the script.
>>
>> Future enhancements may include: aggregating the number of releases
>> blocked by a particular unreleased repo, printing the email addresses of
>> maintainers of repositories, drawing a tree structure.
>>
>> Recent output tells me that there are currently 74 repos ready for
>> release that are blocking other repos, and 186 repos that cannot be
>> released because of unreleased dependencies.
>>
>> Happy releasing,
>>
>> Jackie
>>
>> _______________________________________________
>> ros-release mailing list
>> ros-release at lists.ros.org
>> http://lists.ros.org/mailman/listinfo/ros-release
>>
>>
>
> _______________________________________________
> ros-release mailing list
> ros-release at lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-release
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20160329/cc6ecca7/attachment.html>