As most of you are aware, the Gatekeepers have been attempting to focus the limited resources on the release of 1.4.0 and have put off additional work on some much sought after functionality until it was completed. We started issuing 1.4.0 release candidates in August and it is now October and we no longer believe that it is appropriate to put off new development.
Last night a new branch was cut off of "openafs-stable-1_4_x" with a tag name of "openafs-stable-1_4_0-branch" which will be used exclusively for finishing the 1.4.0 release process. The "openafs-stable-1_4_x" branch will continue to be used for on-going development of the 1.4.x series. The next release in this series will be 1.4.1. Two features we have committed to for 1.4.1 are Mac OSX 10.4.x (Tiger) support and Byte Range Locking support for Windows. Shortly after the new 1.4.0 branch was created, the Tiger and Byte Range Lock code was merged into the 1.4.x branch. If you have been waiting to work on Tiger support, now is your chance. The merge of the Tiger work with the mainline code more than likely broke things both in the Tiger support as well as on other platforms. If there is a choice to be made between testing 1.4.0 or testing the current 1.4.x, please test 1.4.0 so we can issue a final 1.4.0 release and move on with our lives. However, if you can test both, please start to test the contents of the 1.4.x branch. If you are interested in being involved with the testing for the Windows byte range lock support, please join the [EMAIL PROTECTED] mailing list. Discussions of the on-going work are taking place in that forum including announcements of installers including this support. Jeffrey Altman for the OpenAFS Gatekeepers
smime.p7s
Description: S/MIME Cryptographic Signature
