Hi all, I’m going to write the documentation of ALTO within two or three days and we would be ready for M5. After the CoNEXT we may get back to alto-0.2.0, and

1. Code Freeze (bug fixes only from here as defined above) Yes 2. Stability branch, i.e., stable/lithium, must be cut and local project versions bumped on master to avoid

1. Code Freeze (bug fixes only from here as defined above) Yes 2. Stability branch, i.e., stable/lithium, must be cut and local project versions bumped on master to avoid

A good starting point. I added the alto-dev mailing list on opendaylight. The team there has test cases to test the correctness of their alto server in ODL. Richard -- Richard

Dear team, The previous draft doc is under review. ---------- Forwarded message ---------- From: Gerrit Code Review <gerrit@...> Date: Wed, Apr 22, 2015 at 3:26 PM Subject: Change in docs[master]:

Hi Kai, Yes. It is US time, I believe. Hence, I see no problem sending out tomorrow noon China time. Talk to you soon. Richard

Hi Shu, Don't worry and take your time. I'll be working on the M5 stuff today. And Richard, The deadline is actually tomorrow noon in China, right?

Yeah, let's do a sync up at the said time. And sorry for that I didn't involved too much in it this week since I'm preparing my tomorrow's Visa appointment. There are tons of materials to be done : (

Dear team, Here is the template. Richard ---------- Forwarded message ---------- From: George Zhao <George.Y.Zhao@...> Date: Monday, May 11, 2015 Subject: [release] [Reminder for offset 2 projects]

Hi Kai, The requirements are here: https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan Richard -- Richard

Agreed. BTW Where can we see the requirements for M5? I'd like to check the list. On 14/05/15 06:17, Y. Richard Yang wrote:

Dear team, My apologies for being quiet in the last few days. I did check and saw that you guys are making good process! Thank you so much! I greatly appreciate it! Tomorrow (May 14) is the M5 cutoff

Mr. Chen, Thank you for your participation. I'm very glad that I can help. Yours, Kai On 08/05/15 11:00, Chenguohai wrote:

Hi all， I have reported and yangtools shall take over that. @Kai, you gave me much help, thank you. Link is here: https://bugs.opendaylight.org/show_bug.cgi?id=3147

Dear all That is my misunderstanding. I have posted my previous question

Mr. Chen, in().ipv4 is a list, so is in().ipv6. On 07/05/15 08:31, Chenguohai wrote:

Hi folks, I am suspecting there are some constraints on AddressGroup which could most include one IPV4 and(or) one IPV6. The processing code in RFC2ModelEndpointAddressGroupCoventer.java seems only

Hi Kai, Good proposal. I’ll try to find who is responsible for that. There is another project(https://wiki.opendaylight.org/view/YANG_Tools:Main), may be the committers know the clue. BR

Mr. Chen, We appreciate your interest of ALTO and the effort to improve its performance. For the record, however, the code are generated by yangtools automatically.

Hi folks, I am reading the code under ALTO@ODL. And here are my two comments. 1:File named‘AltoProviderImplBuilder’under alto-provider/……./modules/module/configuration :in function