[Management] GB2 Concernes
tpamsler at ucdavis.edu
Sat Nov 21 07:22:10 PST 2009
Please see inline comment bellow w.r.t. GWT and Solaris:
On Sat, Nov 21, 2009 at 6:47 AM, Clay Fenlason
<clay.fenlason at et.gatech.edu> wrote:
> My own comments about some of these below:
> On Fri, Nov 20, 2009 at 8: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)
> At first glance this does not seem to me a Product Council matter, but
> some notes about what I think it means below.
> It was in my mind an important part of the independent release
> mechanism that there be a release tested against the latest kernel +
> other dependencies. In other words, that what separates an independent
> release from a mere tag is a basic level of QA and documentation
> against known versions of its Sakai dependencies.
> It looks to me like GB2 can claim this for Sakai 2.5.x and maybe 2.6
> (I'm not clear on whether UCDavis is using it in production against
> 2.6, but I think I remember Kirk saying that), but it does not have an
> independent release for Kernel 1.1+. I think this will have an impact
> on whether QA and RM can incorporate it post-trunk-freeze (on my
> understanding, allowance was being made for independent releases
> post-trunk-freeze, but so far GB2 does not qualify), to the extent
> that it's a matter of deadlines for a particular release cycle, but
> again this seems to me outside the scope of PC reviews.
> [As an aside, this is part of what I mean when I talk about the PC
> needing to be "backed up," that it is not date-driven or oriented
> toward particular release versions. In my view the PC is ushering new
> development efforts toward maturity, and provides means for assessing
> where they are along that track, but how inclusion is operationalized
> against a particular release cycle seems to me another question it
> shouldn't meddle with.]
>> 2) The build process is platform specific (see point six in
>> We also need to know if any of our supported platforms may be a problem
>> - it seems that Solaris might be.
> This looks to be a consequence of GWT, and not GB2 as such. Is this a
> reason to look on GWT with disfavor?
GWT on Solaris "kinda" works. You just don't get hosted mode, which
probably will be a none issue once GWT 2.0 has been released.
>> 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
>> 4) GB2 does need modification to the gradebook service - James is
>> Jira'ing a patch so it can go about evaluating it and unfreezing
> What's the nature of the patch? Is it a simple adaptation to the
> recent re-packaging of edu-services?
> management mailing list
> management at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to management-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
More information about the management