Skip to content

Scala 3 reference docs for 3.2.0 do not have updated sources #16201

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
bishabosha opened this issue Oct 18, 2022 · 5 comments
Closed

Scala 3 reference docs for 3.2.0 do not have updated sources #16201

bishabosha opened this issue Oct 18, 2022 · 5 comments

Comments

@bishabosha
Copy link
Member

as of 18 October 2022 https://docs.scala-lang.org/scala3/reference/language-versions/source-compatibility.html looks like:
Screenshot 2022-10-18 at 09 59 56

it should show content as listed in https://github.com/lampepfl/dotty/blob/release-3.2.0/docs/_docs/reference/language-versions/source-compatibility.md

@bishabosha bishabosha added itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label area:documentation and removed stat:needs triage Every issue needs to have an "area" and "itype" label labels Oct 18, 2022
@bishabosha
Copy link
Member Author

according to @julienrf release-3.2.0 should be merged into language-reference-stable

@julienrf
Copy link
Contributor

I think there is a general lack of clarity about how the various docs are generated.

As far as I understand, we have:

Correct me if I am wrong, and please document those things here (in CONTRIBUTING.md?), and explain the policies regarding what goes into what branch (if I want to fix something in the documentation, should I target main or language-reference-stable?).

Last, make sure the release procedure takes all those forms of documentation into account (currently, it seems only the API documentation is updated during the release process, but you should also merge the content of the main branch to language-reference-stable before the release)

@bishabosha
Copy link
Member Author

Last, make sure the release procedure takes all those forms of documentation into account ... but you should also merge the content of the main branch to language-reference-stable before the release)

I think you mean the current release branch? - main branch might have documentation for unreleased new features

@julienrf
Copy link
Contributor

I think you mean the current release branch? - main branch might have documentation for unreleased new features

Yes.

Kordyjan added a commit that referenced this issue Oct 18, 2022
did a rebase of `release-3.2.0` onto `language-reference-stable` and
fixed conflicts

fixes #16201
@bishabosha
Copy link
Member Author

Changes are now visible on the website

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

2 participants