You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+28-4Lines changed: 28 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,17 @@
2
2
3
3
Vultr is a client library for the Vultr API.
4
4
5
-
## Bug Reports
5
+
## Bug Reports
6
6
7
7
Please report bugs through the github issue queue. When reporting a bug please include a code sample, describe the behavior you expect, and the behavior you're observing.
8
8
9
9
## Contributing Code
10
10
11
-
Vultr is maintained on Github. Changes should be submitted as pull requests rebased on the latest master.
11
+
Vultr is maintained on Github. Changes should be submitted as pull requests rebased on the latest master.
12
12
13
13
## Becoming a Maintainer
14
14
15
-
Please send an email to darrel.opry@spry-group.com if you are interested in becoming a maintainer. Like all open source projects, the more hands the merrier.
15
+
Please send an email to darrel.opry@spry-group.com if you are interested in becoming a maintainer. Like all open source projects, the more hands the merrier.
16
16
17
17
## Development
18
18
@@ -21,4 +21,28 @@ Please send an email to darrel.opry@spry-group.com if you are interested in beco
21
21
22
22
```
23
23
24
-
## Testing
24
+
## Testing
25
+
26
+
Tests spawn and destroy instances labelled 'python-vultr: test'
27
+
28
+
I highly recommend you setup a Vultr account specifically for integration testing with
29
+
this library to avoid unintentionally destroying servers you need.
30
+
31
+
Be sure to clean up your Vultr account when done.
32
+
33
+
```
34
+
python setup.py test
35
+
```
36
+
37
+
## Release Process
38
+
39
+
Releases are tracked by creating a pull request from master to release. Ensure the version has been properly upticked before creating the release candidate pull request. The merged commit should be tagged with the proper version and built and uploaded to pypi. Currently the release process is manual. Once a more mature testing suite in place, it should be automated with TravisCI.
40
+
41
+
```
42
+
python setup.py sdist
43
+
python setup.py bdist_wheel
44
+
python setup.py sdist upload -r pypi
45
+
python setup.py bdist_wheel upload -r pypi
46
+
```
47
+
48
+
based on: [Sharing Your Labor of Love: PyPI Quick and Dirty](https://hynek.me/articles/sharing-your-labor-of-love-pypi-quick-and-dirty/)
0 commit comments