search

napalm-automation / napalm-ios

Apache License 2.0
31 stars 40 forks source link

Release 0.3.0 #54

Closed ktbyers closed 7 years ago

ktbyers commented 7 years ago

NAPALM-IOS Release 0.3.0

coveralls commented 7 years ago

Coverage Status

Coverage remained the same at 67.834% when pulling b7c98a15254c8699ba01c2a00f96239dd25ff1f4 on ktbyers:devel into d40d7100d17985ba7c7eca5eb2e69f1936b41d1a on napalm-automation:develop.

ktbyers commented 7 years ago

I tested both the config operations and the getter operations against real IOS device as well as the standard unit tests above.

I didn't see any docs on NAPALM release process anywhere. If they exist, just point me to them.

Here is the process I assume I am following:

  1. Create this PR rolling the version to 0.3.0
  2. Once this is approved merged into develop, then create a PR from develop to master
  3. Once the master PR is merged, then create a tag/release and provide some details regarding what is in the release.

I assume the pypi release will happen automatically after push to master, but if there is anything else I need to do here, just let me know.

dbarrosop commented 7 years ago

+1