Develop a simple tool for publishing package feeds; this will have two main functions: 1) Publish only the packages that have materially changed 2) Ensure the indexes are up-to-date We may also want to consider the problem of packages being produced where version the version hasn't changed but the contents has (this would be an error situation since the package manager won't do an upgrade).
Presumably this won't make M1. Randy, will you be able to deal with this for M2?
(In reply to comment #1) > Presumably this won't make M1. Randy, will you be able to deal with this > for M2? Yes. I expected to have the first part finished last week. But some assumptions the package_manager.py indexing code means I'll probably have to refactor some of it.
I've split out the "reducing package feed churn" issue to bug 8318 since it's no longer an integral part of the publishing tool.
This is mostly finished now that the "package diffing" is actually done as part of the build. I need to revisit and make sure that nothing has regressed and submit.
So I think the important part of this is now under bug 8318 which is already scheduled for 2.1; I'm downgrading this bug's priority and moving it to 2.1 as well.
We have a variety of package workflows and automated tests but there's no need for this particular workflow.