On Tue, Apr 22, 2014 at 2:02 PM, Rich Mattes richmattes@gmail.com wrote:
On Tue, Apr 22, 2014 at 1:45 PM, Scott K Logan logans@cottsay.net wrote:
Rich -
We've got a lot of updates on QA right now, and I'm a little concerned that there may be untested combinations of versions in the dependency tree. I'm thinking we should wait until all of the updates have reached a week on QA and push them all to stable around the same time. What are your thoughts here?
A coordinated push sounds like a good plan. Every package has to spend at least a week in -testing if it doesn't get enough karma over that period, so we have to wait at least a week from when the newest update got pushed to -testing for the earliest coordination point. It looks like the newest update out of that list was submitted on April 18th, so how about we plan to push the packages the next Monday after a full week passes: April 28th?
I think the EL6 packages can be pushed on their own, but those have to wait two weeks in -testing. That being said, it looks like there's a bug in bodhi where it didn't reset the counter after I unpushed the update the first time (it left a comment saying that the update has been in -testing for 65 days when I fixed the broken deps and re-submitted to -testing.) Either way, I'll wait 14 days and push them on the 29th.
Rich
CCing the fedora-robotics list
Rich
On Tue, 2014-04-22 at 14:04 -0400, Rich Mattes wrote:
A coordinated push sounds like a good plan. Every package has to spend at least a week in -testing if it doesn't get enough karma over that period, so we have to wait at least a week from when the newest update got pushed to -testing for the earliest coordination point. It looks like the newest update out of that list was submitted on April 18th, so how about we plan to push the packages the next Monday after a full week passes: April 28th?
I generally combine all related packages into one bodhi update, like the gnome or kde teams. This ensures that there isn't a breakage and all required packages get to the repos simultaneously. (It's also simpler than tracking multiple bodhi updates.)
On Tue, Apr 22, 2014 at 9:39 PM, Ankur Sinha sanjay.ankur@gmail.com wrote:
I generally combine all related packages into one bodhi update, like the gnome or kde teams. This ensures that there isn't a breakage and all required packages get to the repos simultaneously. (It's also simpler than tracking multiple bodhi updates.)
I agree that this is the best way to do things. The updates in question
(which I edited out of the reply sent to the list) were all submitted by different people at different times:
Packages: - python-bloom - python-catkin_lint - python-catkin_pkg - python-rosdep - python-rospkg - pretty much all of the ROS packages on el6
I think that we can push all of those updates today if they haven't been pushed already, except for the el6 ones which I'll do tomorrow. I'll take care of it in a couple of hours if nobody beats me to it.
From here on out we can provide a heads-up on this list one of us plans on
doing a large block of updates so that we can all coordinate our efforts and try to group bodhi requests better.
Rich
On 04/28/2014 03:25 PM, Rich Mattes wrote:
I agree that this is the best way to do things. The updates in question (which I edited out of the reply sent to the list) were all submitted by different people at different times:
Packages:
- python-bloom
- python-catkin_lint
- python-catkin_pkg
- python-rosdep
- python-rospkg
- pretty much all of the ROS packages on el6
I think that we can push all of those updates today if they haven't been pushed already, except for the el6 ones which I'll do tomorrow. I'll take care of it in a couple of hours if nobody beats me to it.
From here on out we can provide a heads-up on this list one of us plans on doing a large block of updates so that we can all coordinate our efforts and try to group bodhi requests better.
I just finished pushing all of the f20 and f19 updates in the above list to stable. I'll do the el6 ones tomorrow.
Rich
robotics@lists.fedoraproject.org