[Deploying Sakai] [sakai2-tcc] Request to include SAK-22283 in the 2.9.3 tag

Jean-Francois Leveque jean-francois.leveque at upmc.fr
Tue Jul 2 08:04:08 PDT 2013


I didn't find the answer to:
Are strings returned by LinkMigrationHelper.java's editLinks and 
bracketLinks displayed in the UI? Same question for 
LinkMigrationHelperImpl.java's bracketAndNullifySelectedLinks.

On 26/06/2013 14:43, Bryan Holladay wrote:
>
>     First question is, are the changes fine for projects that have an
>     specific maintenance team, such as samigo, lessons, kernel...?
>
>
> Yes, we've been patching and discussing this patch for almost a year
> now: 17-Jul-2012
>
>     Who has checked the changes for the parts maintained by the CLE team?
>
>
> It's mainly been Aaron Z and me working with George.
>
>     I'm now trying a shallow i18n check.
>
>
> George just patched the issues you found with i18n:
> http://source.sakaiproject.org/viewsvn?root=svn&view=rev&rev=126289
> <http://source.sakaiproject.org/viewsvn?root=svn&view=rev&rev=126289>
>
>
> Did we catch everything?  Are we at a +1 or 0 for i18n?
>
>     On 24/06/2013 22:02, Bryan Holladay wrote:
>
>         The document addresses each requirement in the merge policy.  My
>         opinion
>         is yes.
>
>
>         On Mon, Jun 24, 2013 at 3:58 PM, May, Megan Marie
>         <mmmay at indiana.edu <mailto:mmmay at indiana.edu>
>         <mailto:mmmay at indiana.edu <mailto:mmmay at indiana.edu>>> wrote:
>
>              Does it met the requirements in the maintenance branch
>         merge policy?
>
>         https://confluence. sakaiproject.org/display/TCC/
>         Maintenance+Branch+Merge+ Policy
>         <https://confluence.sakaiproject.org/display/TCC/Maintenance+Branch+Merge+Policy>
>
>
>              *From:*sakai2-tcc-bounces@ collab.sakaiproject.org
>         <mailto:sakai2-tcc-bounces at collab.sakaiproject.org>
>         <mailto:sakai2-tcc-bounces@ collab.sakaiproject.org
>         <mailto:sakai2-tcc-bounces at collab.sakaiproject.org>>
>              [mailto:sakai2-tcc-bounces@ collab.sakaiproject.org
>         <mailto:sakai2-tcc-bounces at collab.sakaiproject.org>
>         <mailto:sakai2-tcc-bounces@ collab.sakaiproject.org
>         <mailto:sakai2-tcc-bounces at collab.sakaiproject.org>>] *On Behalf Of
>              *Neal Caidin
>              *Sent:* Monday, June 24, 2013 3:18 PM
>              *To:* Bryan Holladay
>              *Cc:* production at collab. sakaiproject.org
>         <mailto:production at collab.sakaiproject.org>
>         <mailto:production at collab. sakaiproject.org
>         <mailto:production at collab.sakaiproject.org>>; Sakai 2 Technical
>
>              Coordination Committee; oit-atg (oit-atg at Virginia.EDU); George
>              Pipkin; sakai-dev at collab.sakaiproject. org
>         <mailto:sakai-dev at collab.sakaiproject.org>
>         <mailto:sakai-dev at collab. sakaiproject.org
>         <mailto:sakai-dev at collab.sakaiproject.org>> Developers
>              *Subject:* Re: [sakai2-tcc] Request to include SAK-22283 in the
>
>              2.9.3 tag
>
>              I'm excited to see progress on this issue. This feature
>         looks like a
>              great community feature.
>
>              My main concern is just if we have sufficient QA resources
>         to get it
>              into 2.9.3 in time. We have a tight schedule and this is not a
>              critical fix to get into 2.9.3. We need to keep the scope
>         of 2.9.3
>              controlled to meet our schedule, which we agreed was a high
>         priority
>              (to get the 2.9.3 release out in July).
>
>              My vote would be
>
>              +1 for 2.9.x
>
>              -1 for 2.9.3
>
>         https://jira.sakaiproject.org/ browse/SAK-22283
>         <https://jira.sakaiproject.org/browse/SAK-22283>
>
>              Cheers,
>
>              Neal Caidin
>
>              Sakai CLE Community Coordinator
>
>         neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
>         <mailto:neal.caidin at apereo.org <mailto:neal.caidin at apereo.org> >
>
>              Skype: nealkdin
>
>              AIM: ncaidin at aol.com <mailto:ncaidin at aol.com>
>         <mailto:ncaidin at aol.com <mailto:ncaidin at aol.com>>
>
>
>              On Jun 21, 2013, at 2:41 PM, Bryan Holladay
>         <holladay at longsight.com <mailto:holladay at longsight.com>
>         <mailto:holladay at longsight.com <mailto:holladay at longsight.com>
>          >> wrote:
>
>
>
>              Since it's been almost 24 hours and no responses, I figured
>         I'd add
>              my 2 cents.
>
>              +1 for 2.9.x
>
>              +1 for 2.9.3 (if there isn't enough QA, I can see if Derek
>         will test)
>
>              I consider myself a 3rd party member on this jira.  I've been
>              helping George trek through the Sakai workflow for this
>         jira, but
>              I'm not actually tied to the development of this feature.  I've
>              tested and helped clean up the patch (along with others),
>         so I'm
>              familiar really familiar with this ticket.  It adds a
>         feature that a
>              lot of our clients have been requesting for since the
>         EntityPicker
>              tool was abandoned and not compatible for the CKEditor.  So
>         for a
>              lot of people, this isn't a new feature, but a return of an old
>              feature.
>
>              On Thu, Jun 20, 2013 at 6:04 PM, George Pipkin
>         <gpp8p at virginia.edu <mailto:gpp8p at virginia.edu>
>         <mailto:gpp8p at virginia.edu <mailto:gpp8p at virginia.edu>>> wrote:
>
>              Hi -
>
>                  This is a request to include SAK-22283 in the v2.9.3
>         tag.  The
>              particulars of the request including a description of the
>         included
>              functionality and a test plan are included in the attached word
>              file.  Please feel free to contact me if you have any
>         questions.
>
>
>                                               - George Pipkin
>                                                   U.Va.


More information about the production mailing list