You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Christopher Collins <cc...@apache.org> on 2016/12/03 02:43:11 UTC

[VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Hello all,

I am pleased to be calling this vote for the source release of Apache
Mynewt 1.0.0, beta 1 (rc2).  This is the second release candidate for
Mynewt 1.0.0-b1.  The vote for the first release candidate was cancelled
due to licensing issues with third-party bundled software.  Details
concerning what has changed since the previous release candidate can be
found at the end of this email.

Apache Mynewt is a community-driven, permissively licensed open source
initiative for constrained, embedded applications. Mynewt provides a
real-time operating system, flash file system, network stacks, and
support utilities for real-world embedded systems.

For full release notes, please visit the Apache Mynewt Wiki:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+Notes

[VOTE] thread:
https://lists.apache.org/thread.html/bb3e334e9b3b6b95247e46cca8b95e853f26cc9bb65a289f576dcef1@%3Cdev.mynewt.apache.org%3E

[RESULT][VOTE] thread:
https://lists.apache.org/thread.html/5a6aeb397cf5e0277aca91a34db221921d576725dcfa183abfa23da0@%3Cdev.mynewt.apache.org%3E

[DISCUSS] thread:
https://lists.apache.org/thread.html/e9f2bc01ac4257282c32116d91dc1d4064d428a99b1cc181c8a55980@%3Cdev.mynewt.apache.org%3E

This release candidate was tested as follows:
    1. Manual execution of the Mynewt test plan:
       https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan
       The test results can be found at:
       https://cwiki.apache.org/confluence/display/MYNEWT/1.0.0-b1+Test+Results

    2. The full unit test suite for this release was executed via "newt
       test all" with no failures.  This testing was performed on the
       following platforms:
         * OS X 10.10.5
         * Linux 4.4.6 (Gentoo)

The release candidate to be voted on is available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-b1-incubating/rc2/

The commits under consideration are as follows:

blinky:
    repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky
    commit: b6918edc174b764f1e0b4ef4f4652aca8fedf8dd

core:
    repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-core
    commit: c6a8f88f6b8dc7c8eee6dc75a34c9b6ea295b05d

newt:
    repos: https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
    commit: 59ec3af372952382390cfd988e503d8cf3d5b34b

In addition, the following newt convenience binaries are available:
    linux: https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-b1-incubating/rc2/apache-mynewt-newt-bin-linux-1.0.0-b1-incubating.tgz
    osx: https://dist.apache.org/repos/dist/dev/incubator/mynewt/apache-mynewt-1.0.0-b1-incubating/rc2/apache-mynewt-newt-bin-osx-1.0.0-b1-incubating.tgz


The release candidate is signed with a GPG key available at:
https://dist.apache.org/repos/dist/dev/incubator/mynewt/KEYS

The vote is open for at least 72 hours and passes if a majority of at
least three +1 PPMC votes are cast.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...

The vote is open for at least 72 hours and passes if a majority of at
least three +1 PPMC votes are cast.

As indicated, here is a list of issues with the previous release
candidate (rc1) that have been resolved:
    * Pointers for several third-party libraries added to the LICENSE
      files.
    * Some acknowledgements added to core's NOTICE file, as required by
      the licensing terms of some bundled third-party software.
    * Removal of third-party files with licenses that are incompatible
      with an Apache project.  Specifically:
        * net/ip/lwip_base/include/netif/ppp/pppoe.h
        * net/ip/lwip_base/include/netif/ppp/vj.h
        * net/ip/lwip_base/src/netif/ppp/pppoe.c
        * net/ip/lwip_base/src/netif/ppp/vj.c
      These files specified a 4-clause BSD license (or equivalent).

Thanks,
Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by Ian Dunlop <ia...@gmail.com>.
Hello,

gcc on Ubuntu 16.04 x64

Cheers,

Ian


On 07/12/16 17:21, aditi hilbert wrote:
> Ian,
>
> Thanks for the suggestions - very useful!
> Which platform OS version were you testing on? gcc or clang?
>
> thanks,
> aditi
>
>> On Dec 7, 2016, at 4:40 AM, Ian Dunlop <ia...@gmail.com> wrote:
>>
>> Hello,
>>
>> +1 non-binding
>>
>> I checked:
>>
>> - incubating in name
>>
>> - hashes correct
>>
>> - Can compile from source for newt and blinky. All tests run for core.
>>
>> Here are a few things I noticed when checking that don't affect the
>> release but might help if added to docs in future:
>>
>> 1) Should point out type of sha sum somehow. Perhaps in the .sha file.
>> Could call it .sha512
>> 2) http://mynewt.apache.org/os/get_started/introduction/ referenced in
>> blinky README is missing. Found introduction at os/introduction and
>> build instructions via os/get_started/get_started/ which took me to
>> http://mynewt.apache.org/os/get_started/native_tools/
>> 3) In stage 4 of build newt on
>> http://mynewt.apache.org/os/get_started/native_tools/ you have to export
>> the newt path before you can run it. I think this needs to be pointed
>> out just after the build instructions, not in the bracketed part after
>> telling you to run 'newt'.
>> 4) export newt="go run $GOPATH/mynewt.apache.org/newt/newt/newt.go"
>> seems wrong on my machine since GOPATH would need /src included. Should
>> possibly be export newt="go run
>> $GOPATH/src/mynewt.apache.org/newt/newt/newt.go"
>>
>> Not everything seems to work with newt test all, here is what happened
>> for me:
>>
>> blinky - $newt test all - 'no testable packages found'. Installed with
>> $newt install && $newt build my_blinky_sim
>> core - $newt test all - all tests passed. I wasn't sure if you could
>> actually build this from the root directory or had to build each
>> individual project.
>> newt - $newt test all - 'Error: No project file found!' I successfully
>> built it with ./build.sh
>>
>> Cheers,
>>
>> Ian
>>
>> On 05/12/16 02:37, Sterling Hughes wrote:
>>> +1 binding.
>>>
>>> On 4 Dec 2016, at 16:58, Justin Mclean wrote:
>>>
>>>> Hi,
>>>>
>>>> +1 binding
>>>>
>>>> I checked:
>>>> - incubating in name
>>>> - signatures and hashes correct
>>>> - DISCLAIMER exists
>>>> - LICENSE and NOTICE good
>>>> - All source file have apache headers
>>>> - No unexpected binaries
>>>> - Can compile from source
>>>>
>>>> A couple of minor things re compilation which other people may run into:
>>>> 1. It would be good to have better compile instructions especially
>>>> for the core package.
>>>> 2. It seems that blinky expects gcc-5 in /usr/local/bin/ and I only
>>>> had gcc-6 installed and an older version of gcc in /usr/bin/gcc
>>>> 3. A newt build all in core does nothing, but a newt test all goes
>>>> off and compiles and runs the tests. Is that expected? How do you
>>>> just build core?
>>>>
>>>> Thanks,
>>>> Justin
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by aditi hilbert <ad...@runtime.io>.
Ian,

