Changes between Version 13 and Version 14 of AddOns


Ignore:
Timestamp:
06/19/12 13:02:14 (2 years ago)
Author:
mitar
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • AddOns

    v13 v14  
    9595=== Initial release === 
    9696 
     97For your first release of Orange add-on: 
     98 1. make sure code is ready 
     99 2. make sure your documentation is ready, that index explains what add-on is and does and how can be installed and used 
     100 3. compare your `setup.py` with one of Biolab's add-ons (like bioinformatics add-on) 
     101   1. make sure entry points (hooks) are defined properly 
     102   2. package must have keyword `orange add-on` for it to be displayed on add-ons list 
     103 4. prepare `README.rst` file which should be included in `setup.py` as long description of the package -- this will be used on the list of add-ons, it is useful that there is some link to documentation in there 
     104 5. commit everything 
     105 6. increase version in `setup.py` (commit message is often just `Version bump.`) 
     106 7. commit 
     107 8. tag the commit with (`hg tag <version string>`) 
     108 9. push to Bitbucket 
     109 10. register on ReadTheDocs and import your new Python pacage 
     110    1. for tags use also `orange` and `data mining` 
     111 11. on Bitbucket enable service integration with ReadTheDocs for your package repository, so that every time you push to the repository, documentation will be rebuild 
     112 12. publish package on PyPi (you will be prompted to register an account, if you do not have one) 
     113   1. `python setup.py register` 
     114   2. `python setup.py sdist upload` 
     115   3. `python2.6 setup.py bdist_egg upload` 
     116   4. `python2.7 setup.py bdist_egg upload` 
     117 13. In around one hour it should be visible on add-ons list. 
     118 
    97119=== Subsequent releases === 
    98120 
    99121When a new release is ready: 
    100  1. increase version in `setup.py` 
     122 1. increase version in `setup.py` (commit message is often just `Version bump.`) 
    101123 2. commit 
    102124 3. tag the commit with (`hg tag <version string>`)