We're about to finalize the 1.6.5.2 release. The (or at least my) idea is that these 1.6.5.x releases should provide a timely resolution for current actual problems for which the 1.6.6 release would be too late. To allow releasing without a long public testing phase, the changes should obviously be kept to the minimum.
The changes currently foreseen to go into 1.6.5.2 are here: http://gerrit.openafs.org/#q,status:open+project:openafs+branch:openafs-stable-1_6_5_x,n,z Right now, these include support for OS X 10.9, a fix relevant for the RHEL 6.5 kernel, and a fix for tmpfs caches under Linux 3.1+ kernels. One open question is whether http://gerrit.openafs.org/#change,10457 (which in addition would require changes 10456, 10458, 10472 and 10518) can wait for 1.6.6. It's believed to be required for the client on Ubuntu 14.04, and that's the only known common use case right now. Does anyone know about other use cases for this set of changes? Can anyone familiar with the Ubuntu release process tell whether a 1.6.6 release in January or (hopefully not) February would be too late to make sure 14.04 will come with working AFS client packages? Thanks Stephan -- Stephan Wiesand DESY -DV- Platanenenallee 6 15738 Zeuthen, Germany _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
