> Yes, please. I think that build stability in general are a big problem. > And OOM issues specifically seem to be against AsterixDBs goal of not falling > over when memory gets tight. > So we probably should not release, if that’s something that everybody has a > high chance of running into on first try. >
I went ahead and merged a patch to disable the feeds execution tests, hopefully this will stop the OOM failures from interfering with builds of totally unrelated patches. > Actually, I think that we should find a better way to merge the documentation > and the website as they both are based on markdown and so it should be > feasible to use the same translation to HTML for both. I’m not sure how much > work that is and if that’s a option for the release, but I think that it > would be good if we could agree that that’s the goal. > I think it's ok if we want to use Jekyll for both, but they should remain separate in terms of maintenance and build. The docs have to live with the code IMO, because they are (or at least should be) very tightly coupled in a sense. The website doesn't have that quality at all, in my mind, there's no "release" of the website in the same sense that we have for AsterixDB. - Ian
