Done.On Wed, Mar 30, 2016 at 11:30 AM Tully Foote <tfoote@osrfoundation.org> wrote:Hi Ruben,Thanks we'll go ahead and do that. If you could give @wjwwood or @tfoote access to the release repo https://github.com/smits/orocos-kdl-release we can push to the same location so we won't have to switch urls in the future.TullyOn Wed, Mar 30, 2016 at 2:12 AM, Ruben Smits via ros-release <ros-release@lists.ros.org> wrote:Hi Will,Sorry for not getting back to you sooner. For me it's fine to release the Jade version into Kinetic, I only have a ABI compatible bugfix pending, so that can happen later.R.On Wed, Mar 30, 2016 at 2:41 AM William Woodall via ros-release <ros-release@lists.ros.org> wrote:We're waiting on the refactor of tf2 (geometry_experimental -> geometry2 (I think)) to be finished, or at least the things that need to be done before releasing it the first time. If we get those done and orocos KDL stuff has not been released, then we can consider releasing the Jade version as is into Kinetic so we can also release all of the geometry repositories. We've open an issue against orocos KDL and sent private communications as well:On Tue, Mar 29, 2016 at 5:38 PM, Jon Binney via ros-release <ros-release@lists.ros.org> wrote: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?JonOn Wed, Mar 23, 2016 at 2:17 PM, Dirk Thomas via ros-release <ros-release@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_msgsar_track_alvar_msgsasync_web_server_cppaudio_commonbflcamera_info_manager_pycartesian_msgscontrol_msgsconvex_decompositioncram_3rdpartycsmcv_backportscv_cameradepthimage_to_laserscandynpick_driverecl_toolsectoeuslispexecutive_smachfiltersgraph_msgshumanoid_msgsiai_common_msgsimage_transport_pluginsiot_bridgeivconjsk_common_msgskeyboardkorg_nanokontrollaser_procleap_motionlibccdlibg2olibrmslms1xxlog4cpplyap_controlm4atx_battery_monitormarti_messagesmav_commmavlinkmd49_base_controllermedia_exportmongo_cxx_drivermoveit_resourcesnao_interactionnao_meshesnaoqi_bridge_msgsnaoqi_libqinavigation_msgsnerian_sp1nmea_msgsntpd_driverobject_recognition_msgsobject_recognition_rendereroctomapoctomap_msgsomplopen_kartoopencv_candidateopenni2_cameraopenni_cameraopenrtm_aistopenrtm_aist_pythonopenslam_gmappingorocos_kinematics_dynamicspcl_msgspepper_meshespocketsphinxpower_msgspr2_mechanism_msgspugixmlpython_ethernet_rmppython_qt_bindingrail_manipulation_msgsrail_mapsrail_user_queue_managerrandom_numbersrealtime_toolsrfsmrmp_msgsros_emacs_utilsrosauthrosdoc_literosh_corerospeexrospy_message_converterrtabmaprtctreertsprofilerttrwt_config_generatorsbplscreen_grabserialshape_toolssicktoolboxsmart_battery_msgssophussrdfdomstagetwist_mux_msgsueyeueye_camunique_identifierurg_cusb_camuwsim_bulletuwsim_osgoceanuwsim_osgworksvispvrpnwarehouse_rosxacroyoubot_driverCheers,- DirkOn Wed, Mar 23, 2016 at 1:46 PM, Jackie Kay via ros-release <ros-release@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: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 reposThe 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@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
--_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
--Ruben Smits, Roboticist - Founder+32 479 511 786Intermodalics - Gaston Geenslaan 9, 3001 Heverlee - BELGIUM
_______________________________________________
ros-release mailing list
ros-release@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-release
--Ruben Smits, Roboticist - Founder+32 479 511 786Intermodalics - Gaston Geenslaan 9, 3001 Heverlee - BELGIUM