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: doc/internal/release.rst
+12-10
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@ This document is only meant for the project administrators, not users and develo
17
17
18
18
e. update the README and this release documentation, if necessary.
19
19
20
-
3. Build the new conda package using the following command::
20
+
3. Run the following command in the ``conda-recipe`` directory to build the conda package::
21
21
22
-
conda build -c conda-forge --numpy=1.17 skll
22
+
conda build -c conda-forge --numpy=1.17 .
23
23
24
24
4. Upload the package to anaconda.org using ``anaconda upload --user ets <package tarball>``. You will need to have the appropriate permissions for the ``ets`` organization.
25
25
@@ -35,18 +35,20 @@ This document is only meant for the project administrators, not users and develo
35
35
36
36
9. Then run some SKLL examples or tests from a SKLL working copy. If the TestPyPI package works, then move on to the next step. If it doesn't, figure out why and rebuild and re-upload the package.
37
37
38
-
10. Upload source package to main PyPI using ``python setup.py sdist upload``.
38
+
10. Create pull requests on the `skll-conda-tester <https://github.com/EducationalTestingService/skll-conda-tester/>`_ and `skll-pip-tester <https://github.com/EducationalTestingService/skll-pip-tester/>`_ repositories to test the conda and TestPyPI packages on Linux and Windows.
39
39
40
-
11. Draft a release on GitHub.
40
+
11. Draft a release on GitHub while the Linux and Windows package tester builds are running.
41
41
42
-
12. Make a pull request with the release branch to be merged into ``master`` and request code review.
42
+
12. Once both builds have passed, make a pull request with the release branch to be merged into ``master`` and request code review.
43
43
44
-
13. Once the Travis (Linux) and Appveyor (Windows) builds for the PR pass and the reviewers approve, merge the release branch into ``master``.
44
+
13. Once the build for the PR passes and the reviewers approve, merge the release branch into ``master``.
45
45
46
-
14. Make sure that the ReadTheDocs build for ``master`` passes.
46
+
14. Upload source and wheel packages to PyPI using ``python setup.py sdist upload`` and ``python setup.py bdist_wheel upload``
47
47
48
-
15. Tag the latest commit in ``master`` with the appropriate release tag and publish the release on GitHub.
48
+
15. Make sure that the ReadTheDocs build for ``master`` passes.
49
49
50
-
16. Send an email around at ETS announcing the release and the changes.
50
+
16. Tag the latest commit in ``master`` with the appropriate release tag and publish the release on GitHub.
51
51
52
-
17. Post release announcement on Twitter/LinkedIn.
52
+
17. Send an email around at ETS announcing the release and the changes.
53
+
54
+
18. Post release announcement on Twitter/LinkedIn.
0 commit comments