Re: [tei-council] release branch building again

We currently allow posts from ^.*@github.com to this list list even though the sender is not a member of the list. I can add other allowed addresses if needed -- just let me know. On 3/18/16 6:20 AM, Hugh Cayless wrote:

Peter, any chance you can set the release build to email the Council list? I didn’t get a notification apart from your email when it broke.

Thanks, Hugh

...

On Mar 18, 2016, at 5:00 , Peter Stadler wrote:

I had some trouble getting Jenkins to build the release branch after Hugh inserted this ancient Greek symbol into the version number ;) That’s due to the fact that for the Debian packages a changelog is created (e.g. P5/debian-tei-p5-database/debian/changelog) which afterwards is checked to see whether a new package is needed (when the latest version number differs from the new one). Once the beta was in there, subsequent builds failed because of an "illegal character“.

I simply nuked those changelog files for now but in the mid term we should a) make that process more bullet proof b) rethink whether that’s an appropriate was of creating the changelog. Because if we release now, there will be no history in the changelog but the current release information. So if we care about the history of the deb-packages we’d need to keep this information somewhere outside (under version control); if we don’t, we can simply add those changelog files to the „clean“ target.

Best Peter

PS: I’ll be on holiday for the next 10 days but will be back in office on the 29th. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived