search

w3c / csswg-drafts

CSS Working Group Editor Drafts
https://drafts.csswg.org/
Other
4.42k stars 648 forks source link

Republishing Tasks Permathread #6900

Open tabatkins opened 2 years ago

tabatkins commented 2 years ago

Tag the IRC bot with this thread whenever publication resolutions are being discussed.

Agenda+ and add a comment if you want to publish something.

  1. Edit this comment to add things to the list. Say what is being published (FPWD, WD, CRD, CRS, Rec, etc)
  2. Include a link to the latest resolution to publish and/or Agenda+ request for permission to publish, so we can follow-up.
  3. Checkmark means has a WG resolution.
  4. Link the transition request, once it has been made.
  5. Remove from list once actually published.

See also Estimated Publication Badness Chart and Transition Requests

Latest:

Backlog of Uncertain Blockedness:

fantasai commented 2 years ago

Agenda+ to republish Mediaqueries 3 REC editorial update: https://github.com/w3c/csswg-drafts/commits/main/mediaqueries-3 and fix shorthame to mediaqueries-3

frivoal commented 2 years ago

mediaqueries-3 is not written using bikeshed. Does the tooling to generate .html files from .src.html files still exist?

svgeesus commented 2 years ago

It still exists but the result requires so much hand-editing that it is basically easier to work with the generated html to add changes. Same issue for Fonts 3, Color 3.

fantasai commented 2 years ago

Agenda+ to republish CSS Text Level 4, now that I've merged in css-text-3 and added percentages to letter-spacing and word-spacing (as resolved in 2018 T_T)

css-meeting-bot commented 2 years ago

The CSS Working Group just discussed Republishing CSS Text 4, and agreed to the following:

The full IRC log of that discussion <fantasai> Topic: Republishing CSS Text 4
<fantasai> github: https://github.com/w3c/csswg-drafts/issues/6900#issuecomment-1064818560
<emilio> fantasai: Proposal is to republish css-text level 4
<emilio> ... changes are that I merged css-text 3 and I added percentage values to letter-spacing and word-spacing that we resolved on 4 years ago
<emilio> Rossen_: any reason not to do it?
<emilio> fantasai: don't think so
<emilio> RESOLVED: Republish css-text level 4
svgeesus commented 2 years ago

RESOLVED: Republish css-color-4 and css-color-5

Publications requested 22 Apr, expected 28 Apr (after the publishing moratorium ends)

svgeesus commented 2 years ago

CSS Will Change 1: publication requested 29 Apr, expected Thu 05 May

svgeesus commented 2 years ago

CSS Will Change 1 CRD published Thu 5 May

svgeesus commented 2 years ago

Publication for CSS Variables 1 CR Snapshot requested 13 June, expected Thu 16 June.

Republication issue filed on Properties & Values API.

svgeesus commented 2 years ago

Variables 1 CR Snapshot published 16 June 2022

svgeesus commented 2 years ago

Agenda+ to republish CSS Color 4 and CSS Color 5 which now incorporate the resolutions from the 15 June 2022 telcon.

css-meeting-bot commented 2 years ago

The CSS Working Group just discussed Republishing tasks.

The full IRC log of that discussion <TabAtkins> Topic: Republishing tasks
<TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/6900
<TabAtkins> chris: That was color 4 and 5
svgeesus commented 2 years ago

CSS Color 4, publication requested 22 June expected Tue 28 June CSS Color 5, publication requested 23 June expected Tue 28 June

svgeesus commented 1 year ago

Agenda+ to publish CRD of CSS Color 4. Changes since July 2022 CR Snapshot

css-meeting-bot commented 1 year ago

The CSS Working Group just discussed CSS Color L4, and agreed to the following:

The full IRC log of that discussion <fantasai> Topic: CSS Color L4
<fantasai> github: https://github.com/w3c/csswg-drafts/issues/6900
<emeyer> chris: There’s been a bunch of updates since June, I’d like to keep it up to date and publish current state
<emeyer> Rossen: As of this state, any feedback or reasons why we shouldn’t republish?
<emeyer> …Any objections?
<emeyer> RESOLVED: Republish CRD of CSS Color 4
fantasai commented 1 year ago

Agenda+ to republish CRS of CSS Text 3 once we approve the last few edits (see open DoC issues).

css-meeting-bot commented 1 year ago

The CSS Working Group just discussed Republishing Tasks Permathread Administrative Tracker For external review / publication tracking issues, and agreed to the following:

