[sakai2-tcc] QA and Final Release of an Indie - LTI

[Steve Swinsburg]

Based on that analysis I would say that this is good to go into the branch
for the next release. We need to weigh up shipping unsupported code vs new
code that may have a new bug and or feature or two, but at least has a lot
more support, even if it goes against the historical rule of 'no new
features in the branch'.

As for indies generally, IMO it is up to the project team to say that
something is ready, to roll tags and releases and suggest their inclusion
in the branch next tag. If there can be extra QA resources then that is a
bonus.

cheers,
Steve



On Fri, Mar 15, 2013 at 1:28 AM, Charles Severance <csev at umich.edu> wrote:

> Hi,
>
> I need some more mentoring as to how to get an indie through "QA" and
> included in 2.9-x and 2.9.2.    Do I do my own QA and then just make a
> release and announce it?  Are there community resources that want to take a
> look?  Is there any TCC gating for this or do I just decide when it is time
> to go, make the release tag and tell someone to update the 2-9-x externals?
>
> The reality is that 2.0.0 is a pretty poor bit of code.  I made a tag that
> was just enough to make sure Lessons had something to talk to for 2.9.0 IMS
> Common Cartridge 1.1 import.  The LTI portlet has actually been real solid
> for a few releases - but the new LTI Admin tool in 2.0.0 was kind of a
> Beta.   As a matter of fact, by the time 2.9.0 was done - the trunk of LTI
> was way beyond 2.0.0 and UMich redid the UI of the tool and was running
> that well-past-2.0.0 trunk code since September.  My new code is a bit
> beyond that which UMich is running with the addition of bug fixes.
>
> So even if 2.1.0 turned out to have a few little bugs left, in reality
> 2.1.0 has a lot more production experience than 2.0.0 ever had and there
> are known bugs and security holes in 2.0.0 that are fixed in 2.1.0 - so one
> way or another I want 2.1.0 in Sakai 2.9.2 - because I really cannot
> support 2.0.0 as people start making increasingly sophisticated uses of LTI
> beyond the basic 1.0 launch in the portlet.
>
> Looking for some guidance and assistance.
>
> /Chuck
>
> Begin forwarded message:
>
> *From: *Charles Severance <csev at umich.edu>
> *Subject: **Announcing Sakai LTI 2.1.0-b01*
> *Date: *March 13, 2013 7:27:55 PM EDT
> *To: *dev sakai <sakai-dev at collab.sakaiproject.org>
> *Cc: *"sakai2-tcc at collab.sakaiproject.org Committee" <
> sakai2-tcc at collab.sakaiproject.org>
>
> Hi all,
>
> Sakai LTI 2.1.0 is moving toward inclusion in in 2-9-x and 2.9.2.  This is
> a dramatic improvement over the LTI 2.0.0 that shipped with Sakai 2.9.0 and
> 2.9.1.  Many things have been fixed, new features have been added, the UI
> has been cleaned up, and there are several security fixes.
>
> Release notes:
>
> https://confluence.sakaiproject.org/display/LTI/Home
>
> https://confluence.sakaiproject.org/display/LTI/LTI+-+Release+2.1.0+Notes
>
> Video demonstration:
>
> http://www.youtube.com/watch?v=Xfmc6ePgyaw
>
> It would be great if folks were willing to test this.
>
> /Chuck
>
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130315/bf319b41/attachment.html