Do keep in mind we also have a list of things to consider for P6 at http://wiki.tei-c.org/index.php/P6-dev . Perhaps those should be moved into GitHub as issues with the P6 label so we don't forget about them. On 11/23/15 7:40 AM, James Cummings wrote:
All in favour of it... though I don't think we should worry too much about breaking backwards compatibility with that particular issue. (Since the solution is a trivial conversion and we could provide XSLT as a method of dealing with it.)
FAND-sympathiser,
-James
On 23/11/15 09:10, Peter Stadler wrote:
I was just going through some tickets and came across #1400 „Remove numbered divisions“, wondering whether we need (or want) a P6 label? That way, we could start collecting issues for the day X. That would not necessarily mean that those changes be implemented in P6, but discussion is postponed until then. So, rather than simply closing the issue, we could label it first (and close it then, so it’s not polluting our issue tracker), making it easy to reopen these issues when the time comes.
Cheers Peter