Closed schanzer closed 2 years ago
@flannery-denny @retabak draft schedule ready for comment, possibly/likely on our call today?
@schanzer Thanks for putting this together.
We have trainings scheduled throughout the month of June, so it seems to me that all workbook and peardeck updates should be completed before June 1.
To my mind, in order to turn edits around, this means that we need printed copies of the workbooks in hand by May 1 so we have to time to read carefully, send back edits, and get copies printed for in-person workshops.
My hunch is that in order for us to proofread on the computer before we send it to Lulu, new lessons and accompanying printed materials need to be completed by April 1. (In my experience we spend a fairly small percentage of our time actually making new lessons and if we prioritized our time with this deadline in mind, it would be quite achievable... would you agree?)
Additional reality that makes this earlier deadline particularly important is that I produce a music festival every May, the weekend after mother's day (Swamp in the City is scheduled May 12-15 this year), which makes me unavailable to do much Bootstrap work during the second or third week of May. And later in May there's Memorial Day :)
I'm a little less clear about the fall deadline being end of September.
And am curious to note that next year's spring release will go out a month sooner than this year's.
Also, I love that there's a time on the framework for thinking about new lessons for June's release. I'd love to see a similar time noted for Hour of Code lesson thinking and the Winter release.
@flannery-denny I'm fine moving the workbook pages to May 1, and I've added the HOC thinking as November date.
But why do PearDeck updates need to be completed before the start of June? We regularly make small changes and improvements well after we start training, whereas workbooks really need to be finalized to go to print. Lessons are updated similarly.
The September deadline is a deployment deadline, not an authoring one. We inevitably find small fixes that need to be made in the first few weeks of school, so tagging a release before then makes maintenance a lot harder.
@schanzer Based on the comment I received by email, I thought we needed a phone call. Realized you edited the issue. I've edited it more. If it works for you, great. If you want to discuss, lmk when you're available.
All events added to Team Calendar as recurring reminders
Third week of January
spring20xy
releasefall20xy
branch,fall20xy
April 1
Mid April
First week of May
Second week of May
fall20xy
workbooksThird week of May
June 1
Last week of June
fall20xy
materials to websitelatest
alias tofall20xy
Last week of September
fall20xy
releasespring20xy
branchMid October
Last week of December
spring20xy
materials to websitelatest
alias tospring20xy