0:28:49drmeisterThere is a bit of a problem with that - we have some things in the buildbot tied to dev. But we should probably change that rather than dev.
0:29:31Bikei mean that's why we have master versus dev, right
0:30:40drmeisterMartin has a lot of buildbot scripts that are tied to dev he tells me. He thinks it's going to be a lot of trouble sorting this out.
1:02:37drmeisterIf we built the docker image and AWS machine images off of a particular branch - which should we use?
1:02:46drmeisterWe have dev -> testing -> preview -> master
1:03:27Bikei guess preview or master, since we want one that's gone through tests?
1:03:36drmeisterI guess we should have multiple images, one for each branch.
1:03:59drmeisterWe might want a testing distributor
1:04:09drmeisterAnd a preview distributor and a master distributor.
1:04:44drmeisterI hear you though - if we want one right now it would probably be preview.
1:28:04drmeisterBike: To get back to the other question about defclass at compile time I got a backtrace with compile-file-serial
1:31:10drmeisterI thought this worked with ECL - but it doesn't!
1:31:43Bikeas for what we should do about it- we definitely want to make it known that it's a class at compile time, if nothing else for the find-class and typep optimizations
1:31:57Bikewe don't have to do that by defining a class, though, we can just recorde it in the compilation environment somewhere
1:32:02Bikebut then programmers can't learn about it