Good point Ross - I always forget about Nexus :-)
Im much less grumpy now everything is good again. Appreciate I spammed
the list a little earlier, so sorry about that. Hopefully a brief post-
mortem will help us identify any failings in our process if they are
present. Accidents happen, I know that, and review board isnt full-
proof by any means... rather, perhaps we can just review the processes
we have in place and make sure that we are all adhering to them in a
team effort to avoid these kinds of things happening in the future.
Cheers, Tim
On Feb 24, 3:07 pm, Ross Mellgren <dri...@gmail.com> wrote:
> Tim, you can also pin to certain snapshot dates I believe (-SNAPSHOT versions
> are actually -YYYYMMDDHHMMSS....), if something in the future breaks you.
>
> -Ross
>
> On Feb 24, 2010, at 6:14 AM, Timothy Perrett wrote:
>
>
>
> > Guys,
>
> > I see DPP made a bunch of commits last night. Something in there has
> > fundamentally broken the markup parser. Yesterday I deploy an
> > application to production and today I go to update a small bit of copy
> > that marketing want changed and i'm finding that my application is
> > broken....
>
> > With LiftRules.useXhtmlMimeType = false in Boot, I see the following:
>
> > <script type="text/javascript">
> > // <![CDATA[
> > jQuery(document).ready(function()
> > {liftAjax.lift_successRegisterGC();});
> > var lift_page = "F1075228527421HHA";
> > // ]]>
> > </script>
>
> > This is obviously problematic and all my javascript in my application
> > is now doing this. Sorry to be grizzly about this, but its totally
> > untenable for me to be building apps that work one day and are broken
> > the next... I tried reverting to 2.0-M2, but that was giving me errors
> > about not being able to boot SessionMaster. If we are changing stuff
> > in the core of Lift, we need a good number of eyes (that is, people
> > who are ACTIVE committers) on the changes in review board otherwise
> > stuff like this happens (certainly, I don't remember getting review
> > requests for any of these changes that are now causing me
> > problems...)
>
> > I have to get this fixed today otherwise im going to be seriously
> > flamed.
>
> > A very unhappy Tim.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Lift" group.
> > To post to this group, send email to lift...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > liftweb+unsubscr...@googlegroups.com.
> > For more options, visit this group
> > athttp://groups.google.com/group/liftweb?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
