On terça-feira, 19 de fevereiro de 2013 16.42.44, Turunen Tuukka wrote: > Hi Thiago, > > The whole idea of 4.6.5 and 4.7.6 is to unfork these and unify. It has > never been about making a Digia specific release. We have no intention to > make any Digia specific 4.6 and 4.7 release - quite the opposite - we wish > to unify those releases that have been done earlier (and even then we > actually preferred in having the 4.6.4 and 4.7.5 release to be in the > right place, which was not possible at the time).
That's a great plan. But the plan does not seem to match reality. > It is hard to change history, but we can at least come up with such a > solution that where 4.6 and 4.7 branches end things are somewhat aligned. > > As discussed earlier the rationale for making 4.6.5 and 4.7.6 releases is: > > -> Do the copyrights change also in packages > -> Address important security vulnerabilities > -> "Unfork" 4.6 and 4.7 branches > > Š and all this done in such a way that does not take overwhelmingly high > amount of time as it is away from Qt 5 and 4.8 work. > > What we are proposing is somewhat the same as you listed as 'Plan II'. Plan II is fine. But note what I said about the branch: > >Alternative plan (Plan II): > >1) release Qt Project's 4.7.6 and announce that we're skipping one > >version > >number to align with a past commercial release by Digia, but that it > >won't > >happen again. This release must come from the 4.7 branch, not the > >4.7-digia > >branch. > > > >2) after that, Digia is allowed to release 4.7.6-digia. If we want to unify, then we need to merge the 4.7-digia branch into 4.7. If that's the plan, I will carefully review all the changes in that merge that apply to the modules I maintain. Whether we do that before or after the release, I don't care. What I care about is that the Qt Project's 4.7.5 or 4.7.6 release come from the 4.7 branch. Ditto for the 4.6.5 release and the 4.6 branch. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
