Brent-A · thedewi · Oct 8, 2019 · Oct 9, 2019 · Oct 10, 2019 · Oct 10, 2019
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -0,0 +1,4 @@
+# Data science would like to know about all schema changes Engineering plan to make to SQL databases.  This automates the process and is intended to be used by Data Science as a FYI of an incoming change as opposed to a review. 
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+* @vald-green/code-owners-harald
+*.sql @vald-green/code-owners-harald @vald-green/code-owners-data-science
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -4,6 +4,8 @@
 -->
 ## Fixes #
 
+Related DevOps Ticket: AB#<INSERT_TICKET_NUMBER>
+
 ### Description of the changes:
 -
 -

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,8 +1,22 @@
 ## Change Log
 
+### v1.4.1
+
+* Added NEON for ARM64
+* Failed conversion of MJPEG to BGRA is now a warning - not an error.
+
 ### v1.4.0
 
-### v1.3.0
+* Added ARM64 Suport.
+* On Windows Opencv-4.1.1 is now being used and tested.
+* CPP; Adding record.hpp, updated playback.hpp
+* Fixed small error in transformation functions
+* Updated K4aRecorder allow:
+  * Setting manual exposure based on exposure time.
+  * Record BGRA32 format.
+* Added transformation API's to CSharp
+
+### v1.3.0 
 
 * On Windows VS dependencies are now dynamically linked and require redistributables for
 [VS2015](https://www.microsoft.com/en-us/download/details.aspx?id=48145) or newer.

diff --git a/CMakeLists.txt b/CMakeLists.txt
@@ -128,12 +128,15 @@ endif()
 # executable for shared objects. This is done on Linux to emulate the default
 # behavior of the Windows loader, which searches for DLLs in the path of the
 # executable.
+#
+# We only set RPATH for build since our libs and executables are put in the
+# same folder.
 if ("${CMAKE_SYSTEM_NAME}" STREQUAL "Linux")
-    set(CMAKE_BUILD_WITH_INSTALL_RPATH YES)
-    set(CMAKE_INSTALL_RPATH "\$ORIGIN")
+    set(CMAKE_BUILD_RPATH "\$ORIGIN")
 endif()
 
-set(TARGET_ARCH ${CMAKE_SYSTEM_PROCESSOR})
+include(DetermineTargetArch)
+determine_target_arch(TARGET_ARCH)
 
 # CMake doesn't set the target processor correctly for MSVC
 if ("${CMAKE_C_COMPILER_ID}" STREQUAL "MSVC")
@@ -147,16 +150,14 @@ if ("${CMAKE_C_COMPILER_ID}" STREQUAL "MSVC")
 
     # Check what architecture we are building for. This assumes all 64-bit architectures are amd64, which will break
     # if we decide to support arm.
-    if ("${CMAKE_SIZEOF_VOID_P}" STREQUAL "8")
-        set(TARGET_ARCH "amd64")
+    if ("${TARGET_ARCH}" STREQUAL "x86_64")
         configure_file(k4a.props.in ${CMAKE_CURRENT_SOURCE_DIR}/src/csharp/k4a.x64.props)
         configure_file(StubGenerator.xml.in ${CMAKE_CURRENT_SOURCE_DIR}/src/csharp/StubGenerator.x64.xml)
-    elseif("${CMAKE_SIZEOF_VOID_P}" STREQUAL "4")
-        set(TARGET_ARCH "x86")
+    elseif("${TARGET_ARCH}" STREQUAL "i686")
         configure_file(k4a.props.in ${CMAKE_CURRENT_SOURCE_DIR}/src/csharp/k4a.x86.props)
         configure_file(StubGenerator.xml.in ${CMAKE_CURRENT_SOURCE_DIR}/src/csharp/StubGenerator.x86.xml)
     else()
-        message(FATAL_ERROR "Unknown architecture with size of void* = ${CMAKE_SIZEOF_VOID_P}")
+        message(FATAL_ERROR "Unknown architecture for MSVC: ${TARGET_ARCH}")
     endif()
 endif()
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -24,12 +24,69 @@ When opening a new issue be sure to document:
 
 ### Requesting new features
 
-Please review the list of open Issues to see if one is already open. Please review all categories, Bugs and 
-Enhancements. Also check for Closed Issues before opening a new one.
+Please review the list of open Issues to see if one is already open. Please review all categories, Bugs and enhancements. Also check for Closed Issues before opening a new one.
+If you have a small enhancement that is well defined, please create a new feature request on GitHub.
+
+If you have a larger idea for a new feature please share it with us on [Microsoft Azure Feedback Forums](https://feedback.azure.com/forums/920053) where the rest of the community can up vote it too. We will review the submitted ideas very frequently, usually twice weekly. 
+
+Below is our list of possible status states we may assign to the request:
+
+| Microsoft Azure Feedback Forums status| Process steps definition
+|---------------------------------------|---------------------------------------|
+| No status                                 | New issue we have not looked at yet |
+| Need Feedback                         | Idea doesn't have enough details or needs more community support |
+| Under Review                          | Proposal for the new feature is created and in review |
+| Planned                               | Approved to get the work started  |
+| Started                               | Work started                      |
+| Completed                             | Feature is released               |
+| Declined                              | We have decided not to make this change |
+| Moved                                 | Issue which has been moved to GitHub |
+| Archived                              | Feature not possible to implement on current HW. |
+| Triaged                               | Request has been seen and is under internal discussion |
+
+#### No status
+
+This is a new request that we have not yet seen. Within a week we should have reviewed the request and assigned it an initial state.
+
+#### Needs Feedback
+
+The Azure Kinect team uses this state to ask for more information about this issue. We may need more information from the issue filer as we don't completely understand the request. We might also use this status because we are waiting for more community feedback on the proposal; either in the form of spec feedback or up voting.
+
+#### Under Review
+
+The team is actively reviewing the proposal and determine what the next actions should be. We may ask for more information, iterate on the proposal, or move to planned state while we wait for resources. We will also need to carefully consider not only the work to implement the request but the work needed to be invested our build and test infrastructure to ensure quality of the code remains high.
+
+#### Planned
+
+The requested issue has been planned but not yet started. It may stay in this state indefinitely if we don't have resources to complete the request.
+
+#### Started
+
+Work on the feature, new tests, and possible infrastructure changes have begun.
+
+#### Completed
+
+The requested issue has been checked into develop branch and we are done. The feature however, may not yet be part of a release.
+
+#### Declined
+
+We have consider the request and have decided not to implement it due to various reasons. For example, the idea cannot be implemented with the current hardware.
+
+#### Moved
+
+Issue has been moved to GitHub for tracking.
+
+#### Archived
+
+We will archive the idea if the current hardware can't support the request.
+
+#### Triaged
+
+We use the this status to indicate that request has been seen and is under internal discussion.
 
 ## Finding issues you can help with
 
-Looking for something to work on? Issues marked [``Good First Issue``](https://github.com/Microsoft/Azure-Kinect-Sensor-SDK/labels/good%20first%20issue) 
+Looking for something to work on? Issues marked [``Good First Issue``](https://github.com/Microsoft/Azure-Kinect-Sensor-SDK/labels/good%20first%20issue)
 are a good place to start.
 
 You can also check the [``Help Wanted``](https://github.com/Microsoft/Azure-Kinect-Sensor-SDK/labels/help%20wanted) tag to 

diff --git a/README.md b/README.md
@@ -1,8 +1,6 @@
 # Azure Kinect SDK (K4A)
 
-Welcome to the Azure Kinect DK Sensor SDK! While devices and the Body Tracking SDK will be available this
-summer, we wanted to share the Sensor SDK now. We hope you can use this interim period to get familiar with
-our SDK, ask questions, and provide feedback. See [Azure.com/Kinect](https://Azure.com/kinect) for device
+Welcome to the Azure Kinect Sensor SDK! We hope you can use it to build many great applications and participate in the project. Don't be shy to ask questions, and provide feedback. See [Azure.com/Kinect](https://Azure.com/kinect) for device
 info and available documentation.
 
 [![Build Status
@@ -83,6 +81,8 @@ email to ensure we received your original message. Further information, includin
 [MSRC PGP](https://technet.microsoft.com/en-us/security/dn606155) key, can be found in the
 [Security TechCenter](https://technet.microsoft.com/en-us/security/default).
 
-## License
+## License and Microsoft Support for Azure Kinect Sensor SDK
 
-[MIT License](LICENSE)
+[MIT License](LICENSE)
+
+[Microsoft Support for Azure Kinect Sensor SDK](microsoft-support.md)
-Original file line number
+Diff line change
@@ Expand Up / @@ -4,6 +4,8 @@ @@
     -->
     ## Fixes #
+    Related DevOps Ticket: AB#<INSERT_TICKET_NUMBER>
     ### Description of the changes:
     -
     -
@@ Expand Down @@