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

x/pkgsite: redesign - surfacing “latest” #41588

Open
julieqiu opened this issue Sep 23, 2020 · 0 comments
Open

x/pkgsite: redesign - surfacing “latest” #41588

julieqiu opened this issue Sep 23, 2020 · 0 comments

Comments

@julieqiu
Copy link
Contributor

@julieqiu julieqiu commented Sep 23, 2020

We'll be redesigning pkg.go.dev based on feedback received over the last year. This is the third in a series of issues about plans for the pkgsite/design-2020 milestone. Comment below with any feedback or suggestions related to this issue!

Overview

There are multiple ways in which “latest” can be defined for a path. In order to better express various relationships, we will use the following terms:

  • Series: 1 or more modules that are major versions of each other
  • Project: 1 or more modules that share the same path prefix
  • Latest minor version: the latest minor version of a module containing a path, according to the cmd/go definition. This is also referred to as the “latest” or “@latest” version.
  • Latest major version: the latest major version in a module series.
    • If the latest major version does not have any tagged versions, but an earlier version does, pkg.go.dev will default to the earlier version as the “latest” major version.

Design

Pkg.go.dev will continue to use the following:

  • A “Latest” badge to indicate whether a user is viewing the latest minor version
  • A banner to indicate when a user is not viewing the latest major version

image

Note: This image is a mock, so the data may not accurately represent the exact contents of this package.

We plan to also use the banner style to indicate other information related to surfacing the “latest” version, such as when a path is not present in the latest version of the module.

If a path exists in the latest version of a module, pkg.go.dev/<path> will always show the contents for the latest version of the containing module.

Related Issues

  • #37631: flag packages that are no longer present in the latest version of the containing module
  • #39244: </ should show the contents for the latest version of the containing module
  • #41032: multi-module projects have confusing versions
  • #37714: latest version should not be +incompatible
  • #37765: don't imply that vN.x.y is the latest version when vN+1 exists (also discussed in #40323)
  • #41345: new major version not surfaced when it does not yet have a release tag
@julieqiu julieqiu closed this Sep 23, 2020
@gopherbot gopherbot added the pkgsite label Sep 23, 2020
@gopherbot gopherbot added this to the Unreleased milestone Sep 23, 2020
@julieqiu julieqiu changed the title x/pkgsite: <this issue is a placeholder for a future issue> x/pkgsite: redesign - surfacing “latest” Sep 23, 2020
@julieqiu julieqiu reopened this Sep 23, 2020
@julieqiu julieqiu added the NeedsFix label Sep 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.