<div dir="ltr">Hi Georg, <div><br></div><div>We have been encouraging everyone to make sure to release for them and pushing maintainers to do their best to support them. But so far we've been holding back from making them required. </div><div><br></div><div>Now that we've seen that Jessie is close enough that almost every package is actually already compatible I think we could consider adding it as to the required list. </div><div><br></div><div>For the architectures we haven't called them out at this level, since the packaging is generally supposed to be architecture independent. The only time we have failures is when people embed binaries inside their packages. A common cause of that is a hardware vendor blob driver. </div><div><br></div><div>Tully</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 21, 2016 at 12:56 AM, Georg Bartels via ros-release <span dir="ltr"><<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Jackie,<br>
<br>
regarding "armhf, arm64, and Debian Jessie": Are those now required
target platforms for Kinetic? They are not listed here:<br>
<br>
<a href="http://www.ros.org/reps/rep-0003.html#kinetic-kame-may-2016-may-2021" target="_blank">http://www.ros.org/reps/rep-0003.html#kinetic-kame-may-2016-may-2021</a><br>
<br>
Cheers,<br>
Georg.<div><div class="h5"><br>
<br>
<br>
<br>
<div>On 12.04.2016 03:41, Jackie Kay via
ros-release wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div>
<div><b>tl;dr</b>: April 25th is the deadline for
desktop-full. Fix your failing jobs on the farm or ask us
to disable them. Check your repo's status on <a href="http://54.183.65.232/status_page/blocked_releases/blocked_releases_kinetic.html" target="_blank"></a><a href="http://54.183.65.232/status_page/blocked_releases/blocked_releases_kinetic.html" target="_blank">http://54.183.65.232/status_page/blocked_releases/blocked_releases_kinetic.html</a></div>
<div><b><br>
Release Deadline</b><br>
</div>
<div>Today's update is brought to you by the metapackage
"desktop-full".<br>
<br>
</div>
<div>desktop-full consists of the metapackages "desktop",
"perception", and "simulators".<br>
<br>
</div>
<div>After desktop-full is released into Kinetic, we can
consider ourselves in beta for Kinetic.<br>
<br>
</div>
<div>I would like to establish a deadline of April 25th for
releasing desktop-full.<br>
<br>
</div>
<div>Here are the remaining packages that need to be
released:<br>
</div>
<div><br>
</div>
<div>
<div><a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.control_msgs" target="_blank">control_msgs</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.executive_smach" target="_blank">executive_smach</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.gazebo_ros_pkgs" target="_blank">gazebo_ros_pkgs</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.image_transport_plugins" target="_blank">image_transport_plugins</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.laser_pipeline" target="_blank">laser_pipeline</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.perception_pcl" target="_blank">perception_pcl</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.robot_state_publisher" target="_blank">robot_state_publisher</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.rqt_common_plugins" target="_blank">rqt_common_plugins</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.rqt_robot_plugins" target="_blank">rqt_robot_plugins</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.stage_ros" target="_blank">stage_ros</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.urdf_tutorial" target="_blank">urdf_tutorial</a><br>
<a href="http://54.183.65.232/status_page/blocked_releases_kinetic.html?q=.visualization_tutorials" target="_blank">visualization_tutorials</a></div>
</div>
<br>
<div>Maintainers of these packages (this includes me), let's
get moving. If we released 1 package per day, we would
beat the deadline. It's important to release early so that
we can catch packaging errors on the farm.<br>
</div>
<div><br>
</div>
<div><b>armhf, arm64, and Debian Jessie</b><br>
</div>
<div>There are a lot of failing binary jobs on the farm
right now. I believe all of the failures are currently on
armhf/arm64 platforms, Debian Jessie, or both.<br>
<br>
</div>
<div>To the maintainers of packages with failing jobs (this
also includes me): <br>
<br>
</div>
<div>If your failing job is due to architectural differences
on ARM, please either address the problem or ask us to
disable the armhf/arm64 build for your repo.<br>
<br>
</div>
<div>If your failing job is due to missing package
dependencies in Jessie, please look into adding the
correct rosdep keys or adding a backport for missing
dependencies. We do not have a way to blacklist packages
in Debian only, but luckily these issues are usually
easier to identify and fix than architecture differences.<br>
<br>
</div>
<div>And if at some point your package fails on all
architectures and you don't make efforts to fix it, I will
blacklist it entirely because those emails are really
annoying to receive.<br>
<br>
</div>
<div><b>Blocked Repos Webpage<br>
</b></div>
<div>An intern at OSRF is working on a web interface for the
check_blocking_repos.py script announced on this list a
few weeks ago.<br>
<br>
</div>
<div>You can test it here:<br>
<a href="http://54.183.65.232/status_page/blocked_releases/blocked_releases_kinetic.html" target="_blank">http://54.183.65.232/status_page/blocked_releases/blocked_releases_kinetic.html</a><br>
<br>
</div>
<div>I encourage you to use it to figure out which packages
are blocking your package (or if you are blocking someone
else's packages).<br>
<br>
</div>
<div>It's still in review and has a few minor improvements
pending. If you find issues with it, you can report them
on <a href="https://github.com/ros-infrastructure/ros_buildfarm" target="_blank">https://github.com/ros-infrastructure/ros_buildfarm</a><br>
</div>
<div><br>
</div>
<div>Your ROS boss,<br>
</div>
<div><br>
</div>
<div>Jackie<br>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><span class=""><pre>_______________________________________________
ros-release mailing list
<a href="mailto:ros-release@lists.ros.org" target="_blank">ros-release@lists.ros.org</a>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a>
</pre>
</span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
ros-release mailing list<br>
<a href="mailto:ros-release@lists.ros.org">ros-release@lists.ros.org</a><br>
<a href="http://lists.ros.org/mailman/listinfo/ros-release" rel="noreferrer" target="_blank">http://lists.ros.org/mailman/listinfo/ros-release</a><br>
<br></blockquote></div><br></div>