Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changelog update #570

Merged
merged 20 commits into from Jun 5, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions .circleci/config.yml
Expand Up @@ -104,6 +104,13 @@ jobs:
cd ../
cp "featuretools-${FEATURETOOLS_VERSION}/.coverage" .coverage
codecov
"changelog_updated":
working_directory: ~/featuretools
docker:
- image: circleci/python:3.7
steps:
- checkout
- run: cat docs/source/changelog.rst | grep ":pr:\`${CIRCLE_PULL_REQUEST##https://github.com/Featuretools/featuretools/pull/}\`"

workflows:
version: 2
Expand All @@ -113,3 +120,6 @@ workflows:
- "python-35"
- "python-36"
- "python-37"
changelog_updated:
jobs:
- "changelog_updated"
11 changes: 10 additions & 1 deletion contributing.md
Expand Up @@ -53,7 +53,16 @@ Before starting major work, you should touch base with the maintainers of Featur

#### 3. Submit your Pull Request

* Once your changes are ready to be submitted, make sure to push your changes to GitHub before creating a pull request. Create a pull request, and our continuous integration will run automatically. We will review your changes, and you will most likely be asked to make additional changes before it is finally ready to merge. However, once it's reviewed by a maintainer of Featuretools, passes continuous integration, we will merge it, and you will have successfully contributed to Featuretools!
* Once your changes are ready to be submitted, make sure to push your changes to GitHub before creating a pull request. Create a pull request, and our continuous integration will run automatically.
* Update the "Future Release" section of the changelog (`docs/source/changelog.rst`) to include your pull request and add your github username to the list of contributors. Add a description of your PR to the subsection that most closely matches your contribution:
* Enhancements: new features or additions to Featuretools.
* Fixes: things like bugfixes or adding more descriptive error messages.
* Changes: modifications to an existing part of Featuretools.
* Documentation Changes
* Testing Changes

Documentation or testing changes rarely warrant an individual changelog entry; the PR number can be added to their respective "Miscellaneous changes" entries.
* We will review your changes, and you will most likely be asked to make additional changes before it is finally ready to merge. However, once it's reviewed by a maintainer of Featuretools, passes continuous integration, we will merge it, and you will have successfully contributed to Featuretools!

## Report issues
When reporting issues please include as much detail as possible about your operating system, featuretools version and python version. Whenever possible, please also include a brief, self-contained code example that demonstrates the problem.
5 changes: 5 additions & 0 deletions docs/pull_request_template.md
@@ -0,0 +1,5 @@
### Pull Request Description
(replace this text with your description)

-----
*After creating the pull request: in order to pass the **changelog_updated** check you will need to update the "Future Release" section of* `docs/source/changelog.rst` *to include this pull request.*
21 changes: 21 additions & 0 deletions docs/source/changelog.rst
Expand Up @@ -2,6 +2,27 @@

Changelog
---------
**Future Release**
* Enhancements
* Add unit parameter to timesince primitives (:pr:`558`)
* Add ability to install optional add on libraries (:pr:`551`)
* Load and save features from open files and strings (:pr:`566`)
* Support custom variable types (:pr:`571`)
* Fixes
* Normalize_entity specifies error when 'make_time_index' is an invalid string (:pr:`550`)
* Changes
* Refactor get_pandas_data_slice to take single entity (:pr:`547`)
* Updates TimeSincePrevious and Diff Primitives (:pr:`561`)
* Remove unecessary time_last variable (:pr:`546`)
* Documentation Changes
* Add Featuretools Enterprise to documentation (:pr:`563`)
* Miscellaneous changes (:pr:`552`, :pr:`573`, :pr:`577`)
* Testing Changes
* Miscellaneous changes (:pr:`559`, :pr:`569`, :pr:`570`, :pr:`574`)

Thanks to the following people for contributing to this release:
:user:`allisonportis`, :user:`CJStadler`, :user:`ctduffy`, :user:`gsheni`, :user:`kmax12`, :user:`rwedge`

**v0.8.0** May 17, 2019
* Rename NUnique to NumUnique (:pr:`510`)
* Serialize features as JSON (:pr:`532`)
Expand Down
2 changes: 1 addition & 1 deletion docs/source/getting_started/install.rst
Expand Up @@ -54,7 +54,7 @@ of ``setup.py``.

Development
-----------
Before making contributing to the codebase, please follow the guidelines `here <https://github.com/Featuretools/featuretools/blob/master/docs/contributing.md>`_
Before making contributing to the codebase, please follow the guidelines `here <https://github.com/Featuretools/featuretools/blob/master/contributing.md>`_

Virtualenv
~~~~~~~~~~
Expand Down