So I'm clear, this also means that from Saturday morning (call it 6:00 UTC) until you give the OK (assuming the original schedule) I shouldn't count on having access to any of the source code, right?
And when you do give the OK, I should plan on rebasing whatever I'm working on to the new Git repo. There, did I use at least one Git term correctly? This is not a problem, just making sure I understand what I'll have access to when. Besides, I have a couple of retaining walls to build and can easily spend all weekend without needing to touch my keyboard ;). Erick On Tue, Jan 19, 2016 at 5:53 AM, Dawid Weiss <[email protected]> wrote: >> This works for me as long as we don't have to respin any of the two ongoing >> releases (5.3.2 and 5.4.1) so that the releases will be done by the time >> that we start the migration. > > Good point. I think it makes sense to wait for these as they'd be then > properly tagged in git, etc. If it happens before the weekend, good, > otherwise we'll postpone. > > Dawid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
