I propose that we leave the 2.4 release locked in at Celery 3.1.9. I don't think that Celery bug will be on any code paths, and we can upgrade and test the latest with the 2.4.1 release. What do you think about that?
-Brian ----- Original Message ----- From: "Randy Barlow" <[email protected]> To: [email protected] Sent: Monday, March 24, 2014 9:42:06 AM Subject: [Pulp-list] [devel] Celery 3.1.10 Released Celery 3.1.10 was recently released[0]. Should we upgrade (from 3.1.9), or is it too late in the development cycle? Upgrading would require also upgrading to Kombu 3.0.14 (we're at 3.0.13.) I've read the release notes, and nothing sounds critical for our use of Celery. There is one note that might be interesting about Task.retry() ignoring its queue argument. I don't believe that we explicitly call Task.retry(), but I wonder if Celery uses that for any autoretry behaviors that might happen. If so, that might be important for us since our queues are used for resource locking. [0] http://docs.celeryproject.org/en/latest/changelog.html#version-3-1-10 -- Randy Barlow Raleigh, NC, USA _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
