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

Add Astropy to list of signatories #47

Merged
merged 3 commits into from Aug 24, 2016

Conversation

@astrofrog
Copy link
Contributor

@astrofrog astrofrog commented Aug 22, 2016

The Astropy community has now approved APE 10, which describes the roadmap for releases until 2020, as well as which releases will drop support for Python 2:

https://github.com/astropy/astropy-APEs/pull/13/files

@eteq @taldcroft @kelle - could at least one of you double check this? (especially the dates)

Based on other PRs, I saw the projects are ordered by stars in the project list. Should the order be the same in site.js?

@takluyver
Copy link
Member

@takluyver takluyver commented Aug 23, 2016

Thanks, this looks good to me. I'm happy to merge once one of the people you tagged has had a look.

Yes, I think it makes sense for the project order in the timeline to match that in the list of logos. But I'd like to find a better way to display the timeline information entirely - see #46.

@taldcroft
Copy link

@taldcroft taldcroft commented Aug 23, 2016

I've checked the dates and they match APE-10 and my expectations. Note that I did not run this locally.

@astrofrog
Copy link
Contributor Author

@astrofrog astrofrog commented Aug 23, 2016

Just to confirm, I ran this locally and it all works fine:

screen shot 2016-08-23 at 5 23 11 pm

timeline

@astrofrog
Copy link
Contributor Author

@astrofrog astrofrog commented Aug 23, 2016

@takluyver - now @taldcroft has confirmed this looks ok, I think this is good to go

site.js Outdated
{content: '1.0 LTS', start: '2015-02-19', end: '2017-06-01', py2:true},
{content: '1.1', start: '2015-12-11', end: '2016-06-23', py2:true},
{content: '1.2', start: '2016-06-23', end: '2016-12-01', py2:true},
{content: '1.3', start: '2016-12-01', end: '2017-06-01', py2:true},

This comment has been minimized.

@eteq

eteq Aug 23, 2016

1.3 "start" (and the "end" of 1.2) should probably be '2016-12-16', as that's what we currently have as the release date on https://github.com/astropy/astropy/wiki/Release-Calendar

This comment has been minimized.

@astrofrog

astrofrog Aug 23, 2016
Author Contributor

Thanks, fixed!

@eteq
Copy link

@eteq eteq commented Aug 23, 2016

Looks good to me too, @astrofrog, except for the minor tweak I just suggested above.

@Carreau
Copy link
Member

@Carreau Carreau commented Aug 23, 2016

It's great ! Have been working hard to get some change into PyPI legacy, right now we are hitting a PgSQL bottle neck, so if anyone as experience with SQL to optimize queries...

@takluyver
Copy link
Member

@takluyver takluyver commented Aug 24, 2016

Thanks, and welcome on board :-)

@takluyver takluyver merged commit ca36cf4 into python3statement:master Aug 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

5 participants
You can’t perform that action at this time.