Skip to content

Drop wheezy variant #466

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

Closed
wants to merge 5 commits into from
Closed

Drop wheezy variant #466

wants to merge 5 commits into from

Conversation

chorrell
Copy link
Contributor

Full support for wheezy ended on April 26, 2016. LTS support will drop
in May 2018:

https://wiki.debian.org/DebianReleases#Production_Releases

We may want to wait until the LTS drop date. However, given the recent
release of Stretch the timing seems appropriate to do it sooner.

Also worth noting is that LTS is not supported by the Debian Security
team but by volunteers and interested companies:

https://wiki.debian.org/LTS

Full support for wheezy ended on April 26, 2016. LTS support will drop
in May 2018:

https://wiki.debian.org/DebianReleases#Production_Releases

We may want to wait until the LTS drop date. However, given the recent
release of Stetch the timing seems approriate to do it sooner.

Also worth noting is that LTS is not supported by the Debian Security
team but by volunteers and interested companies:

https://wiki.debian.org/LTS
@chorrell
Copy link
Contributor Author

Also not I'm not expecting this to land anytime soon. I figure this was an easy way to discuss dropping wheezy and to figure out the timing of same.

@chorrell
Copy link
Contributor Author

chorrell commented Jul 13, 2017

Hmm, no test build. I guess this is because I removed things rather than changed existing files?

¯\_(ツ)_/¯ 

@pesho
Copy link
Contributor

pesho commented Jul 14, 2017

Hmm, no test build. I guess this is because I removed things rather than changed existing files?

It's there on Travis actually. Sometimes test builds don't show here on GitHub, no idea why.

I'd like to see it dropped already myself, but admittedly there may be complaints if we do it before the LTS drop date.

pesho

This comment was marked as off-topic.

SimenB

This comment was marked as off-topic.

@chorrell
Copy link
Contributor Author

Yeah, it would be great to know what kind of usage the wheezy variant gets. I'd prefer to drop it in the next few weeks, to be honest, rather than wait until May of next year (the LTS eol date).

@SimenB
Copy link
Member

SimenB commented Jul 26, 2017

This has conflicts, unsure if it needs to be rebased before we decide to land it, though

@chorrell
Copy link
Contributor Author

Yeah, we won't be landing it anytime soon but I can clean it up in the meantime

@chorrell
Copy link
Contributor Author

POW!

I'll try and periodically keep this up to date.

Christopher Horrell added 2 commits August 1, 2017 09:49
@chorrell
Copy link
Contributor Author

I think maybe it might be better to close this and create an issue instead, with target date of May 2018.

Keeping this in sync for a year isn't really worth the effort

@SimenB
Copy link
Member

SimenB commented Oct 19, 2017

No reason to keep it up to date.

A PR is just as good to track something as an issue, IMO

@SimenB SimenB mentioned this pull request Nov 1, 2017
@chorrell
Copy link
Contributor Author

chorrell commented Nov 1, 2017

I'm not sure what happened, but I lost my remote branch...

@chorrell
Copy link
Contributor Author

chorrell commented Nov 1, 2017

Closing this in favour of #567

@chorrell chorrell closed this Nov 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants