Rkt: Roadmap is gone from master?

[cmpitg]

Hi,

I believe from 90c82df30317317620f5f5bc38b5c605180b26f2 the roadmap file is gone. The link from README results in a 404.

$ git log -5 -- ROADMAP.md
commit 90c82df30317317620f5f5bc38b5c605180b26f2
Author: Casey Callendrello <[email protected]>
Date:   Thu Sep 15 15:23:19 2016 +0200

    version: bump to v1.15.0

commit 89ca8decf5ec2465da60275240771a3d858c4d53
Author: Sergiusz Urbaniak <[email protected]>
Date:   Thu Sep 1 10:25:48 2016 +0200

    ROADMAP: update

commit 4d403da1afc19aeeb37e484b4c60f9af44f7bffd
Author: Luca Bruno <[email protected]>
Date:   Thu Aug 18 13:51:42 2016 +0000

    version: bump to v1.13.0

commit b172d657999374a511c042914d0506a3ad8e6464
Author: Sergiusz Urbaniak <[email protected]>
Date:   Thu Jul 21 11:55:30 2016 +0200

    changelog, roadmap: document v1.11.0 release

commit 603e8d4608fea48c46ac0612cadd48a4b550e2ed
Author: Casey Callendrello <[email protected]>
Date:   Thu Jul 7 13:11:32 2016 +0200

    docs: update docs for the v1.10.0 release

$ git diff 89ca8decf5ec2465da60275240771a3d858c4d53 -- ROADMAP.md
diff --git a/ROADMAP.md b/ROADMAP.md
deleted file mode 100644
index 9332025..0000000
--- a/ROADMAP.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# rkt roadmap
-
-This document defines a high level roadmap for rkt development.
-The dates below should not be considered authoritative, but rather indicative of the projected timeline of the project.
-The [milestones defined in GitHub](https://github.com/coreos/rkt/milestones) represent the most up-to-date state of affairs.
-
-rkt is an implementation of the [App Container spec](https://github.com/appc/spec), which is still under active development on an approximately similar timeframe.
-The version of the spec that rkt implements can be seen in the output of `rkt version`.
-
-rkt's version 1.0 release marks the command line user interface and on-disk data structures as stable and reliable for external development. The (optional) API for pod inspection is not yet completely stabilized, but is quite usable.
-
-### rkt 1.15.0 (September)
-
-Full plan at https://github.com/coreos/rkt/milestone/49.
-
-Highlights:
-- initial CRI support, replacing the existing gRPC [API](https://github.com/coreos/rkt/tree/master/api/v1alpha).
-- Refactor distribution/storage handling
-- Improved native support for OCI
-- Enhanced DNS configuration
-- Further improvements for SELinux environments, especially Fedora in enforcing mode
-- Support for unified cgroups
-
-### Upcoming
-
-Full plan at https://github.com/coreos/rkt/milestone/30.
-
-Highlights:
-- `rkt fly` as top-level command
-- User configuration for stage1
-- Stable gRPC [API](https://github.com/coreos/rkt/tree/master/api/v1alpha)
-- Packaged for more distributions
-  - CentOS

Ha-Duong

[lucab]

I think that @squeed deleted it from the latest release as we are now more effectively tracking tasks via GitHub milestones/projects. Also, rkt as a projects is strongly driven by whatever are the needs and evolutions of the surrounding environments (kubernetes, OCI, etc.) so our ROADMAP file was not really accurate except for the very next release.

[jonboulle]

Can we restore some version of this file? even if it's just pointing towards the milestones and mentioning the other surrounding environments.

[squeed]

Darn, I was hoping nobody would notice :-)
I removed it because it fell out of date, and it takes 30 minutes to harass
everyone and write it during a release. Whatever we put back should be
either better maintained, or not require significant maintenance at release
time.

On Fri, Sep 16, 2016 at 1:04 PM, Jonathan Boulle [email protected]
wrote:

Can we restore some version of this file? even if it's just pointing
towards the milestones and mentioning the other surrounding environments.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/issues/3206#issuecomment-247574448, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAhp0uh6MmCKc4iPRzt-YjKH-Y5x8wXOks5qqnfBgaJpZM4J-rNP
.

[jonboulle]

How about adding some verbiage describing how we use the milestones, that
we do fortnightly releases, and restoring the 1.0 compatibility note?

On 16 September 2016 at 13:23, Casey Callendrello [email protected]
wrote:

Darn, I was hoping nobody would notice :-)
I removed it because it fell out of date, and it takes 30 minutes to harass
everyone and write it during a release. Whatever we put back should be
either better maintained, or not require significant maintenance at release
time.

On Fri, Sep 16, 2016 at 1:04 PM, Jonathan Boulle <[email protected]

wrote:

Can we restore some version of this file? even if it's just pointing
towards the milestones and mentioning the other surrounding environments.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/issues/3206#issuecomment-247574448, or
mute
the thread
auth/AAhp0uh6MmCKc4iPRzt-YjKH-Y5x8wXOks5qqnfBgaJpZM4J-rNP>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/issues/3206#issuecomment-247577472, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewNxYHvFffzDPVKJKmZ7To3CM8lbm7ks5qqnxPgaJpZM4J-rNP
.

[lucab]

I see some value in having a doc pointing out to:

• next release version
• timeframe (month granularity seems enough to me)
• pointers to milestone, projects, etc.

Fine-detailing what we will do and when in a static file instead didn't seem to work too well, I agree.

[grepory]

I would also be satisfied with the removal of the broken link from README.md and instead perhaps a link to github projects/etc or whatever the interface for that is. Just saying... Because broken links are a tragedy.

[jonboulle]

@squeed could you take a look at this please?

On 26 September 2016 at 18:35, Greg Poirier [email protected]
wrote:

I would also be satisfied with the removal of the broken link from
README.md and instead perhaps a link to github projects/etc or whatever the
interface for that is. Just saying... Because broken links are a tragedy.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/issues/3206#issuecomment-249623788, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewN-nKOJjxfXyHDqp-YV28pfOqtP5zks5qt_RTgaJpZM4J-rNP
.