[cle-release-team] BasicLTI 2.1.0 -> 2.9.x: ticket review

[Charles Severance]

Yes - this all fits with my understanding.  LTI 2.1.0 means the necessary changes *in LTI* are ready to go and any site can tweak what they need by hand if they really need to activate the code.

The discussion about the ultimate right solution for the default template is still ongoing - hence leaving the JIRAs until a later release.  By putting 2.1.0 out and getting us caught up with the backlog of tons of stuff in the LTI code - we can then focus on the smaller problem of completing KNL-883 and releasing later.

/Chuck


On Apr 10, 2013, at 4:24 AM, Adrian Fish wrote:

> Regarding BLTI-154  ...
> 
> Technically, KNL-883 is not needed for this change. KNL-883 merely adds a default LTI template site for convenience. You could still merge 154 and create a template site yourself and it would all work exactly the same as if KNL-883 had been applied. It would just be nice to have a basic template site already there.
> 
> Also, if this was merged you'd still have to specify the lti site template in props for the code to be activated.
> 
> There is still an unfinished discussion about whether having a site template, populated with some tools like the calendar, makes sense over and above merely having an lti realm (BLTI-151). The two tickets don't clash as the site template could be of type 'lti'.
> 
> Does that make any sense?
> 
> Adrian.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130410/10c15380/attachment-0006.html