The DNN Technology Ecosystem Advisory Group continues to meet on a weekly basis mapping out the future of DNN. The meeting agenda and minutes are shared here in blog entries so that everyone can see the progress being made and conversations occurring in the group.

This January 29th meeting we discussed about branching, versioning, RFC review, 9.4 planning and more.

Dnn Technology Advisory Group
Meeting Agenda

Date: January 29th 2019
Time: 3PM EST

Participants:
Daniel Valadas, Matt Rutledge, Oliver Hine, Clint Patterson, Mitchel Sellers, Brian Dukes, Andrew Hoefling, Stefan Kamphuis, David Poindexter, Peter Donker, Ernst Peter Tamminga, Daniel Aguilera

1. Review and adoption of agenda
2. Approval of minutes from last meeting
3. Finished business / Reports / Announcements
4. Unfinished business / Status updates
   1. Branching & Structure for all Projects (Confirmation - 5 Min)
      Proposed solution for branching strategy is to have the primary branch of “Development”. This branch will be the real-time branch that changes will merge into*. From here we will create Release branches as needed. For the current point in time we have the Release 9.3.x branch, this is where RC builds are done. Once 9.3.0 is released, changes that need to be included in 9.3.1 will merge to 9.3.x (Controlled by the approvers) and then be merged on a regular basis to Development. Changes slated for 9.4.0 release would be merged to development.
      When we get to 9.4.0 readiness, we will create a 9.4.x branch that makes the RC. After release of 9.4.0 the 9.3 branch will be deleted.
      When we get to 10.0 readiness, we will create a 10.0 branch, and RETAIN the 9.4 branch for support, until a 10.1 release or otherwise deemed necessary based on scope of breaking changes
   2. Persona Bar Versioning (Discussion - 5 Min)
      Should the persona bar versioning be updated to match DNN version #? Benefits are consistency in version. Drawback would be if we want to release PB in the future
   3. RFC Review & 9.4 Planning
      Accessibility focus, vNext API Prototype, cleanup/deprecation minor new features (non breaking) - Estimated Code freeze May 17th RC May 20th Release June 3rd.
   4. 9.3.0 Testing Status & Release Date
      Status? - Will get back with us
      Proposed Schedule: RC2 - February 4th or earlier, Release February 11th
   5. Evoq Compatibility/Development.
      Conversation with Ash regarding versioning and differences between Platform and Evoq, see https://www.dnnsoftware.com/docs/developers/product-versions.html we also discussed showing the Platform version and Evoq version separatelly if ever the versions diverge. We discussed a possibility of revamping the installer. See RFC at https://github.com/dnnsoftware/Dnn.Platform/issues/2537
      We will continue discussing this next week.
5. New business
   1. Meeting Cycles:
      TAG Approvers meeting on February 5th (issues focused), Next Group Meeting February 12th (Technology focused).