What roadmap is this issue about?

• Frontend Roadmap
• Backend Roadmap
• DevOps Roadmap
• All Roadmaps

What is this issue about?

• D

We newly uploaded a lookup table including UID, ISO alpha 2, ISO alpha 3, ISO 3-digit, FIPS, and location names used in our Dashboard and GitHub. The UID is a combination of ISO numeric code, FIPS, and some artificial numbers. This table will be updated along with more locations joining in. T

I make a lot of commits with small changes

We should have a common format for describing tunes (series of beeps) across the different implementations in this repository. Extensive searching was done, a simple widespread standard was not found.

Following is proposed:

1. Simple text file
2. Each line represents a beep or a pause
   1. Column one is a positive integer number of milliseconds
   2. Column two is a positive integer freque

I would like to drop Spring Boot support for 1.5.x. It is EOL https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019
I would also add some notes in the docs, that we adhere to the spring boot lifecycle in order to be transparent about dropping support for versions.

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:

https://github.com/caicloud/nirvana/blob/854a4623c350ca2e71741cc93142f13e2b6afe8a/service/context.go#L208-L211

the original CloseNotifier interface was marked as Deprecated since Go

In this example the generated table of contents doesn't link to the sections on the page, because the headers have anchor tags in them. These should be sanitized out.

When incorporating new libraries into opensim-core, the library is assumed to have some specific layout (platform dependent). That typically includes "cmake" folder and have specific contents in this folder that defines include and lib paths etc.
If this is documented somewhere that would be great (appreciate a link here for future reference), if not we need to document these requirements so tha

would be nice to execute all the doc notebooks during a test suite execution to increase our coverage.