Thanks for the quick reply, Sebastian. Also, thanks for all your work on the UDT… it has come a long way from the early days of DNN. I was able to rollback my implementation, so I will wait for v3.5.1 to be released (hopefully, very soon!!).
I fully understand standard the need for a structured release process as I have been developing software for a long time. My point to the last post has nothing to do with what you call the next release, but points out the need to have an exception to the structured release process or an expedited release process... call it a hotfix, patch, v3.5.0.1, whatever... please consider the following:
- v3.5.0 is put through the release process and passes
- v3.5.0 is released to the community
- v3.5.0 is determined to have a major bug which is not caught during the release process
- One of two things should now happen (IMHO)
- v3.5.0 is pulled from distribution because it is not fully functional and shouldn’t have passed the release process
OR
- the code base for v3.5.0 is updated with ONLY the changes needed to fix the major flaw and an expedited release process is used to release the update (regardless of what it is called) in a matter of hours, not days or weeks.
Once again, thanks for what you do for this community and I will patiently await the update.