Right - I just want to add to what David wrote below: To clarify, yes, I moaned and bitched about this today because it was causing me immediate hassle and heat from other people in my workplace. However, Lift on the whole is vastly more stable than any codebase i've ever worked with (commercial or otherwise) - for that very reason I deploy from master without issue. 98% of the time, having this issue fixed in under 12 hours would be more than perfect, it was just the case in this instance that I needed it done like yesterday ;-)
In no way should people read this thread and think that Lift is unstable. Its not. Period. Lift has an awesome community and is a rockin' product. Cheers, Tim On 24 Feb 2010, at 18:51, David Pollak wrote: > Just to be clear, the Lift team has a particularly stellar record of keeping > the master development branch stable. In the instant case, the master branch > was unstable for about 10 hours. The last time the master branch was not > stable was more than 60 days ago and the instability in that case also lasted > for < 12 hours. I deploy most of my projects against master... as apparently > does Tim. I have not participated in a project, commercial or open source, > where the main development branch (call it master, head, edge, etc.) has been > as stable as it is in Lift. > > So, I don't think we need additional QA. I think the existing processes work > just fine. -- 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.
