Hi,

version 2.0 of the Adapt Framework has been a long time in the making. I'm pleased to say that we're finally nearing the code freeze for this. As a reminder to the everyone, the process we're following is:

• develop things like mad
• put in place a code freeze (roughly three to four weeks - roughly three to four weeks before the official release)
  • at this point, the scope of new features for the release is set - we will not add any further functionality and all known issues should be fixed.
• run a thorough testing period
  • We issue a test package to all collaborators and the community with a built module, the source code and a testing brief. We're keen for as many community members to help with the testing and reporting of bugs. Regardless, the official collaborators will all be asked to run this through their testing teams so that we can be confident that the new release is as stable as possible.
  • The core team also fixes issues during this time and retests to verify the fixes
• announce the official release
  • At this point, our "master branch" is updated and tagged. With the upcoming release, we have made a particular effort with the documentation, adherence to specifications and made sure that we have a much improved, better performing and stable product. We can't wait to get this out and hear everyone's thoughts.

For those of you, who'd like to follow us "live", please see our agile sprint chart in JIRA. At the end of this sprint, we will put in place the code freeze and get onto testing the release.

For anyone interested in the system spec and standards for v2.0 of the Adapt Framework, please see this thread.

Thanks,
Sven