The full IRC log of that discussion <emeyer> Topic: Republishing Tasks Permathread Administrative Tracker For external review / publication tracking issues
<emeyer> github: https://github.com/w3c/csswg-drafts/issues/6900
<emeyer> fantasai: We compiled a changes list and disposition of comments
<emeyer> …There’s a minor change we made as a followup to one of the issues
<emeyer> …Assuming that’s good, we’d like to request an updated CR snapshot
<fantasai> https://github.com/w3c/csswg-drafts/commit/d3ed39e04fb2a3087aa745dce57abd59c93412c5
<emeyer> `text-justify: distribute` addition
<emeyer> fantasai: spec was updated to allow Firefox treatment
<emeyer> florian: About testing, all normative changes since last CR do have tests
<emeyer> …Spec itself has pretty extensive test coverage
<emeyer> …Not complete, but pretty exhaustive
<emeyer> Rossen_: All the more reasons to republish
<emeyer> RESOLVED: Republish!
<fantasai> s/Republish CR/
svgeesus commented 1 year ago

CSS Text 3 CRD published 17 Jan 2023

css-meeting-bot commented 1 year ago

The CSS Working Group just discussed Web Anim stuff, and agreed to the following:

The full IRC log of that discussion <TabAtkins> Topic: Web Anim stuff
<TabAtkins> flackr: Scroll Animations is depending on a lot of changes in Web Anim 2, to support CSSNumericValues in the API
<TabAtkins> flackr: But WA2 isn't ED yet
<TabAtkins> flackr: We've been having discussions around that spec for more than a year now. I'd like to move it to ED to get things ready for Scroll Animations
<TabAtkins> +1 from me for fpwd
<Rossen_> ack fantasai
<Zakim> fantasai, you wanted to ask if it should go to FPWD
<TabAtkins> fantasai: Fully support ED, it's overdue. Should it be going to fpwd? Is there stuff you think should *not* be in the spec? Or is it all in the direction we want to take?
<TabAtkins> flackr: There are many things in the spec not implemented/experimented yet..
<TabAtkins> flackr: But I think it's generally in the right direction. Probably just CustomEffects that's not well defined.
<TabAtkins> fantasai: Are they in a direction that looks reasonble and could be more well defined?
<TabAtkins> flackr: Yes
<TabAtkins> fantasai: So yeah then, it's fpwd, that's fine
<chrishtr> +1
<TabAtkins> Rossen_: Objections for web-animations-2 FPWD?
<TabAtkins> Rossen_: Same editors?
<TabAtkins> flackr: It has Stephen and Antoine removed. I know Stephen's no longer working on WA, dunno about Antoine. But me and Brian are def in.
<TabAtkins> Rossen_: Okay then let's go with you and Brian, we can add more later.
<TabAtkins> RESOLVED: Publish Web Animations 2 as FPWD, with flackr and Brian as editors
<TabAtkins> fantasai: Do we want fpwd for CSS Animations 2?
<TabAtkins> flackr: I'm in support
<TabAtkins> Rossen_: Anything there that wouldn't be ready?
<TabAtkins> flackr: from my perspective it's solid
<TabAtkins> Rossen_: Sounds good, objections?
<TabAtkins> RESOLVED: Publish CSS Animations 2 fpwd
<TabAtkins> flackr: There's also Transitions 2
<TabAtkins> fantasai: Summarize changes?
<TabAtkins> flackr: Good question, cant' summarize right now
<TabAtkins> fantasai: That's fine, we'll come back to it
<TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/6900
<TabAtkins> github-bot, take up https://github.com/w3c/csswg-drafts/issues/7664
svgeesus commented 1 year ago

Who is doing the FPWD transition requests for those two?

svgeesus commented 1 year ago

Who is doing the FPWD transition requests for those two?

Thanks @fantasai

css-meeting-bot commented 1 year ago

The CSS Working Group just discussed Republishing Tasks Permathread, and agreed to the following:

