Re: [DISCUSSION] Moving NimBLE to separate project

Hi Szymon, On Thu, Mar 15, 2018 at 12:57 PM, Szymon Janc wrote: > Hi Andrzej, > > On Monday, 12 March 2018 15:30:52 CET Andrzej Kaczmarek wrote: >> Hi, >> >> I created PR for apache-mynewt-core which removes NimBLE code and adds >> dependency to apache-mynewy-nimble

Re: [DISCUSSION] Moving NimBLE to separate project

On Tue, Feb 27, 2018 at 08:39:04AM -0800, Christopher Collins wrote: > I agree with others that the best option is 2a > (@apache-mynewt-core/net/nimble* become empty packages that pull in the > external nimble packages). However, newt doesn't currently support repo > dependencies; if a repo is

Re: [DISCUSSION] Moving NimBLE to separate project

I agree with others that the best option is 2a (@apache-mynewt-core/net/nimble* become empty packages that pull in the external nimble packages). However, newt doesn't currently support repo dependencies; if a repo is not specified in the user's `project.yml` file, then newt won't download it.

Re: [DISCUSSION] Moving NimBLE to separate project

Hi, 1. I'm fine with doing it either before or after 1.4. We just need to make sure update works correctly for 1.4 if we do it before. 2. I'd go with 2a as Will, no need to keep duplicated code around. 3. Agree with Will, lets start with 1.0 NimBLE release. Only the first release needs to be

Re: [DISCUSSION] Moving NimBLE to separate project

My thoughts: 1. Since the 1.4 release is coming up very quickly I would do this for 1.5 (personally). 2. I would choose 2a. 3. Seems a bit confusing to me to label nimBLE releases with same number as Mynewt releases. Why not just make the first stable release of nimBLE 1.0? Not a big deal

[DISCUSSION] Moving NimBLE to separate project

Hi all, As some of you may already noticed, there is apache/mynewt-nimble repository created where NimBLE code was pushed along with some extra changes, most notably initial attempt to create port of NimBLE for FreeRTOS, but other platforms will be supported as well (native Linux port is also