Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
spec:rec-maintenance [2017/02/01 17:16]
liam another more usual approach
spec:rec-maintenance [2017/02/01 19:51] (current)
astearns [Options with Problems]
Line 23: Line 23:
 Both of the options above also have some churn when we have some changes but not all ready to graduate to CR - we have to prepare a draft with only those changes ready for CR, move them through the process, then reintroduce the rest of the changes to a new ED/WD Both of the options above also have some churn when we have some changes but not all ready to graduate to CR - we have to prepare a draft with only those changes ready for CR, move them through the process, then reintroduce the rest of the changes to a new ED/WD
  
-Another option, and I think more usual, is to issue a Proposed Edited Rec (this is the same as publishing directly as a CR, skipping all earlier stages) - https://​www.w3.org/​2015/​Process-20150901/#​revised-rec - the CR can be republished if and as needed without going back to WD. This does not affect the Recommendation status of the original until the new version is published as a final REC - Liam+Another option, and I think more usual, is to issue a Proposed Edited Rec (this is the same as publishing directly as a CR, skipping all earlier stages) - https://​www.w3.org/​2015/​Process-20150901/#​revised-rec - the CR can be republished if and as needed without going back to WD. This does not affect the Recommendation status of the original until the new version is published as a final REC - Liam - (Alan'​s response: this is the method we want to use in the proposal below for those changes we know are ready for a quick CR. When we're not sure which changes will survive review and/or be adopted and testable, the problem is that the REC gets stuck in a republished CR cycle. I don't think it's good to take a REC back to CR for changes that haven'​t yet been vetted)
  
 ==== Proposal ==== ==== Proposal ====
  
 So the WG has proposed a new mechanism for making reviewable changes available on TR. We will produce a copy of the REC (CSS2 in this case) as a NOTE (CSS2-testing). This NOTE will be kept up-to-date with all proposed substantive changes to the REC, and people will be directed to review these changes in the NOTE. Periodically we will check the state of the changes in the NOTE, and those changes that have passed review and have passing tests will be folded in to the REC. This allows us to produce a CR of the Edited Recommendation that is ready to pass through the PR and REC stages as quickly as possible. So the WG has proposed a new mechanism for making reviewable changes available on TR. We will produce a copy of the REC (CSS2 in this case) as a NOTE (CSS2-testing). This NOTE will be kept up-to-date with all proposed substantive changes to the REC, and people will be directed to review these changes in the NOTE. Periodically we will check the state of the changes in the NOTE, and those changes that have passed review and have passing tests will be folded in to the REC. This allows us to produce a CR of the Edited Recommendation that is ready to pass through the PR and REC stages as quickly as possible.
 
spec/rec-maintenance.txt · Last modified: 2017/02/01 19:51 by astearns
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki