hi marcel releasing with not-known (but existing) bugs is something totally different than releasing with known, critical bugs that are trivial to fix.
i'd rather have it fixed instead of having the escalation overhead later on. angela On 09/04/15 17:11, "Marcel Reutegger" <[email protected]> wrote: >Hi, > >On 09/04/15 17:02, "Angela Schreiber" <[email protected]> wrote: >>i will attach to proposed fix to the issue right now so everyone >>can take a look and make an educated guess on whether this is >>considered a change too risky to be included in the release. > >I think the question is rather, are we OK releasing 1.2 with >this known issue and fix it e.g. in 1.2.1. > >IIUC this issue was already present in many previous Oak releases >and we still published them. > >Regards > Marcel >
