[cle-release-team] Trunk Experimental Build changes

[Steve Swinsburg]

It can run along side, diff toolIds.

cheers



On 02/02/2012, at 10:10 AM, Matthew Jones wrote:

> Perhaps asking the obvious, but does Roster2 run alongside or drop in replace Roster?
> 
> I was planning on bringing up this list for a short discussion at the release meeting tomorrow. I'm not expecting much debate, but there might be some tools that I missed or some that people want to omit.
> 
> If any don't build or deploy into trunk easily (in under 10 minutes of my time), those are automatically excluded. ;)
> 
> On Wed, Feb 1, 2012 at 6:01 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> I am in the middle of doing the Roster2 1.0.0 release so please include that. It has also been proposed from promotion before.
> 
> Same feature set as Roster classique but improved integration with Profile2 (and everyone loves profile2 ;)
> 
> cheers,
> Steve
> 
> 
> 
> 
> On 02/02/2012, at 6:30 AM, Matthew Jones wrote:
> 
>> Jim Eng put in a request today to add Dashboard to the trunk experimental build. [1] Experimental used to be a place where contrib tools that may be considered for a future release, or the most popular contrib tools were put so at least they had some place to run as a nightly demo. Currently though there's no tools in experimental that are different from the main build since everything was approved during the 2.8/2.9 cycles.
>> 
>> Along with dashboard I was thinking there are a few others that might be worth putting up in there if the effort to get them deployed in trunk is minimal. Running these tools on experimental wouldn't be a sign of approval of incubation or any other process. Just that these tools are used in the community and "well known". Increasing interest could get further support for them, pushing them toward larger adoption.
>> 
>> * Evaluation - The latest release tag is currently running on qa5-us, and it needs some initial setup but still could be worth putting here. Unknown if this would ever make a core tool
>> * Clog - This is the most supported blog tool (that I know of) and was considered for previous releases. Blogwow also still appears to be supported by Sam.
>> * The Etudes tools (melete, mneme, jforum) - While these never will be in core, many schools are interested in them
>> * Signup tool - Just seems like a good tool overall, and great support from Yale
>> * GB2 - Because of licensing will likely never make core, but some schools may want to check it out
>> * The Edia tools (Scorm player, knowledgebase, etc) - I think knowledgebase could be a possible replacement someday for help if they were interested in promoting it
>> * The newsfeeds tool - This didn't make 2.9 because there was a library that couldn't be updated in time(wicket-dojo), but I think it was still functional
>> * Assignments2 - Has had a lot of work around it, if it runs alongside assignments seems like it would be worth including.
>> 
>> Any thoughts? Additions? Subtractions?
>> 
>> [1] https://jira.sakaiproject.org/browse/INFRSTR-89
>> _______________________________________________
>> cle-release-team mailing list
>> cle-release-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 
> 

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