Getting code into the "full release"--what's the deadline?
Hi Tom, I would like a clearer definition of how/when we are going to roll out the "full release" after next week's full build. In an ideal world, everything that we wanted to show in our Feb 25th demos would be checked into git by this Friday, tested next week during the Build, and then released in one big beautiful release the following week, after which we'd only re-release modules that had catastrophic bugs found and fixed, until some time in March when we'd do another minor build/release. However, I know that some (all?) of the domains are planning to finish writing code for the demos right up till the bitter end, which leaves us in an awkward position, because we can't have people checking in code on midnight on Sunday the 24th of Feb and expecting their code to make it into "the" release--we'd have no time to test and release it. So clearly we need to establish a deadline for getting stuff into the big Feb release--and I don't think telling people that tomorrow is the deadline would go over too well. What were you envisioning? Nomi
participants (1)
-
Nomi Harris