The full IRC log of that discussion <TabAtkins> fantasai: We'd like to publish Position 3 with the stickypos change we just resolved.
<TabAtkins> fantasai: Also publish Box Alignment
<TabAtkins> fantasai: Some of the issues we fixed crossed between these specs.
<TabAtkins> Rossen_: Objections for new WD of Position 3 and Align 3?
<fantasai> https://drafts.csswg.org/css-position-3/#changes
<TabAtkins> fantasai: We did a substantial number of fixes to the staticpos section, I'd definitely encourage people to look at that.
<fantasai> https://drafts.csswg.org/css-position-3/#abspos-insets
<TabAtkins> fantasai: Right now we still have an old-style "two versions" of the spec - rewritten and non-rewritten. Probably want to drop the non-rewritten soon, so if people can review the rewritten is correct it woudl be great
<TabAtkins> fantasai: Particularly #abspos-insets, most of the changes are in that section
<fantasai> https://drafts.csswg.org/css-position-3/#abspos-layout is also a major part of the replacement (but less changes lately)
<TabAtkins> fantasai: So rquesting to repub, and hopefully in next repub we can drop the old section
<TabAtkins> Rossen_: Not hearing objections
<astearns> +1 to publish
<TabAtkins> RESOLVED: Publish new WD of Position 3 and Align 3.
<fantasai> https://drafts.csswg.org/css-align-3/#changes
<TabAtkins> Rossen_: no objectiosn to Align 3 pub
svgeesus commented 1 year ago

CSS Box 3 published 16 Feb 2023

svgeesus commented 1 year ago

CSS Animations 2 FPWD and CSS Animations 1 WD published today.

svgeesus commented 1 year ago

CSS Text 4 published 1 March

fantasai commented 1 year ago

Agenda+ to request review and republication of:

(The other changes in this cycle were all in response to WG resolutions on issues.)

css-meeting-bot commented 1 year ago

The CSS Working Group just discussed Republishing Tasks Permathread, and agreed to the following:

The full IRC log of that discussion <fantasai> https://drafts.csswg.org/css-overflow-3/#scrolling
<TabAtkins> fantasai: Request to repub Overflow 3, which added a section for scrolling-related concepts
<TabAtkins> fantasai: This gives us a bunch of anchors
<dbaron> https://lists.w3.org/Archives/Member/w3c-css-wg/2023JanMar/0224.html (repeating from before the topic)
<TabAtkins> astearns: Changes section up to date?
<fantasai> https://drafts.csswg.org/css-overflow-3/#changes
<TabAtkins> RESOLVED: Repub Overflow 3
svgeesus commented 1 year ago

@sanketj please do not un-pin this issue

sanketj commented 1 year ago

@sanketj please do not un-pin this issue

Sorry, didn't realize that was un-pinning for the repo itself. Thought that somehow was pinned just for me. My bad...

svgeesus commented 1 year ago

CSS Display 3 CR Snapshot published 30 Mar

sanketj commented 1 year ago

Agenda+ to republish WD for CSS Custom Highlight API 1

Notable changes since last WD:

svgeesus commented 1 year ago

CSS Box 3 Rec publication requested 03 Apr, expected 06 Apr.

css-meeting-bot commented 1 year ago

The CSS Working Group just discussed Republishing Tasks Permathread, and agreed to the following:

The full IRC log of that discussion <dael> Rossen_: Are we ready to start the republishing process?
<dael> sanketj: I think changelog is only thing left
<dael> Rossen_: Anything else you wanted to cover? I think we have a resolution but happy to record one more.
<dael> sanketj: I think these were all deltas since last WD. Not quite ready for CR. Has been a while since we last published.
<dael> Rossen_: Happy to record a resolution with the changes you outlined. [reads]
<dael> Rossen_: These are the changes going into the WD. Unless someone objects would like a resolution to proceed
<dael> florian: Think it's good. Seems all edits are editorial or backed by resolution
<dael> RESOLVED: Republish WD of css-highlight-api-1
svgeesus commented 1 year ago

CSS 3 Box REC published 6 Apr 2023

css-meeting-bot commented 1 year ago

The CSS Working Group just discussed FPWD Moving CSS Transitions 2 to FPWD, and agreed to the following:

The full IRC log of that discussion <dbaron> Topic: FPWD Moving CSS Transitions 2 to FPWD
<fantasai> github: https://github.com/w3c/csswg-drafts/issues/6900
<dbaron> https://drafts.csswg.org/css-transitions-2/#changes-fpwd
<fantasai> -> https://lists.w3.org/Archives/Member/w3c-css-wg/2023JulSep/0126.html
<emeyer> dbaron: There’s a bunch of stuff sitting in it for a while mostly about integrations with web animations
<emeyer> …@starting-stle rule and [missed] property
<chris> q+
<TabAtkins> +1
<astearns> +1 to FPWD
<fantasai> s/stle/style/
<flackr> +1
<dbaron> s/[missed]/discrete animations and the transition-behavior/
<Rossen_> ack chris
<emeyer> s/@starting-stle/@starting-style/
<emeyer> chris: No problem with saying FPWD is a delta
<chris> +1
<emeyer> Rossen: Any objections to FPWD for CSS-transitions-2?
<emeyer> (none)
<fantasai> +1
<emeyer> RESOLVED: CSS Transitions 2 will have a FPWD
frivoal commented 1 year ago

