Skip to content

Add Spyder to project list and timeline #141

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Jul 28, 2018
Merged

Add Spyder to project list and timeline #141

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
315a467
Add Spyder to participating projects list with logo
CAM-Gerlach Jul 27, 2018
cd33efd
Add Spyder project to timeline
CAM-Gerlach Jul 27, 2018
a3539a5
Update Spyder timeline dates based on maintainer input
CAM-Gerlach Jul 27, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions _sections/30-projects.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ These projects pledge to drop Python 2 support in or before 2020.
- [![](assets/zulip.png)Zulip](https://zulip.org)
- [![](assets/sympy.png)SymPy](http://www.sympy.org/)
- [![](assets/jupyter.png)Jupyter notebook](https://jupyter.org)
- [![](assets/spyder.png)Spyder](https://www.spyder-ide.org)
- [![](assets/scikit-image.png)Scikit Image](http://scikit-image.org/)
- [![](assets/pymc3.png)PyMC3](https://github.com/pymc-devs/pymc3)
- [![](assets/tensorpack.png)Tensorpack](https://github.com/tensorpack/tensorpack)
Expand Down
Binary file added assets/spyder.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 5 additions & 0 deletions site.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,11 @@ $(document).ready(function (){
{content: '3.1', start: '2019-01-01', end: '2019-07-01'},
{content: '3.2', start: '2019-07-01', end: '2020-01-01'}
],
'Spyder':[
{content: '3', start: '2016-09-24', end: '2019-03-01', py2:true},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the end date of our 3 series is going to be 2018-12-01.

Copy link
Contributor Author

@CAM-Gerlach CAM-Gerlach Jul 27, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that defines the "support" date as the day of the last scheduled release, unlike the convention followed by every other project on this list, and it will leave a gap between them, rather than being supported at least until the release of the following version (i.e. leaving no version of Spyder "supported" during the transition period). Even if the last scheduled release is on that date, we would naturally support Spyder 3 (e.g. via Github, Gitter, Google Groups, Docs, and possibly emergency fixes if necessary) at least until the release of Spyder 4. It wouldn't make any sense to do otherwise.

Therefore, I propose an end date of at least 2019-01-15, the same day on which Spyder 4 is scheduled for release (although at least in practice, we'd want to consider the delay to get conda packages out, possible emergency fixes, at least some latency in all users upgrading to a new major version on the day of its release, etc.).

{content: '4', start: '2019-02-01', end: '2020-02-01', py2:true},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be start: 2019-01-15, end: 2019-12-15

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Following the above reasoning, we would want to shift the end date to at least the start date of the next version, 2019-12-31.

{content: '5', start: '2019-12-31', end: '2021-12-16'}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is good!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

],
'Xonsh':[
{content: '0.x series – Python 3.4+', start: '2015-03-09', end: '2021-12-16'},
],
Expand Down