OK, the fix has been pushed to 1.0.1-SNAPSHOT and it's in master (1.1-SNAPSHOT).
Derek On Mon, Aug 24, 2009 at 1:30 PM, Derek Chen-Becker <dchenbec...@gmail.com>wrote: > Yes, that should be fixed in both 1.1 and 1.0.1, really. I didn't even see > that issue. The code freeze for 1.0.1 was yesterday, so if I want to get > this fix in (which I think should be in there) then we'll need to push back > 1.0.1. Let me send out a vote email. > > > On Sun, Aug 23, 2009 at 12:27 PM, Jeppe Nejsum Madsen <je...@ingolfs.dk>wrote: > >> >> Derek Chen-Becker <dchenbec...@gmail.com> writes: >> >> > It should be very safe to use 1.0.1-SNAPSHOT. I'm planning on spinning >> the >> > release of 1.0.1 GA next Wednesday, so we're in a code freeze starting >> > Sunday. Really, the 1.0 line is strictly bug-fix at this point >> (1.1-SNAPSHOT >> > is where new features make it in). So far, the things that have made it >> into >> > 1.0.1 are: >> > >> > 1. Proper Oracle support >> > 2. Fix for PostgreSQL double type >> > 3. The DateTime fix >> > 4. Some fixes for the Textile parser >> > 5. Some minor XML parsing fixes (PCDataMarkupParser) >> > 6. Some Actor fixes >> >> Derek, with the flurry of changes you're doing to the Db code (which is >> nice :-), it's increasingly difficult to maintain my own copy which >> fixes http://github.com/dpp/liftweb/issues#issue/36 >> >> Any chance to get this included in 1.1 soon? (It's a two line fix :-)? >> >> /Jeppe >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@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 -~----------~----~----~----~------~----~------~--~---
