[Development] Preparing to release repackaged version of Qt 4.8.3 with Digia copyrights

[Oleg Shparber]

Being a 3rd party observer and thoroughly reading all messages by Tuukkla I
anyway cannot understand the logic behind having 4.8.3-1 version instead of
suggested 4.8.4 with new copyrights, MinGW and SSL fixes.
What is wrong with releasing it right now and then process all the new
commits since 4.8.3 directly to 4.8.5? To my mind if a critical fix needs
to be released, 4.8.(N+1) can come out the next day or even hour after
4.8.N.

Thanks.

--
Oleg

On Fri, Oct 5, 2012 at 11:11 AM, Turunen Tuukka <Tuukka.Turunen at digia.com>wrote:

>
> On 4.10.2012 17.42, "Rafael Roquetto" <rafael.roquetto at kdab.com> wrote:
>
> >On Thu, Oct 04, 2012 at 01:11:19PM +0000, Turunen Tuukka wrote:
> >>
> >>
> >> My preference is towards releasing now and making proper 4.8.4 (with
> >>more
> >> content) later. It is true that getting the security fix in is also
> >> valuable and then we certainly need to call it 4.8.4.
> >
> >And what do you think about going down that road, instead? As suggested,
> >you do not need to do the full release cycle. Would that work? I think
> >that
> >would make everyone happy.
>
> It is true that there are many value adding improvements pending in the
> 4.8 branch - over 80 since 4.8.3.
>
> So we will not release 4.8.3-1 with the new copyrights and MinGW fix as
> advised by many of you.
>
> We will start work to make 4.8.4, which we should then be able to release
> in about two weeks. We will do that according to the defined release
> process of 4.8 in order not to cause confusion and reduce risk of
> regressions.
>
> Yours,
>
>                 Tuukka
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121005/4534f3f9/attachment.html>