Wow, thank you! I agree with Ethan that those 3 bugs can be moved to 1.3 - let's focus on the bug fixes for now.
/Anne On 29 January 2011 07:06, Ethan Jewett <[email protected]> wrote: > Thanks Dick, this is great. > > I commented separately that I think maybe we should keep the ESME-314 > bug in 1.2. > > I've also moved ESME-286 and ESME-287 back to 1.2 and marked them as > resolved. These are complete except for the search timeline and the > formatting of the user timeline (ESME-314). I am still not sure if > switching the search timeline over to automatically update with new > messages is even possible, so I'll hold off on this. > > Regarding the three issues here, I think we can move them to 1.3 > without issue as they are infrastructure bugs, not user-facing or > security issues. > > Ethan > > On Sat, Jan 29, 2011 at 7:00 AM, Richard Hirsch <[email protected]> wrote: >> Morning, >> >> I just did some major pruning for 1.2. I've left the bugs in 1.2 (with >> a few exceptions) and moved most of the Comet and timeline-related >> stuff to 1.3. >> >> There are still some issues where I'm not sure of the status. >> >> * Get rid of deprecated methods [1] >> * Add SBT integration for building project [2] >> * Format rendering gets confused by some punctuation [3] >> >> Please take a look at the list for this issue and update / comment >> issues as appropriate. >> >> Thanks >> >> D. >> >> [1] https://issues.apache.org/jira/browse/ESME-321 >> [2] https://issues.apache.org/jira/browse/ESME-320 >> [3] https://issues.apache.org/jira/browse/ESME-307 >> [4] >> https://issues.apache.org/jira/secure/BrowseVersion.jspa?id=12310850&versionId=12315284&showOpenIssuesOnly=true >> >
