Hi all, Thanks for all of your work on the release today! I'm glad to know what the process looks like. Here are a few notes on today while the thoughts were still fresh in my head. Syd can feel to jump in with anything else. Hopefully, this will be useful for refining the process in the future: * Following the document's instructions under "1-2 weeks before release" would have been incredibly useful, so I apologize for not being on top of that! This is an aspect of the release it would be worth emphasizing for upcoming releases. * Some more detailed language on the relationship between git branches and Jenkins in TCW22 would have been helpful for me as a newcomer (nothing exhaustive; just some info on which builds you should be worried about at which point) * Other than the issue of circular dependencies, no hitches on 1-8, 10-15 that wouldn't have been fixed by my first point * TCW22 should be rewritten to expand upon instructions for stylesheets (particularly point #9). A lot of this will be duplicating information from pre-existing points. * I have no idea what happened with oXygen (step #17), but I'd love to hear more about it at some point * A few points that could afford to be languaged a bit: * #8 - particularly the parenthetical section * #14 - just to say that the package from Jenkins should be uploaded *not* included as a link in the the release notes (both options were used in the last two releases, but following the links provided to http://jenkins.tei-c.org/job/TEIP5/lastSuccessfulBuild/artifact/P5/tei-3.1.0..., for example, gives you a 404 error) This is all rather specific, in part because it seemed that things went smoothly overall. Please let me know if you have any questions, and thank you all again for everything today! -Sarah Sarah Stanley Office of Digital Research and Scholarship Strozier Library, Florida State University https://www.lib.fsu.edu/drs/ Twitter: https://twitter.com/sarcathtic
Thanks Sarah! This is really helpful stuff. I'll try to work on it this week while it's still fresh in my mind. Sent from my phone.
On Jul 10, 2017, at 20:42, Sarah S
wrote: Hi all,
Thanks for all of your work on the release today! I'm glad to know what the process looks like.
Here are a few notes on today while the thoughts were still fresh in my head. Syd can feel to jump in with anything else. Hopefully, this will be useful for refining the process in the future:
* Following the document's instructions under "1-2 weeks before release" would have been incredibly useful, so I apologize for not being on top of that! This is an aspect of the release it would be worth emphasizing for upcoming releases. * Some more detailed language on the relationship between git branches and Jenkins in TCW22 would have been helpful for me as a newcomer (nothing exhaustive; just some info on which builds you should be worried about at which point) * Other than the issue of circular dependencies, no hitches on 1-8, 10-15 that wouldn't have been fixed by my first point * TCW22 should be rewritten to expand upon instructions for stylesheets (particularly point #9). A lot of this will be duplicating information from pre-existing points. * I have no idea what happened with oXygen (step #17), but I'd love to hear more about it at some point
* A few points that could afford to be languaged a bit: * #8 - particularly the parenthetical section * #14 - just to say that the package from Jenkins should be uploaded *not* included as a link in the the release notes (both options were used in the last two releases, but following the links provided to http://jenkins.tei-c.org/job/TEIP5/lastSuccessfulBuild/artifact/P5/tei-3.1.0..., for example, gives you a 404 error)
This is all rather specific, in part because it seemed that things went smoothly overall.
Please let me know if you have any questions, and thank you all again for everything today!
-Sarah
Sarah Stanley Office of Digital Research and Scholarship Strozier Library, Florida State University https://www.lib.fsu.edu/drs/ Twitter: https://twitter.com/sarcathtic -- 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
Thanks for going the extra mile, Sarah. However, you don't get to take much, if any, blame for not being on top of the "1-2 weeks out" stuff. That's on me. A few other thoughts: * We had to change the permission bits of tei-install.sh on the server to allow execution. (I suppose would could have used the `source` builtin command, but either way, someone not familiar with the shell may well have been stymied.) * Sarah already covered this in general, but one particular example: we did not know which branch should be checked out when tagging (step 13). * The ant script for building oXygen framework (step 17) failed for both on my machine and Sarah's. Seems to have worked for Hugh. * Steps 1 & 2 under release day say "alpha" and "beta", but step 21 and the VERSION files themselves say 'a'. * The main content of release day step 1 should be moved to the "1-2 weeks before" section (for 1 week before), and then replaced with just something like "Make sure the README is reasonable".
Thanks Sarah! This is really helpful stuff. I'll try to work on it this week while it's still fresh in my mind.
participants (3)
-
Hugh Cayless
-
Sarah S
-
Syd Bauman