[Building Sakai] Sakai 10.4 plan - first week February

[Neal Caidin]

Goes back to my first response, it should be a pull request against the
Sakai project on Github.

On Thu, Jan 15, 2015 at 3:29 PM, alaanizar <alaanizar at iihem.ac.ma> wrote:

> Perfect.
>
> Who has to include it on the trunk?
>
> It's fine for me if it can be included in future releases.
>
> Thank you Neal
>
>
> Alaa NIZAR
>
> Envoyé depuis un mobile Samsung.
>
>
> -------- Message d'origine --------
> De : Neal Caidin
> Date :15/01/2015 20:23 (GMT+00:00)
> A : alaanizar
> Cc : Sakai-Dev ,sakai-pmc at collab.sakaiproject.org,"
> sakai-qa at collab.sakaiproject.org QA"
> Objet : Re: RE : Re: RE : [Building Sakai] Sakai 10.4 plan - first week
> February
>
> I notice in that ticket, which is marked for security so I will not share
> the Jira id on this public list, that you commented the code is working
> fine in 10. But I also notice the ticket is still open, which means it
> would not be flagged to get into the 10.4 release at this time. From a
> process perspective code needs to be :
>
> 1) Merged into trunk and the status in Jira set to resolved
> 2) Verified in trunk and Jira status updated
> 3) Then it can be merged into supported branches (when that makes sense,
> as indicated by status flags for merge)
>
> We can talk about the specifics of this ticket either on the Jira itself
> or on sakai-security at collab.sakaiproject.org.
>
> Thanks,
> Neal
>
>
> On Thu, Jan 15, 2015 at 3:13 PM, alaanizar <alaanizar at iihem.ac.ma> wrote:
>
>> No. It's not a new patch that I have created.
>>
>> It's a patch already available in Jira,  created by Alexander.
>>
>> The patch resolves the email duplication issue with a property in
>> sakai.properties. It's false by default.
>>
>> Yours,
>>
>>
>> Alaa NIZAR
>>
>> Envoyé depuis un mobile Samsung.
>>
>>
>> -------- Message d'origine --------
>> De : Neal Caidin
>> Date :15/01/2015 20:06 (GMT+00:00)
>> A : alaanizar
>> Cc : Sakai-Dev ,sakai-pmc at collab.sakaiproject.org,"
>> sakai-qa at collab.sakaiproject.org QA"
>> Objet : Re: RE : [Building Sakai] Sakai 10.4 plan - first week February
>>
>> Hi Alaa,
>>
>> Are you asking how to contribute a patch to the community release?
>>
>> Now that we are using Git/Github, we like to encourage pull requests as
>> per
>>
>> https://confluence.sakaiproject.org/display/SAKDEV/Git+Setup
>>
>> Thanks!
>> Neal
>>
>>
>> On Thu, Jan 15, 2015 at 2:59 PM, alaanizar <alaanizar at iihem.ac.ma> wrote:
>>
>>> Hi Neal,
>>>
>>> We are running sakai 10.3 now.
>>>
>>> I patched this release to correct the announcements issue.
>>> Also, I patched the code to include the Rmail duplication feature.
>>>
>>> It works nicely.
>>>
>>> I don't know what the steps needed to include it a sakai official
>>> release.
>>>
>>> Yours,
>>>
>>>
>>> Alaa NIZAR
>>>
>>> Envoyé depuis un mobile Samsung.
>>>
>>>
>>> -------- Message d'origine --------
>>> De : Neal Caidin
>>> Date :15/01/2015 19:50 (GMT+00:00)
>>> A : Sakai-Dev ,sakai-pmc at collab.sakaiproject.org,"
>>> sakai-qa at collab.sakaiproject.org QA"
>>> Objet : [Building Sakai] Sakai 10.4 plan - first week February
>>>
>>> [sakai-dev, sakai-pmc, sakai-qa]
>>>
>>> Hi All,
>>>
>>> We are planning to have a Sakai 10.4 release. Our target date is to have
>>> a release candidate (RC01) by January 30 and to release 10.4 the first week
>>> in February.
>>>
>>> We expect this release to be fairly small, on the order of a dozen to
>>> two dozen fixes. The main drivers for this release are a couple of blockers
>>> and updated Sakai Help documentation (originally targeted for 10.3).
>>>
>>> https://jira.sakaiproject.org/browse/SAK-28965 - Sakai 10.3 CAS logins
>>> are broken because of Spring Security upgrade
>>>
>>> https://jira.sakaiproject.org/browse/SAK-28955 - Announcement email
>>> sent immediately without subject or body
>>>
>>> https://jira.sakaiproject.org/browse/SAK-28949 - Updated help files for
>>> 10.4 from documentation team
>>>
>>> There is still time to identify and fix blocker bugs, especially for you
>>> institutions who are recently on 10.3 or are moving onto 10.3 soon.  We
>>> appreciate your help.
>>>
>>> Cheers,
>>> Neal Caidin
>>> Sakai Community Coordinator
>>> Apereo Foundation
>>>
>>>
>>> --
>>> This message has been scanned for viruses and
>>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
>>> is
>>> believed to be clean.
>>> --
>>> This message has been scanned for viruses and
>>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
>>> is
>>> believed to be clean.
>>>
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
>> is
>> believed to be clean.
>> --
>> This message has been scanned for viruses and
>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
>> is
>> believed to be clean.
>>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20150115/2090aae0/attachment.html