Re: [tei-council] Release followup

I also want to follow up on this: I think this is a REALLY SERIOUS problem. The stylesheets’ CI ought to flag issues with the current state of the Guidelines. Keeping up with some of the expected results stuff may be a small pain, but figuring out what bugs other people’s additions have caused is hard. I’d like to push that fixing process closer to the checkin, rather than waiting to deal with it after a release.

On Oct 13, 2015, at 8:20 , Hugh Cayless wrote:

I also think this should have showed up way earlier, and the reason it didn’t is that the Stylesheets tests are pegged by default to the current release, so Jenkins is not checking them against the contents of the master branch. I do see the value of having them test against the current release in terms of pure Stylesheets development, but it’s a serious flaw for any work that should happen in tandem. I’d like to suggest that we add a second build of the Stylesheets in Jenkins that runs its tests against the last build of TEIP5. That would a) alert us immediately if tests need to be regenerated, and b) flag things like this Odd By Example bug early on.