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

MR14: Update "Maintained" to 2019 for DockerHub README #28010

Closed
sagetrac-gitlab-bot mannequin opened this issue Jun 18, 2019 · 10 comments
Closed

MR14: Update "Maintained" to 2019 for DockerHub README #28010

sagetrac-gitlab-bot mannequin opened this issue Jun 18, 2019 · 10 comments

Comments

@sagetrac-gitlab-bot
Copy link
Mannequin

sagetrac-gitlab-bot mannequin commented Jun 18, 2019

Julian Rüth (@saraedum) opened a merge request at https://gitlab.com/sagemath/sage/merge_requests/14:

This updates the "maintained" year for the README on Docker Hub,
thus making it clear this project is currently maintained.

CC: @slel

Component: distribution

Keywords: days101

Author: Samuel Lelièvre

Branch/Commit: 96a0c45

Reviewer: Julian Rüth

Issue created by migration from https://trac.sagemath.org/ticket/28010

@sagetrac-gitlab-bot sagetrac-gitlab-bot mannequin added this to the sage-8.8 milestone Jun 18, 2019
@saraedum

This comment has been minimized.

@slel
Copy link
Member

slel commented Jun 19, 2019

@saraedum
Copy link
Member

New commits:

96a0c45#28010 Signal Sage Docker as maintained in 2019

@saraedum
Copy link
Member

Changed author from Julian Rüth to Samuel Lelièvre

@saraedum
Copy link
Member

Changed commit from 8df690f to 96a0c45

@saraedum
Copy link
Member

Reviewer: Julian Rüth

@saraedum
Copy link
Member

Changed keywords from none to days101

@slel

This comment has been minimized.

@vbraun
Copy link
Member

vbraun commented Jun 28, 2019

Changed branch from u/slelievre/mrs/14/update-maintained-2019 to 96a0c45

@embray
Copy link
Contributor

embray commented Jul 3, 2019

comment:7

Not in Sage 8.8. Let's please to try keep tickets' milestones related to the release in which we actually intend to include them, and in particular the release in which they were actually included, especially when closing tickets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants