[sakai2-tcc] Small change to trunk kernel related to KNL-1011
Steve Swinsburg
steve.swinsburg at gmail.com
Sun Feb 24 13:46:21 PST 2013
I still think we should have t-shirts with "I broke the build" on them :)
Gesendent von meinem iPhone
On 25/02/2013, at 4:39, Charles Severance <csev at umich.edu> wrote:
> You may have seen a commit go by related to KNL-1011 to "fix trunk":
>
> https://source.sakaiproject.org/viewsvn?view=revision&revision=120432
>
> https://jira.sakaiproject.org/browse/KNL-1011
>
> Things related to KNL-1011 were mostly working in the trunk but editing a site using Site Info or Admin -> Sites with the trunk code prior to r120432 ended up causing a problem.
>
> A fix is being developed and you should see another commit soon that backs out my commit. But in the meantime it seemed like a good idea to make a simple change to keep trunk with 100% functionality in case folks do an full source check out or an svn update and I also wanted the trunk instance on nightly2.sakaiproject.org (just rebuilt at noon Eastern Time US) to also have 100% functionality while the real fix is being worked on.
>
> These things happen. We have a saying that if you never break trunk - you are not working hard enough :) KNL-1011 is a really important step forward in terms of performance for the SiteService and portal page loading. I am really excited about it - but it is non-trivial code deep in the Sakai engine room - so it is natural that when we go into the engine room, we will find and catch little things.
>
> Comments welcome.
>
> /Chuck
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130225/6df4b0cc/attachment.html
More information about the sakai2-tcc
mailing list