Thanks for the suggestions - very useful!
Which platform OS version were you testing on? gcc or clang?

thanks,
aditi

> On Dec 7, 2016, at 4:40 AM, Ian Dunlop <ia...@gmail.com> wrote:
> 
> Hello,
> 
> +1 non-binding
> 
> I checked:
> 
> - incubating in name
> 
> - hashes correct
> 
> - Can compile from source for newt and blinky. All tests run for core.
> 
> Here are a few things I noticed when checking that don't affect the
> release but might help if added to docs in future:
> 
> 1) Should point out type of sha sum somehow. Perhaps in the .sha file.
> Could call it .sha512
> 2) http://mynewt.apache.org/os/get_started/introduction/ referenced in
> blinky README is missing. Found introduction at os/introduction and
> build instructions via os/get_started/get_started/ which took me to
> http://mynewt.apache.org/os/get_started/native_tools/
> 3) In stage 4 of build newt on
> http://mynewt.apache.org/os/get_started/native_tools/ you have to export
> the newt path before you can run it. I think this needs to be pointed
> out just after the build instructions, not in the bracketed part after
> telling you to run 'newt'.
> 4) export newt="go run $GOPATH/mynewt.apache.org/newt/newt/newt.go"
> seems wrong on my machine since GOPATH would need /src included. Should
> possibly be export newt="go run
> $GOPATH/src/mynewt.apache.org/newt/newt/newt.go"
> 
> Not everything seems to work with newt test all, here is what happened
> for me:
> 
> blinky - $newt test all - 'no testable packages found'. Installed with
> $newt install && $newt build my_blinky_sim
> core - $newt test all - all tests passed. I wasn't sure if you could
> actually build this from the root directory or had to build each
> individual project.
> newt - $newt test all - 'Error: No project file found!' I successfully
> built it with ./build.sh
> 
> Cheers,
> 
> Ian
> 
> On 05/12/16 02:37, Sterling Hughes wrote:
>> +1 binding.
>> 
>> On 4 Dec 2016, at 16:58, Justin Mclean wrote:
>> 
>>> Hi,
>>> 
>>> +1 binding
>>> 
>>> I checked:
>>> - incubating in name
>>> - signatures and hashes correct
>>> - DISCLAIMER exists
>>> - LICENSE and NOTICE good
>>> - All source file have apache headers
>>> - No unexpected binaries
>>> - Can compile from source
>>> 
>>> A couple of minor things re compilation which other people may run into:
>>> 1. It would be good to have better compile instructions especially
>>> for the core package.
>>> 2. It seems that blinky expects gcc-5 in /usr/local/bin/ and I only
>>> had gcc-6 installed and an older version of gcc in /usr/bin/gcc
>>> 3. A newt build all in core does nothing, but a newt test all goes
>>> off and compiles and runs the tests. Is that expected? How do you
>>> just build core?
>>> 
>>> Thanks,
>>> Justin
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by Ian Dunlop <ia...@gmail.com>.
Hello,

+1 non-binding

I checked:

 - incubating in name

 - hashes correct

 - Can compile from source for newt and blinky. All tests run for core.

Here are a few things I noticed when checking that don't affect the
release but might help if added to docs in future:

1) Should point out type of sha sum somehow. Perhaps in the .sha file.
Could call it .sha512
2) http://mynewt.apache.org/os/get_started/introduction/ referenced in
blinky README is missing. Found introduction at os/introduction and
build instructions via os/get_started/get_started/ which took me to
http://mynewt.apache.org/os/get_started/native_tools/
3) In stage 4 of build newt on
http://mynewt.apache.org/os/get_started/native_tools/ you have to export
the newt path before you can run it. I think this needs to be pointed
out just after the build instructions, not in the bracketed part after
telling you to run 'newt'.
4) export newt="go run $GOPATH/mynewt.apache.org/newt/newt/newt.go"
seems wrong on my machine since GOPATH would need /src included. Should
possibly be export newt="go run
$GOPATH/src/mynewt.apache.org/newt/newt/newt.go"

Not everything seems to work with newt test all, here is what happened
for me:

blinky - $newt test all - 'no testable packages found'. Installed with
$newt install && $newt build my_blinky_sim
core - $newt test all - all tests passed. I wasn't sure if you could
actually build this from the root directory or had to build each
individual project.
newt - $newt test all - 'Error: No project file found!' I successfully
built it with ./build.sh

Cheers,

Ian

On 05/12/16 02:37, Sterling Hughes wrote:
> +1 binding.
>
> On 4 Dec 2016, at 16:58, Justin Mclean wrote:
>
>> Hi,
>>
>> +1 binding
>>
>> I checked:
>> - incubating in name
>> - signatures and hashes correct
>> - DISCLAIMER exists
>> - LICENSE and NOTICE good
>> - All source file have apache headers
>> - No unexpected binaries
>> - Can compile from source
>>
>> A couple of minor things re compilation which other people may run into:
>> 1. It would be good to have better compile instructions especially
>> for the core package.
>> 2. It seems that blinky expects gcc-5 in /usr/local/bin/ and I only
>> had gcc-6 installed and an older version of gcc in /usr/bin/gcc
>> 3. A newt build all in core does nothing, but a newt test all goes
>> off and compiles and runs the tests. Is that expected? How do you
>> just build core?
>>
>> Thanks,
>> Justin
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by Sterling Hughes <st...@apache.org>.
+1 binding.

On 4 Dec 2016, at 16:58, Justin Mclean wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - incubating in name
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - All source file have apache headers
> - No unexpected binaries
> - Can compile from source
>
> A couple of minor things re compilation which other people may run 
> into:
> 1. It would be good to have better compile instructions especially for 
> the core package.
> 2. It seems that blinky expects gcc-5 in /usr/local/bin/ and I only 
> had gcc-6 installed and an older version of gcc in /usr/bin/gcc
> 3. A newt build all in core does nothing, but a newt test all goes off 
> and compiles and runs the tests. Is that expected? How do you just 
> build core?
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by "David G. Simmons" <sa...@mac.com>.
+1 

> On Dec 5, 2016, at 5:27 PM, Christopher Collins <cc...@apache.org> wrote:
> 
> I just tried running "newt test all" using clang, and it mostly works.
> There are a few warnings that get reported, but they should be easy to
> fix.  My thought it is that we should fix the warnings and change the
> compiler definition such that the "gcc" binary (i.e., clang) is used in
> OS X.  It's unfortunate that this ambiguity exists, but I think it's
> preferable to just use clang than to impose these gcc version headaches
> on the user.

--
David G. Simmons
(919) 534-5099
Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs>
/** Message digitally signed for security and authenticity.  
* If you cannot read the PGP.sig attachment, please go to 
 * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!!
 * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/>
**/
♺ This email uses 100% recycled electrons. Don't blow it by printing!

There are only 2 hard things in computer science: Cache invalidation, naming things, and off-by-one errors.

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> To get started, a user should also acquire
> the blinky repository by using the "newt new" command.  Blinky includes
> a sample target for running the blinky application in a simulated
> environment.

The issue I had here is that it will download it from git rather than used the local released artefact I was trying to test.

> For the next release, I think we should clarify this in the core README file. 

I think that will help.

> I think it’s preferable to just use clang than to impose these gcc version headaches
> on the user.

Seem’s the easiest way to get people started on OSX.

Thanks,
Justin

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by aditi hilbert <ad...@runtime.io>.
We do talk about dealing with gcc versions (that the default expectation is gcc-5 but can be changed) in the documentation for native tool installation.

https://mynewt.apache.org/latest/os/get_started/native_tools/

thanks,
aditi

> 
>> 2. It seems that blinky expects gcc-5 in /usr/local/bin/ and I only had gcc-6 installed and an older version of gcc in /usr/bin/gcc
> 
> Hmm, this is indeed a problem.  On OS X, /usr/bin/gcc is not actually
> gcc; it's clang.  I don't recall the details, but I believe there was a
> time when clang was incompatible with Mynewt.  "gcc-5" is the name of
> the gcc 5.x binary that home brew installs, so that is what newt looks
> for.
>

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by Christopher Collins <cc...@apache.org>.
(The email I'm responding is from general@. I'm replying in dev@, as all
my comments concern Mynewt specifically.  For those who don't follow
general@, in the original email, Justin voted +1 on 1.0.0-b1-rc2, but he
raised a few issues that I believe warrant a closer look.)

Hi Justin,

Thanks for taking a look.  I want to address the three issues you
raised.  I reordered them slightly, as issues 1 and 3 are closely
related.

On Mon, Dec 05, 2016 at 11:58:58AM +1100, Justin Mclean wrote:
[...]
> A couple of minor things re compilation which other people may run into:
> 1. It would be good to have better compile instructions especially for the core package. 
> 3. A newt build all in core does nothing, but a newt test all goes off and compiles and runs the tests. Is that expected? How do you just build core?

Yes - I believe this has been a point of confusion in some earlier
releases as well.  I think Mynewt might be atypical this regard, and
we should address this in the core README file.  Specifically, core is
not something that can be built directly; it is a collection of
libraries and sample applications that a user's project depends on.

The "newt build all" command doesn't do anything in a bare
apache-mynewt-core repo because there are no targets to build.  A target
is the top-level Mynewt entity that actually gets built; it ties a BSP
and an application together.  To get started, a user should also acquire
the blinky repository by using the "newt new" command.  Blinky includes
a sample target for running the blinky application in a simulated
environment.

For the next release, I think we should clarify this in the core README
file.  We should make it very clear to the user what they have
downloaded, and indicate how to proceed.

> 2. It seems that blinky expects gcc-5 in /usr/local/bin/ and I only had gcc-6 installed and an older version of gcc in /usr/bin/gcc

Hmm, this is indeed a problem.  On OS X, /usr/bin/gcc is not actually
gcc; it's clang.  I don't recall the details, but I believe there was a
time when clang was incompatible with Mynewt.  "gcc-5" is the name of
the gcc 5.x binary that home brew installs, so that is what newt looks
for.

I just tried running "newt test all" using clang, and it mostly works.
There are a few warnings that get reported, but they should be easy to
fix.  My thought it is that we should fix the warnings and change the
compiler definition such that the "gcc" binary (i.e., clang) is used in
OS X.  It's unfortunate that this ambiguity exists, but I think it's
preferable to just use clang than to impose these gcc version headaches
on the user.

Thanks,
Chris

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

+1 binding

I checked:
- incubating in name
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE and NOTICE good
- All source file have apache headers
- No unexpected binaries
- Can compile from source

A couple of minor things re compilation which other people may run into:
1. It would be good to have better compile instructions especially for the core package. 
2. It seems that blinky expects gcc-5 in /usr/local/bin/ and I only had gcc-6 installed and an older version of gcc in /usr/bin/gcc
3. A newt build all in core does nothing, but a newt test all goes off and compiles and runs the tests. Is that expected? How do you just build core?

Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [VOTE] Release Apache Mynewt 1.0.0-b1-incubating-rc2

Posted by Greg Stein <gs...@gmail.com>.
On Fri, Dec 2, 2016 at 8:43 PM, Christopher Collins <cc...@apache.org>
wrote:
>...

> The release candidate to be voted on is available at:
> https://dist.apache.org/repos/dist/dev/incubator/mynewt/
> apache-mynewt-1.0.0-b1-incubating/rc2/

>...

> The vote is open for at least 72 hours and passes if a majority of at
> least three +1 PPMC votes are cast.
>
> [ ] +1 Release this package
> [ ]  0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>

+1 (binding)