My suggestion would be to move the following items to 'backlog':

* ESME-135       Add LDAP to ESME
* ESME-214       Add container-based authentication
* ESME-235       add the profiler plugin by John Resig to profile our jQuery 
calls.
* ESME-308       Update times in standard timeline on a regular basis
* ESME-285       Allow turning features on and off through configuration options
* ESME-228       Error messages for REST API calls - don't make it back to the 
client

@Imitiaz - are far did you get on the Pubsubhubbub implementation?

* ESME-170       Pubsubhubbub support for Atom & RSS actions

Thoughts?

D.

On Tue, Jan 11, 2011 at 6:05 PM, Ethan Jewett <[email protected]> wrote:
> Agreed - I think we have enough for a release, after a quick look at
> the closed tickets.
>
> I see one blocker currently - I'm still in the middle of ESME-287 and
> the formating of the user page timeline is a mess (though I believe
> that the comet timeline is actually working fine here). I'll be
> honest: I'm not optimistic I'm going to be able to fix this in
> January. It should be a pure CSS/HTML issue, so if someone else wants
> to take a shot at the formatting that would be excellent. Once this is
> fixed we can close ESME-287 and open a separate ticket for comet-izing
> the search timeline, which I'm still not sure is going to be
> realistic.
>
> Any other things that we *must* fix before a release?
>
> Ethan
>
> On Tue, Jan 11, 2011 at 4:00 PM, Anne Kathrine Petterøe
> <[email protected]> wrote:
>> Yes, I agree and think we should move at least LDAP and
>> container-based authentication into the backlog for now.
>> Release early and often ;-)
>>
>> /Anne
>>
>> On 11 January 2011 15:07, Richard Hirsch <[email protected]> wrote:
>>> We should probably decide which features are going to be included in
>>> V1.2. We've currently have feature creep and we should probably maybe
>>> a decision what we really want to include in this version.  We might
>>> want to move items that haven't been started yet (LDAP,
>>> container-based authentication, etc) into the backlog and focus on
>>> items that have been started and bugs that are present.
>>>
>>> D.
>>>
>>
>

Reply via email to