Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 6248:2f53d41ae71f
Upgrading directions from 2.0.0 - classname format requirements.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Tue, 28 Jul 2020 21:41:59 -0400 |
| parents | 13f5cbbcd4e6 |
| children | b2eb59ada444 |
comparison
equal
deleted
inserted
replaced
| 6247:ca0915457761 | 6248:2f53d41ae71f |
|---|---|
| 19 | 19 |
| 20 Contents: | 20 Contents: |
| 21 | 21 |
| 22 .. contents:: | 22 .. contents:: |
| 23 :local: | 23 :local: |
| 24 | |
| 25 .. index:: Upgrading; 1.6.x to 2.x.x | |
| 26 | |
| 27 Migrating from 2.0.0 to 2.x.x | |
| 28 ============================= | |
| 29 | |
| 30 Classname Format Enforced | |
| 31 ========================= | |
| 32 | |
| 33 Check schema.py and look at all Class(), IssueClass(), FileClass() | |
| 34 calls. The second argument is the classname. All classnames must: | |
| 35 | |
| 36 * start with an alphabetic character | |
| 37 * consist of alphanumerics and '_' | |
| 38 * not end with a digit | |
| 39 | |
| 40 this was not enforced before. Using non-standard classnames could lead | |
| 41 to other issues. | |
| 24 | 42 |
| 25 .. index:: Upgrading; 1.6.x to 2.0.0 | 43 .. index:: Upgrading; 1.6.x to 2.0.0 |
| 26 | 44 |
| 27 Migrating from 1.6.X to 2.0.0 | 45 Migrating from 1.6.X to 2.0.0 |
| 28 ============================= | 46 ============================= |