chibenwa commented on pull request #886:
URL: https://github.com/apache/james-project/pull/886#issuecomment-1069851749


   > sorry for the absence (I had to do other tasks).
   > What is the current status? Should I cherry-pick the commits from 
https://github.com/apache/james-project/pull/903?
   
   Hello @ff-wl !
   
   No worry, we'd been actively working on our side too! That is days I want to 
make a status statement regarding our progress!
   
   #903 is not that critical I'd rather not put it on the critical path. Idem 
for #898 . We will rebase them later.
   
   ## Remaining blockers
   
    - [ ] https://github.com/apache/james-project/pull/917 Apparently we broke 
COMPRESS + IDLE. Likely in your original commits. It explains the IMAP IDLE 
invalid commands we got in Thunderbird. We still need to figure out a fix.
    - [ ] We need to evaluate the performance behaviour of 
https://github.com/apache/james-project/pull/908 . Before refining the 
behaviour with flame graphs to tune the Netty stack we got perfs somehow 
similar to Netty3. I'm expecting us to be good in this regards.
    - [ ] Better understanding of Netty stack leads to bug findings. I don't 
want to create a hard dependency, but we will need at some point to integrate 
https://github.com/apache/james-project/pull/919 into the Netty4 work or vice 
versa...
   
   Please note that 3.7.0 being released when addressing the above points we 
can merge ;-)
   
   We are making slow progress, but methodically, adding critical pieces of 
testing for the IMAP stack, significantly improving its reliability.
   
   Best regards,
   
   Benoit TELLIER


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to