Agenda+ to request review and republication of css-text-3 as CRD

css-meeting-bot commented 12 months ago

The CSS Working Group just discussed Republishing Tasks Permathread, and agreed to the following:

The full IRC log of that discussion <chris> +1 to transition to CRD
<emeyer> florian: The question is, should we publish as a CR draft
<emeyer> …Spec is up to date, tests exist for every change
<chris> changes look good, few open issues
<emeyer> …There are a couple of open issues, but they’re coordination problems with other specs or browser releases
<emeyer> …We should compile comments and wider review, and if those go well we’re probably ready for a full CR
<emeyer> astearns: Thank you for making sure all the changes have tests
<emeyer> florian: Thank Elika as well
<emeyer> chris: Everything looks good after a quick look
<emeyer> astearns: Any objections?
<emeyer> RESOLVED: Publish CSS Text 3 as a CRD
svgeesus commented 8 months ago

CSS Color 4 has some remaining issues, 23 open 257 closed but given the large number of changes since the Candidate Recommendation Draft of 1 November 2022 I would like to publish an updated CRD of CSS Color 4.

@LeaVerou @tabatkins

(CSS Color 5, which is not yet at CR, also has a bunch of changes so I would republish that at the same time.)

svgeesus commented 7 months ago

FPWD of css-viewport-1

css-meeting-bot commented 7 months ago

The CSS Working Group just discussed Republishing Tasks Permathread, and agreed to the following:

The full IRC log of that discussion <Frances> Alan: First on the Agenda is FPWD for css-viewport-1
<Frances> Emilio: Something might be worse than doing, but we can republish it. Place for things in the spec that are linkable.
<Frances> Alan: Inclined to publish now and zoom stuff later.
<florian> q+
<Frances> PROPOSAL: Publish FPWD for css-viewport-1
<Frances> Florian: Section 3 viewport, is it light?
<Frances> Alan: We already published the section
<chris> rrsagent, here
<RRSAgent> See https://www.w3.org/2024/01/17-css-irc#T17-07-03
<Frances> Alan: Any objections?
<Frances> Alan: None and resolved.
<Frances> RESOLVED: Create FPWD for css-viewport-1
<Frances> RESOLVED: Publish FPWD for css-viewport-1
<Frances> Alan: Who wants to talk about display mode?
svgeesus commented 7 months ago
svgeesus commented 7 months ago

CSS Viewport 1 published 25 Jan 2024

svgeesus commented 6 months ago

Agenda+ For

  1. an updated WD of CSS Fonts 4. There remain a fair number of issues 91 open, 248 closed but there have been a lot of changes since the previous /TR publication of 21 December 2021
  2. an updated WD of CSS Fonts 5 which has 39 open, 41 closed and a much smaller list of changes but should be republished at the same time, for consistency.
  3. already requested CRD update for CSS Color 4 and
  4. updated WD of CSS Color 5

@astearns @atanassov these could all be async decisions, of course

svgeesus commented 6 months ago
fantasai commented 6 months ago

Agenda+ for republishing an updated WD of CSS Generated Content Level 3 assuming confirmation of edits in #5478, see Changes List.

astearns commented 6 months ago

The CSSWG will automatically accept this resolution one week from now if no objections are raised here. Anyone can add an emoji to this comment to express support. If you do not support this resolution, please add a new comment.

Proposed Resolution: Publish CRD update for CSS Color 4

astearns commented 6 months ago

@fantasai on an updated WD for CSS Generated Content Level 3, you could use https://wiki.csswg.org/spec/publish as the resolution “if there are only non-controversial editorial changes and/or substantive changes approved by the WG”

svgeesus commented 6 months ago

CSS Color 4 has some remaining issues, 23 open 257 closed but given the large number of changes since the Candidate Recommendation Draft of 1 November 2022 I would like to publish an updated CRD of CSS Color 4.

@astearns could I get an async resolution for CRD on this one, please?

astearns commented 6 months ago

@astearns could I get an async resolution for CRD on this one, please?

Is this not that?

https://github.com/w3c/csswg-drafts/issues/6900#issuecomment-1928584953 https://lists.w3.org/Archives/Public/www-style/2024Feb/0001.html

svgeesus commented 6 months ago

Haha I read @fantasai asking for WD of CSS Generated Content Level 3 and then your async and thought it was in response to her request, not mine.

(Cleans glasses)

Yes, it is.