Andy Bierman wrote:
Hi, The WG now has an issue tracker (better late than never), thanks to David Partain. http://tools.ietf.org/wg/netconf/trac/report/1
I noticed the tracker assigned ticket numbers from 1 to N across all components. It would be better if the numbering was per component. The WG does not need to resolve the RFC4741 tickets to complete the Notifications deliverable. A flat numbering scheme like the arbitrary and scattered RFC numbers is not very user-friendly either. These are not software components within an application, they are independent drafts. Is there another numbering scheme available in trac? Andy
David has agreed to help administer the list, so please ask him how it works ;-) We are still working out the kinks, but there are 5 components in the NETCONF project: - RFC4741 - RFC4742 - RFC4743 - RFC4744 - draft-ietf-netconf-notification I have already filed 3 tickets for feature enhancements to RFC4741. Each of the reviewers who raised issed with notification-08 should click on the 'Get Passwd' button, and then login and enter a ticket for each issue (with component == draft-ietf-netconf-notification). thanks, Andy-- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/netconf/>
-- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/netconf/>