:)
Hey all -
I wanted to get a few more opinions on this. We're going to need to
change some repositories around on the newt/newtmgr side (Chris/Todd,
can you send a summary to the list?)
I'd like to get this all done at once. I don't think we need a formal
vote on this one, but just lazy consensus. My suggestion is that Chris
send a summary of the go changes, and we leave this open till Sunday.
If anyone has objections before then, we can stop & vote.
Also, we have our last few features/changes coming in this week. So, we
should uncharacteristically have a few days to poke around at the
release prior to releasing B2.
Sterling
On 3/3/16 4:09 AM, Jim Jagielski wrote:
Maintaining the precedent also becomes more painful as
things move forward :)
On Mar 2, 2016, at 6:28 PM, Sterling Hughes <sterl...@apache.org> wrote:
Howdy,
Awhile ago we decided to be cute about naming things: eggs, eggshells,
clutches, etc. One holdover from this was larva: our main package repository,
which includes the OS and most of the packages.
While its painful to rename the git repo: it's only going to get more painful
as we move forward. Do we think it makes sense to make it clearer, and rename
this to apache-mynewt-os or apache-mynewt-main?
Sterling
