Hi Marcus, Yes, the term "blocker" was discussed often. (Maybe we should add another flag "release_proposal"?) For me it is just a flag to let the release manager know that I would like to see a certain commit/fix included in the next release.
I think 4.1.4 would be the perfect moment to show our integration in the ASF, even if it is only a little logo. But I will leave it to the release manager to decide... Anyway, it is just two graphics. I can exchange them manually. ;-) Matthias Am 17.04.2017 um 09:21 schrieb Marcus: > Am 17.04.2017 um 01:17 schrieb Andrea Pescetti: >> Matthias Seidel wrote: >>> I would be happy to commit them and ask for 4.1.4. release >>> blocker... ;-) >> >> I would prefer to keep 4.1.4 for important bugfixes and commit this type >> of enhancements to trunk for 4.2.0, otherwise we risk to settle too much >> on 4.1.x for no reason. That said, I'm not the Release Manager, so >> please go ahead with committing to trunk (which must be done anyway) and >> then feel free to ask for 4.1.4 too if you wish! > > Matthias, thanks for your great work and enthusiasm. > > When thinking about the term "release blocker" I would expect some > serious problems that prevent the users from using OpenOffice or at > least a larger part of its functionality. > > A new graphic looks easy to handle but would also put the bar lower > for other issues. So, we shouldn't accept any new exceptions. IMHO we > have already enough. > > Therefore I second Andrea's opinion that this "fix" shouldn't go into > the 4.1.4 release. > > Marcus > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
smime.p7s
Description: S/MIME Cryptographic Signature
