esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Jewett <>
Subject Re: Release planning
Date Sat, 17 Jul 2010 14:11:44 GMT
Thoughts on items remaining for this release:

ESME-225 - "need unit test for GET api2/users/actions don't retrieve
disabled actions" - I don't think this is required for release and
should be moved to the backlog.

ESME-242 - "The use of metadata in the api2 currently doesn't work" -
I think this is important but also not required for release and should
be moved to the backlog.

I agree that ESME-205 and ESME-212 are major. ESME-212 at least is a blocker.

Regarding changes to be made to API2: I've created JIRA issues for all
the todos at the bottom of the file (except a couple that were already
done). It was lazy of me to put a todo-list in the file - I should
really avoid that and force myself to have everything in Jira. I will
be checking in a version of the file without the todo-list shortly.


On Fri, Jul 16, 2010 at 12:40 PM, Richard Hirsch <> wrote:
> I've been working on the JIRA items and we have 10 items left for this
> release.
> The following items are linked to IE 7:
> * ESME-207
> * ESME-239
> * ESME-208
> Some of these items are CSS-related (for example, 207) but the other
> ones are javascript / jquery related.
> I think the two main issues are:
> * ESME-205 Search is broken (This only happens when you use a JDBC
> based compass indexes - first noticed on Stax but it also is present
> locally)
> * ESME-212 Messages from pools aren't hidden
> I'm going to be gone the next four weeks on vacation, so either
> someone else can coordinate the release or we wait until I return to
> continue with our release preparations.
> If anyone wants to work on other items until the release, here are
> other items that I consider important:
> * ESME-108 - View my pools" functionality
> * ESME-170   Pubsubhubbub support for Atom & RSS actions#
> * ESME-214   Add container-based authentication
> * ESME-213   Twitter API is out-of-date and API calls don't always
> return the correct info
> -- other api2 related changes - see the ToDos at the bottom of the
> API2.scala page .
> D.

View raw message