Hi All, Release 3.0.0 is coming up in less than a week! I've started a draft of the release notes here: https://docs.google.com/document/d/1htSJpqjKv4pe-N3Oelo70fDJGOrkD297B7Aa4QQC... Please add things you've worked on that you think should be in the list, and Lou, James, and Magdalena may want to modify and add to what I have down for Pure ODD and ProcMod. I've also started a section dedicating the release to Sebastian's memory. Additions, suggestions, and corrections are most welcome. I'll turn this into TEI and commit it on Sunday evening, so you have until then to modify it. I've put a fresh build of the release branch up at http://teic.github.io/TEI/. Please take some time this week to proofread and push changes to the release-3.0.0 branch. All the best, Hugh
I'm a little uncomfortable with the notion of dedicating a release to Sebastian. It seems a bit, well, demeaning. The entire *Guidelines* are already dedicated to him (among others).[1] That said, what you've written is lovely. Notes ----- [1] http://jenkins.tei-c.org/job/TEIP5-release-3.0.0/lastSuccessfulBuild/artifac...
Release 3.0.0 is coming up in less than a week! I've started a draft of the release notes here: https://docs.google.com/document/d/1htSJpqjKv4pe-N3Oelo70fDJGOrkD297B7Aa4QQC...
Please add things you've worked on that you think should be in the list, and Lou, James, and Magdalena may want to modify and add to what I have down for Pure ODD and ProcMod.
I've also started a section dedicating the release to Sebastian's memory. Additions, suggestions, and corrections are most welcome. I'll turn this into TEI and commit it on Sunday evening, so you have until then to modify it.
I've put a fresh build of the release branch up at http://teic.github.io/TEI/. Please take some time this week to proofread and push changes to the release-3.0.0 branch.
Why is it demeaning? Honest question. Social niceties sometimes go sailing
right past me, so I like to be told if I'm accidentally doing something
offensive.
On Thu, Mar 24, 2016 at 1:09 PM, Syd Bauman
I'm a little uncomfortable with the notion of dedicating a release to Sebastian. It seems a bit, well, demeaning. The entire *Guidelines* are already dedicated to him (among others).[1]
That said, what you've written is lovely.
Notes ----- [1] http://jenkins.tei-c.org/job/TEIP5-release-3.0.0/lastSuccessfulBuild/artifac...
Release 3.0.0 is coming up in less than a week! I've started a draft of the release notes here:
https://docs.google.com/document/d/1htSJpqjKv4pe-N3Oelo70fDJGOrkD297B7Aa4QQC...
Please add things you've worked on that you think should be in the list, and Lou, James, and Magdalena may want to modify and add to what I have down for Pure ODD and ProcMod.
I've also started a section dedicating the release to Sebastian's memory. Additions, suggestions, and corrections are most welcome. I'll turn this into TEI and commit it on Sunday evening, so you have until then to
modify
it.
I've put a fresh build of the release branch up at http://teic.github.io/TEI/. Please take some time this week to proofread and push changes to the release-3.0.0 branch. -- 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
Perhaps "demeaning" is not the right word (and certainly "offensive" isn't). But it's a bit like saying "not only did you win the $1000 prize, but in addition you won the $100 prize for the same accomplishments". Maybe that's not really a bad thing, given that Sebastian was instrumental in PureODD and ProcMod. But it does rub me the wrong way.
Why is it demeaning? Honest question. Social niceties sometimes go sailing right past me, so I like to be told if I'm accidentally doing something offensive.
Hi Hugh, when checking my issues, I realized that there is a mistake in the rephrasing of the specification of the @match attribute (which affects the spec and the documentation). Is it still possible to push changes tomorrow morning? If so, do I push directly to release-3.0.0 by first changing my default branch from "dev" to "release-3.0.0" with the command "git checkout release-3.0.0" and then pushing my changes there? Or is it better to re-open the issue and do the changes in the next release? Best, Martina -----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Hugh Cayless Gesendet: Mittwoch, 23. März 2016 15:56 An: TEI Council Betreff: [tei-council] Getting ready for 3.0.0 Hi All, Release 3.0.0 is coming up in less than a week! I've started a draft of the release notes here: https://docs.google.com/document/d/1htSJpqjKv4pe-N3Oelo70fDJGOrkD297B7Aa4QQC... Please add things you've worked on that you think should be in the list, and Lou, James, and Magdalena may want to modify and add to what I have down for Pure ODD and ProcMod. I've also started a section dedicating the release to Sebastian's memory. Additions, suggestions, and corrections are most welcome. I'll turn this into TEI and commit it on Sunday evening, so you have until then to modify it. I've put a fresh build of the release branch up at http://teic.github.io/TEI/. Please take some time this week to proofread and push changes to the release-3.0.0 branch. All the best, Hugh -- 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
Hi Martina, If it's a change in prose and/or an error being fixed, then go ahead and commit it to the release branch. If you haven't yet checked out the release branch you'll want to do git checkout -b release-3.0.0 origin/release-3.0.0 Sent from my phone.
On Mar 27, 2016, at 19:58, Scholger, Martina (martina.scholger@uni-graz.at)
wrote: Hi Hugh,
when checking my issues, I realized that there is a mistake in the rephrasing of the specification of the @match attribute (which affects the spec and the documentation). Is it still possible to push changes tomorrow morning? If so, do I push directly to release-3.0.0 by first changing my default branch from "dev" to "release-3.0.0" with the command "git checkout release-3.0.0" and then pushing my changes there? Or is it better to re-open the issue and do the changes in the next release?
Best, Martina
-----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Hugh Cayless Gesendet: Mittwoch, 23. März 2016 15:56 An: TEI Council Betreff: [tei-council] Getting ready for 3.0.0
Hi All,
Release 3.0.0 is coming up in less than a week! I've started a draft of the release notes here: https://docs.google.com/document/d/1htSJpqjKv4pe-N3Oelo70fDJGOrkD297B7Aa4QQC...
Please add things you've worked on that you think should be in the list, and Lou, James, and Magdalena may want to modify and add to what I have down for Pure ODD and ProcMod.
I've also started a section dedicating the release to Sebastian's memory. Additions, suggestions, and corrections are most welcome. I'll turn this into TEI and commit it on Sunday evening, so you have until then to modify it.
I've put a fresh build of the release branch up at http://teic.github.io/TEI/. Please take some time this week to proofread and push changes to the release-3.0.0 branch.
All the best, Hugh -- 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 -- 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
Hi Hugh, thank you! I pushed the file to release-3.0.0. Do I have to do anything else, since the branch is now 1 commit ahead of dev? Or do you merge everything back to dev at the time of the release? Best, Martina -----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Hugh Cayless Gesendet: Montag, 28. März 2016 02:54 An: tei-council@lists.tei-c.org Betreff: Re: [tei-council] Getting ready for 3.0.0 Hi Martina, If it's a change in prose and/or an error being fixed, then go ahead and commit it to the release branch. If you haven't yet checked out the release branch you'll want to do git checkout -b release-3.0.0 origin/release-3.0.0 Sent from my phone.
On Mar 27, 2016, at 19:58, Scholger, Martina (martina.scholger@uni-graz.at)
wrote: Hi Hugh,
when checking my issues, I realized that there is a mistake in the rephrasing of the specification of the @match attribute (which affects the spec and the documentation). Is it still possible to push changes tomorrow morning? If so, do I push directly to release-3.0.0 by first changing my default branch from "dev" to "release-3.0.0" with the command "git checkout release-3.0.0" and then pushing my changes there? Or is it better to re-open the issue and do the changes in the next release?
Best, Martina
-----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Hugh Cayless Gesendet: Mittwoch, 23. März 2016 15:56 An: TEI Council Betreff: [tei-council] Getting ready for 3.0.0
Hi All,
Release 3.0.0 is coming up in less than a week! I've started a draft of the release notes here: https://docs.google.com/document/d/1htSJpqjKv4pe-N3Oelo70fDJGOrkD297B7Aa4QQC...
Please add things you've worked on that you think should be in the list, and Lou, James, and Magdalena may want to modify and add to what I have down for Pure ODD and ProcMod.
I've also started a section dedicating the release to Sebastian's memory. Additions, suggestions, and corrections are most welcome. I'll turn this into TEI and commit it on Sunday evening, so you have until then to modify it.
I've put a fresh build of the release branch up at http://teic.github.io/TEI/. Please take some time this week to proofread and push changes to the release-3.0.0 branch.
All the best, Hugh -- 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 -- 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 -- 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
participants (3)
-
Hugh Cayless
-
Scholger, Martina (martina.scholger@uni-graz.at)
-
Syd Bauman