Hi, > So the problem here is where to draw the line. I think in a setup like we have > with lucene and solr in one codebase the chance to hit a bug within these 72h > is huge. This means the Release process is a huge pain each time. Then we > have bugs that justify a respin and some who don't. I looked at SOLR-5762 > and it seems this one should cause a respin but the LUCENE-5461 doesn't. It's > hard to draw that line since its pretty much up to the RM and then you get > heat if you draw that line. IMO we should improve our release process and > release a point release every week shortening the vote period for that to > maybe 24h. > That way we can get stuff out quickly and don't spend weeks on the release > process.
A similar thing was already discussed on the board. I think we have to stick with the 72 hours (for now?). We can do releases once per week; we can also do them "automatically" - the problem here is the GPG signature: It has to be done by a real person (the RM). A machine as RM is therefore not possible. One important thing is that the voting PMC members have to check the signatures. If they are not correct/trusted, the release fails. Everything else is open to the community. A failing test is not a problem for a release. We could theoretically release Lucene with all tests failing, as long as the signatures are OK :-) Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
