I forgot that, thanks for reminding me, Guillaume!

Should we put it under https://docs.opendaylight.org/en/latest/contributor-guides/newcomers-guide.html ?

Thanks Navid

For information, most of best practices have now been migrated to the documentation contributor guides

at https://docs.opendaylight.org/en/latest/contributor-guides/index.html

Guillaume

Hi All,

Here is the list of fields I believe we should make them mandatory in any jira ticket. I have added description with some example values for each field. As mentioned in our last TSC call, this may help automating the project release tracking and release notes publication.

please let me know what your thoughts are.

We should also find a good place in wiki to publish it. Maybe under Best Practices (https://wiki-archive.opendaylight.org/view/BestPractices)?

Thanks,

Navid

Project:

description: project name

values: aaa/bgpcep/controller/daexim/distribution/infrautils/jsonrpc/lispflowmapping/netconf/netvirt/openflowplugin/ovsdb/serviceutils/tpce

Priority:

description: the importance of ticket

values: Highest, High, Medium, Low, Lowest

Type:

description: issue type

values: Bug/New Feature/Task/Improvement/Deprecate

Status:

description: the status of ticket

values: Open/In Progress/In Review/Confirmed/Verified/Resolved/Closed/Done/Open

affectedVersion:

description: the version that the issue was seen (it’s only applicable to bugs)

values: aluminum/silicon/etc.; “None” to be used for anything other than “Bug”

fixVersion:

description: the version that includes the bug fix, new feature, behavior/feature change (improvement), or deprecated feature (the first time that the feature is being disappeared)

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

You’re welcome.

It’s up to you where you want to put it.

You can use newcomers guide but you can also create a dedicated page since  this mostly concerns PTL and committers.

Guillaume

I forgot that, thanks for reminding me, Guillaume!

Should we put it under https://docs.opendaylight.org/en/latest/contributor-guides/newcomers-guide.html ?

Thanks Navid

For information, most of best practices have now been migrated to the documentation contributor guides

at https://docs.opendaylight.org/en/latest/contributor-guides/index.html

Guillaume

Hi All,

Here is the list of fields I believe we should make them mandatory in any jira ticket. I have added description with some example values for each field. As mentioned in our last TSC call, this may help automating the project release tracking and release notes publication.

please let me know what your thoughts are.

We should also find a good place in wiki to publish it. Maybe under Best Practices (https://wiki-archive.opendaylight.org/view/BestPractices)?

Thanks,

Navid

Project:

description: project name

values: aaa/bgpcep/controller/daexim/distribution/infrautils/jsonrpc/lispflowmapping/netconf/netvirt/openflowplugin/ovsdb/serviceutils/tpce

Priority:

description: the importance of ticket

values: Highest, High, Medium, Low, Lowest

Type:

description: issue type

values: Bug/New Feature/Task/Improvement/Deprecate

Status:

description: the status of ticket

values: Open/In Progress/In Review/Confirmed/Verified/Resolved/Closed/Done/Open

affectedVersion:

description: the version that the issue was seen (it’s only applicable to bugs)

values: aluminum/silicon/etc.; “None” to be used for anything other than “Bug”

fixVersion:

description: the version that includes the bug fix, new feature, behavior/feature change (improvement), or deprecated feature (the first time that the feature is being disappeared)

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.