[WG: Sakai QA] [Building Sakai] Samigo 2.7 Freeze

Lydia L Li lydial at stanford.edu
Sun Nov 22 23:07:50 PST 2009


All,

   James has already contacted us about the patch (SAK-17377). We will merge it in 2.7. 

thanks,
Lydia


----- "Anthony Whyte" <arwhyte at umich.edu> wrote:

| One exception to the Samigo team's decision to freeze new features for
| 2.7:  Samigo, edu-services and the gradebook teams need to decide if
| GB2-related SAK merges are acceptable for inclusion in 2.7.  I
| recommend the three teams collaborate in order to frame a joint
| recommendation.  See summary of concerns below.
| 
| 
| Cheers,
| 
| 
| Anth
| 
| 
| 
| 
| 
| 
| Begin forwarded message:
| 
| 
| 
| 
| From:  James Renfro < jlrenfro at ucdavis.edu >
| Date:  November 21, 2009 7:43:32 PM GMT-05:00
| To:  David Horwitz < david.horwitz at uct.ac.za >
| Cc:  " management at collab.sakaiproject.org " <
| management at collab.sakaiproject.org >
| Subject:  Re: [Management] GB2 Concernes
| 
| Hi David,
| Not sure if you're looking for responses directly from UCDavis at this
| point, but thought I'd answer what I could here in case that's
| helpful.
| 
| See below for inline responses. 
| 
| Thanks,
| James.
| 
| 
| 
| On Fri, Nov 20, 2009 at 5:29 AM, David Horwitz  <
| david.horwitz at uct.ac.za >  wrote:
| 
| 
| Hi All,
| 
| After a brief poke around in GB2 I have a number of concerns that
| seems
| to have slipped through the PC process:
| 
| 1) There is no build for the current trunk (This is blocker but should
| be fairly easy to fix)
| 
| 
| Just to clarify the exact situation here. Building against current
| trunk / 2.7 requires three patches at this moment that are provided as
| part of the module itself. 
|   (1) against edu-services to bring the original gradebook data model
| up-to-date
|   (2) against the gb2 code itself, which is checked in as 2.5.5 
|   (3) against the sam module
| 
| The (1) patch will be eliminated if and when the Gradebook committers
| approve SAK-17428, and the (2) patch will be eliminated in the next
| couple of days when I commit that change. (3) will be eliminated when
| the Samigo committers approve SAK-17377.  
| 
| Of course, the question then becomes exactly what you want tools to do
| -- should gb2 trunk build against fnd trunk, or the 2.7.x branch? I
| assume trunk. Especially at this moment, with 2.5.x, 2.6.x, 2.7.x, and
| trunk all currently in existence and supported, it is not really
| feasible, afaics, for a tool to create a branch for each, in addition
| to the tool's own versioning and development. It's a merging
| nightmare. Our preference would be to maintain GB2 trunk against FND
| trunk or 2.7.x and provide binary artifacts for distribution via the
| Sakai maven repositories. I believe we can accomplish this currently
| by maintaining sakai comptability patches and applying these ourselves
| on each tag release, compiling a release artifact and uploading it to
| the appropriate maven repo for 2.5.x, 2.6.x, and 2.7.x. Institutions
| that wish to bring down the source code may, and will have to apply
| the Sakai version patches themselves. 
| 
| This is practical for our purposes since the actual Sakai APIs we
| interact with have barely changed since 2.4.x -- while the build
| process and dependency management has shifted tremendously. Our gb2
| patch is almost entirely to accommodate the pre-kernel/post-kernel
| situation. As we make bug fixes and add functionality it is much more
| appealing to us to have all institutions receive those changes
| simultaneously rather than tying them to a particular Sakai verison. 
| 
| c.f. 
| http://jira.sakaiproject.org/browse/SAK-17428
| http://jira.sakaiproject.org/browse/SAK-17377
| 
|  
| 
| 
| 
| 2) The build process is platform specific (see point six in
| https://source.sakaiproject.org/contrib//gradebook2/trunk/sakai/2-6-x/INSTALL.txt
| )
| We also need to know if any of our supported platforms may be a
| problem
| - it seems that Solaris might be.
| 
| 
| Apologies, this particular line of the build process is no longer
| relevant. I'm currently updating the INSTALL.txt to reflect that. The
| system-dependency of GWT disappears at GWT version 2.0 (we're
| expecting to be on 1.7.1 for the next few weeks before the final
| release of 2.0) and in any case is only relevant for compiling the
| Javascript code itself and testing it via GWT "Hosted Mode", a step
| which in our trunk currently is no longer part of the maven build
| process. 
| 
|  
| 
| 3) An open Jira suggests that L18N is incomplete
| ( http://jira.sakaiproject.org/browse/GRBK-366 ) This also suggests
| that
| L18N/L10N is missing from the PC evaluations
| 
| 
| Yes, we need to do a due-diligence check through the code and
| eliminate any cases where a string is hard-coded. We'll probably do
| this in the next few days. Localization of numbers has not been
| incorporated yet, but this should be relatively straightforward. 
|  
| 
| 4) GB2 does need modification to the gradebook service - James is
| Jira'ing a patch so it can go about evaluating it and unfreezing
| edu-services
| 
| 
| 
| Again, this is the issue covered in (1) above. The JIRA is 
| http://jira.sakaiproject.org/browse/SAK-17428
| 
| On Nov 22, 2009, at 10:39 AM, Berg, A.M. wrote:
| 
| 
| 
| 
| 
| Hi all,
| 
| I would like to announce the freezing of Samigo 2.7
| 
| Monday, Anthony will:
| 
| 1) create a samigo 2.7.x branch
| 2) update samigo trunk poms to 2.8-SNAPSHOT
| 
| 
| Alan
| 
| Alan Berg
| Interim QA Director - The Sakai Foundation
| 
| Senior Developer / Quality Assurance
| Group Education and Research Services
| Central Computer Services
| University of Amsterdam
| 
| http://home.uva.nl/a.m.berg
| 
| 
| 
| 
| -----Original Message-----
| From: sakai-dev-bounces at collab.sakaiproject.org on behalf of Steve
| Swinsburg
| Sent: Sat 11/21/2009 3:16
| To: Anthony Whyte
| Cc: sakai-dev sakai-dev
| Subject: Re: [Building Sakai] Master pom: removing
| myfaces.zones.apache.orgrepo reference
| 
| +1.
| 
| Does anyone know if it's coming back?
| 
| cheers,
| Steve
| 
| 
| On 21/11/2009, at 8:52 AM, Speelmon, Lance Day wrote:
| 
| > +1
| >
| >
| > Lance Speelmon
| > Scholarly Technologist
| >
| > On Nov 20, 2009, at 4:25 PM, Anthony Whyte wrote:
| >
| >> Any objection to commenting out/removing the
| myfaces.zones.apache.org repo reference in the master pom?  I checked
| the Apache network and it's nowhere to be seen.  Excluding it should
| speed up the builds a wee bit.
| >>
| >> Cheers,
| >>
| >> Anth
| >>
| >> <repository>
| >>             <id>apache-repo</id>
| >>             <name>apache-repo</name>
| >>             <layout>default</layout>
| >>             <url>
| http://myfaces.zones.apache.org/dist/maven-repository </url>
| >>             <snapshots>
| >>                 <enabled>false</enabled>
| >>             </snapshots>
| >>         </repository>
| >>
| >> Forbidden
| >>
| >> You don't have permission to access /dist/maven-repository on this
| server.
| >>
| >> Additionally, a 403 Forbidden error was encountered while trying to
| use an ErrorDocument to handle the request.
| >>
| >> Apache/2.0.63 (Unix) DAV/2 Server at myfaces.zones.apache.org Port
| 80
| >>
| >> Begin forwarded message:
| >>
| >>> From: Seth Theriault < slt at columbia.edu >
| >>> Date: November 19, 2009 2:00:16 AM GMT-05:00
| >>> To: Anthony Whyte < arwhyte at umich.edu >
| >>> Cc: Speelman Lance < lance at indiana.edu >, Maurer Christopher <
| chmaurer at iupui.edu >, Horwitz David < david.horwitz at uct.ac.za >
| >>> Subject: Re: Apache infrastructure machine status
| >>>
| >>> Anthony Whyte wrote:
| >>>
| >>>> Nothing I see in the Apache network that sheds any light on the
| status
| >>>> http://myfaces.zones.apache.org/dist/maven-repository
| >>>
| >>> I think this repo is dead or out of date.
| >>>
| >>> Looking at:
| >>>
| >>>
| http://wiki.apache.org/myfaces/Using_MyFaces_in_a_Project_built_with_Maven
| >>>
| >>> I think the libs are served out of the central maven2 repos
| >>> now.
| >>>
| >>> Seth
| >>>
| >>>
| >>
| >> _______________________________________________
| >> sakai-dev mailing list
| >> sakai-dev at collab.sakaiproject.org
| >> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
| >>
| >> TO UNSUBSCRIBE: send email to
| sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
| "unsubscribe"
| >
| > _______________________________________________
| > sakai-dev mailing list
| > sakai-dev at collab.sakaiproject.org
| > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
| >
| > TO UNSUBSCRIBE: send email to
| sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
| "unsubscribe"
| 
| 
| 
| 
| 
| 
| 
| _______________________________________________
| sakai-qa mailing list
| sakai-qa at collab.sakaiproject.org
| http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
| 
| TO UNSUBSCRIBE: send email to
| sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of
| "unsubscribe"
| 
| _______________________________________________
| sakai-dev mailing list
| sakai-dev at collab.sakaiproject.org
| http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
| 
| TO UNSUBSCRIBE: send email to
| sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
| "unsubscribe"


More information about the sakai-qa mailing list