Difference between revisions of "BP revision ticket triage"

From TEIWiki
Jump to navigation Jump to search
(medium implementation: issue 5 needs to be reconsidered)
m (easy implementation: issues 30 and 33 done)
Line 8: Line 8:
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 issue 22: a corrigible error to fix (accidentally referring to Tite!)] – complete
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 issue 22: a corrigible error to fix (accidentally referring to Tite!)] – complete
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 issue 29: explain how to use just the header recommendations from the Best Practices] – complete
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 issue 29: explain how to use just the header recommendations from the Best Practices] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – Kevin will implement along with issue 33.
+
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/33 issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once] – Kevin will implement along with issue 30.
+
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/33 issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once] – complete
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/34 issue 34: clarify where to encode <pb/>s: footnotes not entirely on same page as point of attachment] – James will implement
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/34 issue 34: clarify where to encode <pb/>s: footnotes not entirely on same page as point of attachment] – James will implement
  

Revision as of 03:26, 3 June 2016

Probably not controversial

easy implementation

medium implementation

hard implementation

Could be controversial

easy implementation

medium implementation

hard implementation

Postpone