Steve published a document explaining what the process is. Most likely on the wiki, please try and track it down. If we have an issue with the openwrt repo that doesn’t actually force a release as that repo isn’t actually part of the code that is tagged and released. However, if this exposes issues in the core/alljoyn project then we may have to make a release.
From: Josh Spain [mailto:[email protected]] Sent: Tuesday, May 10, 2016 3:59 PM To: Lioy, Marcello <[email protected]> Cc: Jorge Martinez <[email protected]>; [email protected]; Aaron Vernon <[email protected]>; Jarrod Moldrich <[email protected]>; Schuff, Kristopher <[email protected]> Subject: Re: FW: OpenWRT and Core We currently have a 16.04-test branch. I believe this is what Kris and his team used to test the release. I have just created a 16.04-review branch based on the 16.04-test branch. I have reviewed the changes that Jarrod made. There are a few things to discuss, like the fact that we even have a separate branch that's not a feature branch called 16.04-baseservices. This diverges from how things were done in the past. The correct way to do this (based on my understanding) is for the Base Services team to make changes directly to the 16.04-test branch. One important thing to be aware of is that we will need some amount of testing again for Core on OpenWrt in order to merge their changes in to the release branch (after it is cut). This may mean that we need a 16.04a release after all. -Josh On Tue, May 10, 2016 at 4:25 PM, Lioy, Marcello <[email protected]<mailto:[email protected]>> wrote: Josh, Jorge, What is the plan for the Open WRT feed branch? I know typically we don’t create the “released” branch until after the BI review period as that is when we know that the release is unencumbered. Is that where we are at? My understanding is that Jarrod contacted you with a list of issues? Are those being addressed? From: Jarrod Moldrich [mailto:[email protected]<mailto:[email protected]>] Sent: Monday, May 09, 2016 5:49 PM To: Aaron Vernon <[email protected]<mailto:[email protected]>> Cc: Lioy, Marcello <[email protected]<mailto:[email protected]>>; Jarrod Moldrich <[email protected]<mailto:[email protected]>> Subject: Re: OpenWRT and Core Hi Marcello, I did see the 16.04-test branch but didn't see movement on it, so figure it mustn't be ready for release. From our experience, there's still a number of changes that need to occur before the feed would be usable in the real world. Our OpenWRT maintainer just had twins, so I can't point to the issues directly until we get back up to speed. However, we have our branch up for code-review and the git message offers some clues. I can recall one thing that we needed to do was respect the Config Service moving to the core repository (can't be sure how Config would get built with the 16.04-test branch) https://git.allseenalliance.org/gerrit/#/c/7703/ From memory, we also have a couple of other niceties in there including the ability to cache the OpenWRT SDK build which dramatically reduces build times. Hopefully our work will be useful to you. Would also be great if someone could eyeball our code and give us the thumbs up or down :) Cheers, Jarrod On Tue, May 10, 2016 at 9:37 AM, Aaron Vernon <[email protected]<mailto:[email protected]>> wrote: Looping in Jarrod to explain what we think is missing. Sent from my iPhone On May 9, 2016, at 7:32 PM, Lioy, Marcello <[email protected]<mailto:[email protected]>> wrote: It was tested, what are you looking for exactly? From: Aaron Vernon [mailto:[email protected]] Sent: Monday, May 09, 2016 2:28 PM To: Lioy, Marcello <[email protected]<mailto:[email protected]>> Subject: OpenWRT and Core Hi Marcello, If I am not too late, can you add an agenda item tomorrow for talking about releasing Core for OpenWRT - the base services team noticed that it wasn't there. Cheers Aaron
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
