Document release process about moodle

[SorraTheOrc]

@hosungsmsft can you please review this proposal

[hosungsmsft]

Given the long deployment time of the template, I'm not sure how the validations will work effectively and if the release period is a bit too frequent in that sense? Let's sync up offline on the validation methods.

[SorraTheOrc]

I'd much rather we do things that affect all users in the public space than offline (that's not to say we can't discuss offline and bring proposals here). The goal is to have the maximum input from potential partners. For example, my answer below provides an ideal opportunity for others to help us out...

The goal of fast release cycles is:

1. move as fast as users need us to
2. forcing function to automate as much as possible

I agree that long deployment times make manual testing difficult, the answer is therefore to set up a CI solution that is continually testing dev and releasecandidate branches (by the way, this is something I'm already working on ;-)