Created "1.2" (realized that "Release" is a bit redundant when naming a release...) and added a few issues: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310850&fixfor=12315284
Issues added: 1. Container-based authentication 2. Pubsubhubbub 3. Tag & conversation following Let the discussion begin :-) Ethan On Fri, Aug 27, 2010 at 3:20 PM, Richard Hirsch <[email protected]> wrote: > "1.2" sounds great > > On Fri, Aug 27, 2010 at 3:15 PM, Ethan Jewett <[email protected]> wrote: >> Cool! Thanks for doing this Dick. It does look great. >> >> With regards to the next release, Should set it up in Jira so that we >> can start adding tickets to the release? Do you think now would be the >> right time to set that up? "Release 1.2"? >> >> Ethan >> >> On Fri, Aug 27, 2010 at 11:59 AM, Richard Hirsch <[email protected]> >> wrote: >>> I just deployed on Stax >>> (http://esmecloudserverapache.dickhirsch.staxapps.net/) and everything >>> looks great - search works as well. >>> >>> We now just have one release issue left ( >>> https://issues.apache.org/jira/browse/ESME-207) which is related to >>> IE7. I played around with it a bit and the problem is associated with >>> the CSS style and the width of the items involved. I was hoping that >>> Anne would have time to fix the error.but she is currently on the road >>> at the moment. >>> >>> I may try and look at the problem tonight at home where I have IE7 but >>> no ESME installation. >>> >>> Once we have that bug fixed, I'll start the official preparation for >>> the next release (tags, etc.) >>> >>> While we are preparing for the next release, we can obviously keep >>> working on other features. This current release is associated with the >>> UI. The next few releases should probably concentrate on server-based >>> functionality (pubsubhubbub, etc.) - that is our strength and where >>> the greatest potential lies. >>> >>> D. >>> >> >
