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

Changes in manage workflow form #644

Closed
ietf-svn-bot opened this issue Mar 30, 2011 · 5 comments
Closed

Changes in manage workflow form #644

ietf-svn-bot opened this issue Mar 30, 2011 · 5 comments

Comments

@ietf-svn-bot
Copy link

owner:esanchez@yaco.es resolution_fixed type_enhancement | by esanchez@yaco.es


Do the following changes in the manage workflow form:

  • Add state definitions
  • Freeze states so they can not be removed from the WG workflow:
    • WG Document
    • Submitted to IESG for Publication
    • And probably 'Call For Adoption By WG Issued' cause you need it to bring a document to your WG.
  • Reorder states to more closely resemble how an I-D might traverse the state diagram, from top to bottom
  • Include a pointer to the state diagram in section 4.1 of RFC6174

Issue migrated from trac:644 at 2022-03-04 01:48:23 +0000

@ietf-svn-bot
Copy link
Author

@esanchez@yaco.es commented


From 8527cda:

Freeze global WG states. See #644

@ietf-svn-bot
Copy link
Author

@esanchez@yaco.es commented


From e4f9bbe:

Added state definitions in workflow edit form.
Re-order states in workflow edit form.
See #644

@ietf-svn-bot
Copy link
Author

@esanchez@yaco.es changed status from new to closed

@ietf-svn-bot
Copy link
Author

@esanchez@yaco.es set resolution to fixed

@ietf-svn-bot
Copy link
Author

@esanchez@yaco.es commented


Fixed in e800623:

Add a link to the default Working Group I-D State Diagram. Fixes #644

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant