As a committer on this project I am +1 for archiving messaging4transport. There hasn't been any activity on the project recently and the project has not participated in a release since Beryllium. Rega

Dear Messaging4Transport developers, The OpenDaylight TSC is initiating a termination review in order to archive the Messaging4Transport project [1], as per section 2.3.5 of the OpenDaylight Project L

Messaging4Transport project is formally declining to participate in the Carbon Simultaneous Release. Thank you. Regards, Pradeeban. -- Pradeeban Kathiravelu. PhD Researcher, Erasmus Mundus Joint Docto

Hi All, The Messaging4Transport project is formally declining to participate in the Boron SR. Regards, Pradeeban. -- Pradeeban Kathiravelu. PhD Researcher, Erasmus Mundus Joint Doctorate in Distribute

Hi MESSAGING4TRANSPORT Team, This is a friendly reminder that we are currently missing the M1 status email for your project. Please send an email to release@... with the status template filled out [1]

Hi Messaging4Transport, I noticed one of your CSIT jobs [0] today, and that it was broken (red dot). Looks like restconf is not being pulled in as a dependency of the two features being installed (odl

Hello Pradeeban Kathiravelu and the messaging4transport development team: If you've already registered for the Boron Developer Design Forum (DDF) please disregard this email and I look forward to seei

Hi MESSAGING4TRANSPORT Team, Please take a moment today to address some action items for your project regarding the Beryllium Release. 1. We are missing the Beryllium GO/NOGO vote for your project. ht

I'm working on it. --Colin

When: Friday, February 12, 2016 7:30 AM-9:30 AM (UTC-08:00) Pacific Time (US & Canada). Where: IRC #opendaylight-meeting Note: The GMT offset above does not reflect daylight saving time adjustments. *

Hi Devs, Could you please review and merge the patch [1], which contains the documentation for Messaging4Transport Beryllium? [1] https://git.opendaylight.org/gerrit/#/c/30724/ Thank you. Regards, Pra

Hi MESSAGING4TRANSPORT Team, RC Status [1]: Please take a moment to update your project with the status of your own external testing using the release candidates and verify if there are any issues wit

Messaging4Transport 1. Please provide updates on any previously-incomplete items from prior milestone readouts: Automated system testing for top-level features merged. 2. Has your project met code fre

merged.

Just for the public record, could we get an email of Tony's +1 somewhere to link to? Thanks, --Colin

Hi All, Thanh Ha has been a great contributor and motivator to the Messaging4Transport with his code contributions [1] and reviews. Given that the early stage of Messaging4Transport, his contributions

Hi JamO, I am sorry for not responding to this in a timely manner - I was having a late summer vacation. The bugs reported regarding messaging4transport must have been fixed with https://git.opendayli

Messaging4Transport 1. Please provide updates on any previously-incomplete items from prior milestone readouts. 1.1. Checked in the asciidoc outlines? Link to gerrit patch? https://git.opendaylight.or

Hi Messaging4Transport Team, For M3, Messaging4Transport project has three missing items. Could your team please provide an ETA for when the items can be completed. 1. Checked in the asciidoc outlines

Hi messaging4transport-devs, I opened blocking bug [1] to track issue with messaging4transport-features depending on a dependency that is not found: features-aaa 0.2.1-SNAPSHOT. This is blocking Beryl