Dear all, TO CONFIRM - THE FORTHCOMING RELEASE OF NUKE 8.0v3 WILL REINSTATE WINDOWS API COMPATIBILITY WITH 8.0v1.
We've bolstered our systems and release checks so the API breakage which occurred in 8.0v2 (Windows only) should not happen again. Many thanks Simon Pickles Nuke Engineer On 5 February 2014 16:10, Simon Pickles <[email protected]> wrote: > Dear all, > > Please accept our apologies for the inconvenience caused by the API > breakage in 8.0v2 on Windows. It is 100% our policy to ensure API > compatibility between v-releases. > > *API breakage in 8.0v2* > This is a serious issue and we are investigating why our release checks > did not pick this up. We work hard to ensure that issues like this do not > arise, and are disappointed that this has slipped through the net. Our > current plan is to revert to 8.0v1 compatibility for 8.0v3, which we hope > to release within the next two weeks. > > Whilst we appreciate this may cause further inconvenience for some of you, > we feel it is better to correct this error as soon as possible. Please let > us know if you would prefer this or if it would cause you problems. > > *7.0v5* > There was a serious flaw in the memory system update in Nuke 7.0v1. It > was vital that this issue was fixed during the bug fix cycle. Although this > required an addition to the API, it did not break API compatibility. It > still allowed previously built plugins to continue to function although > still subject to the original bug. > > All Foundry plugins were patched for this issue in 7.0v5. The changes > were documented in the Developer Notes section of the release notes for > 7.0v5 (see the note under Bug Fixes). > > Any comments are very welcome. > > Regards > > > Simon Pickles > Nuke Engineer >
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
