Thanks for updating the Google Docs, but we also need your M1 status email for the record. Could someone from NeXt UI Toolkit team please send an email to release@... with the message below. If you ha

Hi, Is there a date for the code release of the NeXt project, and then add it as a decency? Thanks, Alberto Montes

We are currently missing the M2 status email for NeXt UI Toolkit project. Please send an email to release@... with this template filled out [1]. If you have any questions, please do not hesitate to em

We are currently missing the M3 status email for NEXT project. Please send an email to release at lists.opendaylight.org with this template filled out [1]. If you have any questions, please do not hes

We are currently missing the M3 status email for NEXT project. Please send an email to release at lists.opendaylight.org with this template filled out [1]. If you have any questions, please do not hes

By M3, projects should define karaf features and include them in the integration karaf distribution [1]. next project is still missing from Integration/Distribution [2]. Please let me know if there is

Hi Kangli, Do we have chance to have a meeting with An Ho tomorow. Regards Ming Sent from my Mi phoneOn Nov 6, 2015 12:36 AM, An Ho <An.Ho@...> wrote: By M3, projects should define karaf features and

Hi: We are missing you on the map!! Here is how our community map look like, so far we have about 150 people registered on the map. You can double check if your location and information is correct, if

Hi, Abu, Xiaobao, I’ve just talk with An Ho about the process of ODL publishing, considering Abu’s health, I want to take the ‘PTO’ role of NeXt UI Toolkit, what would you say? Thanks, Knly

Hi, An Ho, Any updates about the resources of ODL? Thanks, Knly

We are currently missing the M4 status email for NEXT project. Please send an email to release at lists.opendaylight.org with this template filled out [1]. If you have any questions, please do not hes

Hi NEXT Team, Please note your project features have not been built/included successfully in autorelease as of M4. Projects are strongly encouraged to get their project successfully in autorelease by

Hi NEXTUITOOLKIT Team, I wanted to follow up on the status of your project. We notice that NEXTUITOOLKIT is purely for client browsers with no specific support on ODL JVM side needed. The code is most

Hi Everyone, Your validate-autorelease job will fail to build if you're one of the projects that still have not yet approved the build with jdk8 patch in Boron. If you're one of the projects listed at

Hi NEXTUITOOLKIT Team, RC Artifacts: * Please provide a download link to a release candidate of your project's artifacts. Since your projects builds outside of the OpenDaylight Autorelease process, we

Hi NEXT 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. https://docs.goog

Hi Aikepaer Abuduweili and NEXT Team, This is the formal release review of the NEXT project over email. Please reply with links to the Release Review and Release Notes of the project as well as any ad

Hi next-devs, I realized today that the next project pom.xml configuration is incorrectly configured to always produce release builds. This is why your merge jobs are always failing [1]. In a Maven pr

I think there's some confusion here which explains why the NeXt merge jobs have been failing for a long time now. I submitted this patch to fix it in Boron (and also went ahead and fixed it in Berylli

Hi next-dev, It seems like NeXt's Boron jobs have all been failing since January 26th and was introduced by this patch: https://git.opendaylight.org/gerrit/33589/ Can someone look into resolving the b