Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[benedikte.holm]

I've found the following bug when using the qt-4.8.0:

https://bugs.webkit.org/show_bug.cgi?id=81699

it is a bit critical for me.
Do I have to fill  in bugreports.qt-project.org ?


[Benedikte] >> No, please don't. It will only be marked as reported upstream 
and closed again.
You need to track the issue on the WebKit tracker for this one.

/Benedikte




>
> The solution then _could_ be to apply changes to the normal 4.8 branch,
> and then we can cherry-pick only those changes on top of the current SHA1
> and tag that. (A tag can be a commit, alas, does _not_ have to be a SHA1
> from any of the branches. So, it's fully possible.)


regards.
Haithem.

*
"If you ask a question - you will be a fool for 5 minutes, otherwise
ignorant for rest of your life"
*
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.qt-project.org/pipermail/development/attachments/20120321/bfd5e0a5/attachment.html

--

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


End of Development Digest, Vol 6, Issue 67
**




-- 
"If you ask a question - you will be a fool for 5 minutes, otherwise ignorant 
for rest of your life"

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[haithem rahmani]

sorry I forgot to edit the subject...



> >On 20.3.2012 11.11, "marius.storm-ol...@nokia.com"
> > > wrote:
> > >
> > >>Please don't create the tags yet though. I've heard that there are a
> > >>couple of things that needs to be fixed first, though I have not
> received
> > >>an email on the issues yet.
> > >
> > >
> > >If there is something critical, we can of course fix. But since 4.8.1 is
> > >done without a branch, we can not easily pick any single items into the
> > >source. We would by default need to take in all the contributions up
> until
> > >the fix, which causes all items to be re-done and tested. As there is a
> > >large amount of eagerly waited fixes already in 4.8.1 I would not like
> to
> > >wait a couple of more weeks with it (as would be the case if we start
> over
> > >with the testing).
> >
> > The thing is, if there's issues that needs to be fixed coming from the
> > legal scan, we have no option, we need to fix them before we can
> > distribute the package.
> >
>
> I've found the following bug when using the qt-4.8.0:
>
> https://bugs.webkit.org/show_bug.cgi?id=81699
>
> it is a bit critical for me.
> Do I have to fill  in bugreports.qt-project.org ?
>
>
>
> >
> > The solution then _could_ be to apply changes to the normal 4.8 branch,
> > and then we can cherry-pick only those changes on top of the current SHA1
> > and tag that. (A tag can be a commit, alas, does _not_ have to be a SHA1
> > from any of the branches. So, it's fully possible.)
>
>
> regards.
> Haithem.
>
> *
> "If you ask a question - you will be a fool for 5 minutes, otherwise
> ignorant for rest of your life"
> *
> -- next part --
> An HTML attachment was scrubbed...
> URL:
> http://lists.qt-project.org/pipermail/development/attachments/20120321/bfd5e0a5/attachment.html
>
> --
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
>
> End of Development Digest, Vol 6, Issue 67
> **
>



-- 
*
"If you ask a question - you will be a fool for 5 minutes, otherwise
ignorant for rest of your life"
*
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[marius.storm-olsen]

On 3/20/12 11:56 AM, "ext Turunen Tuukka"  wrote:

>
>On 20.3.2012 11.11, "marius.storm-ol...@nokia.com"
> wrote:
>
>>Please don't create the tags yet though. I've heard that there are a
>>couple of things that needs to be fixed first, though I have not received
>>an email on the issues yet.
>
>
>If there is something critical, we can of course fix. But since 4.8.1 is
>done without a branch, we can not easily pick any single items into the
>source. We would by default need to take in all the contributions up until
>the fix, which causes all items to be re-done and tested. As there is a
>large amount of eagerly waited fixes already in 4.8.1 I would not like to
>wait a couple of more weeks with it (as would be the case if we start over
>with the testing).

The thing is, if there's issues that needs to be fixed coming from the
legal scan, we have no option, we need to fix them before we can
distribute the package.

The solution then _could_ be to apply changes to the normal 4.8 branch,
and then we can cherry-pick only those changes on top of the current SHA1
and tag that. (A tag can be a commit, alas, does _not_ have to be a SHA1
from any of the branches. So, it's fully possible.)

-- 
.marius

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[Turunen Tuukka]

On 20.3.2012 11.11, "marius.storm-ol...@nokia.com"
 wrote:

>Please don't create the tags yet though. I've heard that there are a
>couple of things that needs to be fixed first, though I have not received
>an email on the issues yet.


If there is something critical, we can of course fix. But since 4.8.1 is
done without a branch, we can not easily pick any single items into the
source. We would by default need to take in all the contributions up until
the fix, which causes all items to be re-done and tested. As there is a
large amount of eagerly waited fixes already in 4.8.1 I would not like to
wait a couple of more weeks with it (as would be the case if we start over
with the testing).

4.8.1 is the first patch release of 4.8 series - definitely not the last.
So for any minor problems, I would like to include fixes for the 4.8.2
release (and to make it quite soon, in less than 2 months).

Yours,

Tuukka

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[marius.storm-olsen]

Please don't create the tags yet though. I've heard that there are a
couple of things that needs to be fixed first, though I have not received
an email on the issues yet.

-- 
.marius

On 3/20/12 9:20 AM, "ext Sergio Ahumada"  wrote:

>On 03/20/2012 09:08 AM, ext Turunen Tuukka wrote:
>>
>> Hi Girish,
>>
>> No, we have not yet gained these. Who can create them?
>>
>> The persons who should have the rights are:
>>
>> iikka.ekl...@digia.com
>> akseli.salova...@digia.com
>> janne.antt...@digia.com
>>
>> For the 4.8.1 we will just tag, as it was decided that we do 4.8.1
>>without
>> a branch. Naturally having a branch is good, but it is possible to do
>> without as well.
>>
>> The release is ready, and so are the installers. We need confirmation
>>from
>> Nokia when they are ready to release. As the Qt Project does not have
>> distribution server for installers available now, we need to use Nokia's
>> servers (the same ones where all lgpl packages until 4.8.0 are). Digia's
>> existing servers are used for Qt Commercial distribution, and most
>>likely
>> can not take the load of all commercial and lgpl users rushing to get
>>the
>> new version.
>>
>> Yours,
>>
>
>Hi,
>
>I've created a "Qt Release Team" group in Gerrit and I've added those
>people to the group. I think that's enough to create tags, not for
>branches yet though.
>
>Cheers,
>-- 
>Sergio Ahumada
>___
>Releasing mailing list
>releas...@qt-project.org
>http://lists.qt-project.org/mailman/listinfo/releasing
>


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[Sergio Ahumada]

On 03/20/2012 09:08 AM, ext Turunen Tuukka wrote:
>
> Hi Girish,
>
> No, we have not yet gained these. Who can create them?
>
> The persons who should have the rights are:
>
> iikka.ekl...@digia.com
> akseli.salova...@digia.com
> janne.antt...@digia.com
>
> For the 4.8.1 we will just tag, as it was decided that we do 4.8.1 without
> a branch. Naturally having a branch is good, but it is possible to do
> without as well.
>
> The release is ready, and so are the installers. We need confirmation from
> Nokia when they are ready to release. As the Qt Project does not have
> distribution server for installers available now, we need to use Nokia's
> servers (the same ones where all lgpl packages until 4.8.0 are). Digia's
> existing servers are used for Qt Commercial distribution, and most likely
> can not take the load of all commercial and lgpl users rushing to get the
> new version.
>
> Yours,
>

Hi,

I've created a "Qt Release Team" group in Gerrit and I've added those 
people to the group. I think that's enough to create tags, not for 
branches yet though.

Cheers,
-- 
Sergio Ahumada
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[Turunen Tuukka]

Hi Girish,

No, we have not yet gained these. Who can create them?

The persons who should have the rights are:

iikka.ekl...@digia.com
akseli.salova...@digia.com
janne.antt...@digia.com

For the 4.8.1 we will just tag, as it was decided that we do 4.8.1 without
a branch. Naturally having a branch is good, but it is possible to do
without as well. 

The release is ready, and so are the installers. We need confirmation from
Nokia when they are ready to release. As the Qt Project does not have
distribution server for installers available now, we need to use Nokia's
servers (the same ones where all lgpl packages until 4.8.0 are). Digia's
existing servers are used for Qt Commercial distribution, and most likely
can not take the load of all commercial and lgpl users rushing to get the
new version. 

Yours,

--
Tuukka Turunen
Director, Qt Commercial R&D
Digia Plc
Piippukatu 11, 40100 Jyväskylä, Finland
 
Visit us at: www.digia.com or qt.digia.com
 






On 20.3.2012 7.15, "Girish Ramakrishnan"  wrote:

>Hi Tuuka,
>Following this up - did your release team members get access to branch
>and tag?
>
>Thanks,
>Girish
>
>2012/3/16 Turunen Tuukka :
>> Excellent, thank you very much for the trust.
>>
>>
>> We naturally want to have all release content from the Qt Project. If
>>some
>> patch is needed, it is done via gerrit. This is the case with 4.8.1
>>already,
>> and will be also in the future.
>>
>>
>> For practicalities, is it possible to have some members of the release
>>team
>> with right to tag etc?
>>
>>
>> Yours,
>>
>> --
>>
>> --
>>
>> Tuukka
>>
>>
>> lars.kn...@nokia.com kirjoitti 16.3.2012 13:39:
>>
>> Hi Tukka,
>>
>> let's make this simple. You and Digia stepped up to make 4.8 patch level
>> releases. So far nobody else has, so the 'release manager' job simply
>> falls into your hands.
>>
>> Adding some patches to the release and deciding what exactly goes out
>> should be at the discretion of the one doing the releases, ideally in
>> coordination with a team that has the same interest.
>>
>> Having said that, all patches in a qt-project release should also be
>> inside the git repo on qt-project.org. I am ok for another exception for
>> 4.8.1 (if required), but would really like to see that we have it all
>> upstream afterwards.
>>
>> The release can however be a branch from 4.8, and contain additional
>> patches. But these should live inside a release branch on gerrit.
>>
>> Cheers,
>> Lars
>>
>>
>> On 3/15/12 8:50 AM, "ext Turunen Tuukka" 
>>wrote:
>>
>>>
>>>
>>>On 5.3.2012 18.21, "Oswald Buddenhagen" 
>>
>>>wrote:
>>>
On Mon, Mar 05, 2012 at 03:24:04PM +, ext Salovaara Akseli wrote:
> At the moment we are following content of
> http://qt.gitorious.org/qt/qt/commits/4.8 branch on our internal
> repository. We would like to provide Qt 4.8.1 branch on
> Gitorious\Gerrit in order to enable you more visibility for the
> progress & content. Could Gitorious\Gerrit administrators enable such
> branch and later tag final 4.8.1 release?
>
i understand that this is the commercial qt release with additional
patches not sanctioned by the qt project (yet). i can only repeat my
offer from the last time: we create a 4.8.1-digia branch you can push
your stuff into and put a v4.8.1-digia tag on.
>>>
>>>No, this is intended to be the open-source 4.8.1 release by the Qt
>>>Project.
>>>
>>>For us it is fine if someone else does the releases, but since about
>>>no-one seems to care making patch release out of 4.8 we have stepped up
>>>and offered to create the releases.
>>>
>>>For Qt Commercial viewpoint it is easier for us to base our releases on
>>>patch releases from Qt Project. It gets hard eventually if we would
>>>continue releasing commercial only patch releases on top of 4.8.0. And I
>>>am sure there are also open-source users who wish to get patch releases
>>>for 4.8.
>>>
>>>Yes, there is already some amount of patches out after the proposed
>>>4.8.1.
From our viewpoint they should go into 4.8.2.
>>>
>>>If needed, of course we can rebase 4.8.1 and redo the testing, but it is
>>>already a release with a large number of fixes.
>>>
>>>It is the decision of the Qt Project what we want to do about releases.
>>>I
>>>would like to have 4.8.1 released, and Digia is ready to help also with
>>>the subsequent releases. If others are also interested in making the
>>>releases, great.
>>>

you still have all rights necessary to push refs/heads/4.7-digia and
refs/tags/v4.7.5-digia if you finally decide to actually do so. i
suggest you do that and then we see about 4.8. i'm on irc if you have
questions about the execution.
>>>
>>>
>>>Regarding 4.7.5 we have created the open-source installers ages ago, but
>>>since there is no place for Qt Project to distribute the releases at the
>>>moment, they are not out. We wanted that the installers and code for
>>>4.7.5
>>>are released at the same time, but since there did not seem to be
>>>interest
>>>in the commu

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[Girish Ramakrishnan]

Hi Tuuka,
Following this up - did your release team members get access to branch and tag?

Thanks,
Girish

2012/3/16 Turunen Tuukka :
> Excellent, thank you very much for the trust.
>
>
> We naturally want to have all release content from the Qt Project. If some
> patch is needed, it is done via gerrit. This is the case with 4.8.1 already,
> and will be also in the future.
>
>
> For practicalities, is it possible to have some members of the release team
> with right to tag etc?
>
>
> Yours,
>
> --
>
> --
>
> Tuukka
>
>
> lars.kn...@nokia.com kirjoitti 16.3.2012 13:39:
>
> Hi Tukka,
>
> let's make this simple. You and Digia stepped up to make 4.8 patch level
> releases. So far nobody else has, so the 'release manager' job simply
> falls into your hands.
>
> Adding some patches to the release and deciding what exactly goes out
> should be at the discretion of the one doing the releases, ideally in
> coordination with a team that has the same interest.
>
> Having said that, all patches in a qt-project release should also be
> inside the git repo on qt-project.org. I am ok for another exception for
> 4.8.1 (if required), but would really like to see that we have it all
> upstream afterwards.
>
> The release can however be a branch from 4.8, and contain additional
> patches. But these should live inside a release branch on gerrit.
>
> Cheers,
> Lars
>
>
> On 3/15/12 8:50 AM, "ext Turunen Tuukka"  wrote:
>
>>
>>
>>On 5.3.2012 18.21, "Oswald Buddenhagen" 
>
>>wrote:
>>
>>>On Mon, Mar 05, 2012 at 03:24:04PM +, ext Salovaara Akseli wrote:
 At the moment we are following content of
 http://qt.gitorious.org/qt/qt/commits/4.8 branch on our internal
 repository. We would like to provide Qt 4.8.1 branch on
 Gitorious\Gerrit in order to enable you more visibility for the
 progress & content. Could Gitorious\Gerrit administrators enable such
 branch and later tag final 4.8.1 release?

>>>i understand that this is the commercial qt release with additional
>>>patches not sanctioned by the qt project (yet). i can only repeat my
>>>offer from the last time: we create a 4.8.1-digia branch you can push
>>>your stuff into and put a v4.8.1-digia tag on.
>>
>>No, this is intended to be the open-source 4.8.1 release by the Qt
>>Project.
>>
>>For us it is fine if someone else does the releases, but since about
>>no-one seems to care making patch release out of 4.8 we have stepped up
>>and offered to create the releases.
>>
>>For Qt Commercial viewpoint it is easier for us to base our releases on
>>patch releases from Qt Project. It gets hard eventually if we would
>>continue releasing commercial only patch releases on top of 4.8.0. And I
>>am sure there are also open-source users who wish to get patch releases
>>for 4.8.
>>
>>Yes, there is already some amount of patches out after the proposed 4.8.1.
>>>From our viewpoint they should go into 4.8.2.
>>
>>If needed, of course we can rebase 4.8.1 and redo the testing, but it is
>>already a release with a large number of fixes.
>>
>>It is the decision of the Qt Project what we want to do about releases. I
>>would like to have 4.8.1 released, and Digia is ready to help also with
>>the subsequent releases. If others are also interested in making the
>>releases, great.
>>
>>>
>>>you still have all rights necessary to push refs/heads/4.7-digia and
>>>refs/tags/v4.7.5-digia if you finally decide to actually do so. i
>>>suggest you do that and then we see about 4.8. i'm on irc if you have
>>>questions about the execution.
>>
>>
>>Regarding 4.7.5 we have created the open-source installers ages ago, but
>>since there is no place for Qt Project to distribute the releases at the
>>moment, they are not out. We wanted that the installers and code for 4.7.5
>>are released at the same time, but since there did not seem to be interest
>>in the community to do that, we have not been pushing.
>>
>>Source code of 4.7.5 open-source is available at
>>http://qt.gitorious.org/qt/qt/commits/4.8 - and we do have the
>
>>open-source installers ready if those are needed. There just needs to be a
>>location where these can be placed.
>>
>>I can understand the lack of interest for 4.7.5, but 4.8.1 is a different
>>case. It gets really ugly if Qt Project does not make any patch releases
>>out of 4.8.
>>
>>Yours,
>>
>> Tuukka
>>
>>___
>>Development mailing list
>>tuukka.turu...@digia.com
>>http://qt.gitorious.org/qt/qt/commits/4.8
>
>
>
>
> ___
> Releasing mailing list
> releas...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/releasing
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[Turunen Tuukka]

Excellent, thank you very much for the trust.


We naturally want to have all release content from the Qt Project. If some 
patch is needed, it is done via gerrit. This is the case with 4.8.1 already, 
and will be also in the future.


For practicalities, is it possible to have some members of the release team 
with right to tag etc?


Yours,

--

--

Tuukka



lars.kn...@nokia.com kirjoitti 16.3.2012 13:39:

Hi Tukka,

let's make this simple. You and Digia stepped up to make 4.8 patch level
releases. So far nobody else has, so the 'release manager' job simply
falls into your hands.

Adding some patches to the release and deciding what exactly goes out
should be at the discretion of the one doing the releases, ideally in
coordination with a team that has the same interest.

Having said that, all patches in a qt-project release should also be
inside the git repo on qt-project.org. I am ok for another exception for
4.8.1 (if required), but would really like to see that we have it all
upstream afterwards.

The release can however be a branch from 4.8, and contain additional
patches. But these should live inside a release branch on gerrit.

Cheers,
Lars


On 3/15/12 8:50 AM, "ext Turunen Tuukka" 
mailto:tuukka.turu...@digia.com>> wrote:

>
>
>On 5.3.2012 18.21, "Oswald Buddenhagen" 
>mailto:tuukka.turu...@digia.com>>
>wrote:
>
>>On Mon, Mar 05, 2012 at 03:24:04PM +, ext Salovaara Akseli wrote:
>>> At the moment we are following content of
>>> http://qt.gitorious.org/qt/qt/commits/4.8 branch on our internal
>>> repository. We would like to provide Qt 4.8.1 branch on
>>> Gitorious\Gerrit in order to enable you more visibility for the
>>> progress & content. Could Gitorious\Gerrit administrators enable such
>>> branch and later tag final 4.8.1 release?
>>>
>>i understand that this is the commercial qt release with additional
>>patches not sanctioned by the qt project (yet). i can only repeat my
>>offer from the last time: we create a 4.8.1-digia branch you can push
>>your stuff into and put a v4.8.1-digia tag on.
>
>No, this is intended to be the open-source 4.8.1 release by the Qt
>Project.
>
>For us it is fine if someone else does the releases, but since about
>no-one seems to care making patch release out of 4.8 we have stepped up
>and offered to create the releases.
>
>For Qt Commercial viewpoint it is easier for us to base our releases on
>patch releases from Qt Project. It gets hard eventually if we would
>continue releasing commercial only patch releases on top of 4.8.0. And I
>am sure there are also open-source users who wish to get patch releases
>for 4.8.
>
>Yes, there is already some amount of patches out after the proposed 4.8.1.
>>From our viewpoint they should go into 4.8.2.
>
>If needed, of course we can rebase 4.8.1 and redo the testing, but it is
>already a release with a large number of fixes.
>
>It is the decision of the Qt Project what we want to do about releases. I
>would like to have 4.8.1 released, and Digia is ready to help also with
>the subsequent releases. If others are also interested in making the
>releases, great.
>
>>
>>you still have all rights necessary to push refs/heads/4.7-digia and
>>refs/tags/v4.7.5-digia if you finally decide to actually do so. i
>>suggest you do that and then we see about 4.8. i'm on irc if you have
>>questions about the execution.
>
>
>Regarding 4.7.5 we have created the open-source installers ages ago, but
>since there is no place for Qt Project to distribute the releases at the
>moment, they are not out. We wanted that the installers and code for 4.7.5
>are released at the same time, but since there did not seem to be interest
>in the community to do that, we have not been pushing.
>
>Source code of 4.7.5 open-source is available at
>http://qt.gitorious.org/qt/qt/commits/4.8 - and we do have the
>open-source installers ready if those are needed. There just needs to be a
>location where these can be placed.
>
>I can understand the lack of interest for 4.7.5, but 4.8.1 is a different
>case. It gets really ugly if Qt Project does not make any patch releases
>out of 4.8.
>
>Yours,
>
> Tuukka
>
>___
>Development mailing list
>tuukka.turu...@digia.com
>http://qt.gitorious.org/qt/qt/commits/4.8



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[lars.knoll]

Hi Tukka,

let's make this simple. You and Digia stepped up to make 4.8 patch level
releases. So far nobody else has, so the 'release manager' job simply
falls into your hands.

Adding some patches to the release and deciding what exactly goes out
should be at the discretion of the one doing the releases, ideally in
coordination with a team that has the same interest.

Having said that, all patches in a qt-project release should also be
inside the git repo on qt-project.org. I am ok for another exception for
4.8.1 (if required), but would really like to see that we have it all
upstream afterwards.

The release can however be a branch from 4.8, and contain additional
patches. But these should live inside a release branch on gerrit.

Cheers,
Lars


On 3/15/12 8:50 AM, "ext Turunen Tuukka"  wrote:

>
>
>On 5.3.2012 18.21, "Oswald Buddenhagen" 
>wrote:
>
>>On Mon, Mar 05, 2012 at 03:24:04PM +, ext Salovaara Akseli wrote:
>>> At the moment we are following content of
>>> http://qt.gitorious.org/qt/qt/commits/4.8 branch on our internal
>>> repository. We would like to provide Qt 4.8.1 branch on
>>> Gitorious\Gerrit in order to enable you more visibility for the
>>> progress & content. Could Gitorious\Gerrit administrators enable such
>>> branch and later tag final 4.8.1 release?
>>> 
>>i understand that this is the commercial qt release with additional
>>patches not sanctioned by the qt project (yet). i can only repeat my
>>offer from the last time: we create a 4.8.1-digia branch you can push
>>your stuff into and put a v4.8.1-digia tag on.
>
>No, this is intended to be the open-source 4.8.1 release by the Qt
>Project.
>
>For us it is fine if someone else does the releases, but since about
>no-one seems to care making patch release out of 4.8 we have stepped up
>and offered to create the releases.
>
>For Qt Commercial viewpoint it is easier for us to base our releases on
>patch releases from Qt Project. It gets hard eventually if we would
>continue releasing commercial only patch releases on top of 4.8.0. And I
>am sure there are also open-source users who wish to get patch releases
>for 4.8.
>
>Yes, there is already some amount of patches out after the proposed 4.8.1.
>>From our viewpoint they should go into 4.8.2.
>
>If needed, of course we can rebase 4.8.1 and redo the testing, but it is
>already a release with a large number of fixes.
>
>It is the decision of the Qt Project what we want to do about releases. I
>would like to have 4.8.1 released, and Digia is ready to help also with
>the subsequent releases. If others are also interested in making the
>releases, great.
>
>>
>>you still have all rights necessary to push refs/heads/4.7-digia and
>>refs/tags/v4.7.5-digia if you finally decide to actually do so. i
>>suggest you do that and then we see about 4.8. i'm on irc if you have
>>questions about the execution.
>
>
>Regarding 4.7.5 we have created the open-source installers ages ago, but
>since there is no place for Qt Project to distribute the releases at the
>moment, they are not out. We wanted that the installers and code for 4.7.5
>are released at the same time, but since there did not seem to be interest
>in the community to do that, we have not been pushing.
>
>Source code of 4.7.5 open-source is available at
>https://qt.gitorious.org/qt/digia-qt/commits/4.7.5 - and we do have the
>open-source installers ready if those are needed. There just needs to be a
>location where these can be placed.
>
>I can understand the lack of interest for 4.7.5, but 4.8.1 is a different
>case. It gets really ugly if Qt Project does not make any patch releases
>out of 4.8.
>
>Yours,
>
>   Tuukka
>
>___
>Development mailing list
>Development@qt-project.org
>http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Releasing] Qt 4.8.1 release during week 11/2012

[Turunen Tuukka]

On 5.3.2012 18.21, "Oswald Buddenhagen" 
wrote:

>On Mon, Mar 05, 2012 at 03:24:04PM +, ext Salovaara Akseli wrote:
>> At the moment we are following content of
>> http://qt.gitorious.org/qt/qt/commits/4.8 branch on our internal
>> repository. We would like to provide Qt 4.8.1 branch on
>> Gitorious\Gerrit in order to enable you more visibility for the
>> progress & content. Could Gitorious\Gerrit administrators enable such
>> branch and later tag final 4.8.1 release?
>> 
>i understand that this is the commercial qt release with additional
>patches not sanctioned by the qt project (yet). i can only repeat my
>offer from the last time: we create a 4.8.1-digia branch you can push
>your stuff into and put a v4.8.1-digia tag on.

No, this is intended to be the open-source 4.8.1 release by the Qt Project.

For us it is fine if someone else does the releases, but since about
no-one seems to care making patch release out of 4.8 we have stepped up
and offered to create the releases.

For Qt Commercial viewpoint it is easier for us to base our releases on
patch releases from Qt Project. It gets hard eventually if we would
continue releasing commercial only patch releases on top of 4.8.0. And I
am sure there are also open-source users who wish to get patch releases
for 4.8.

Yes, there is already some amount of patches out after the proposed 4.8.1.
>From our viewpoint they should go into 4.8.2.

If needed, of course we can rebase 4.8.1 and redo the testing, but it is
already a release with a large number of fixes.

It is the decision of the Qt Project what we want to do about releases. I
would like to have 4.8.1 released, and Digia is ready to help also with
the subsequent releases. If others are also interested in making the
releases, great.

>
>you still have all rights necessary to push refs/heads/4.7-digia and
>refs/tags/v4.7.5-digia if you finally decide to actually do so. i
>suggest you do that and then we see about 4.8. i'm on irc if you have
>questions about the execution.


Regarding 4.7.5 we have created the open-source installers ages ago, but
since there is no place for Qt Project to distribute the releases at the
moment, they are not out. We wanted that the installers and code for 4.7.5
are released at the same time, but since there did not seem to be interest
in the community to do that, we have not been pushing.

Source code of 4.7.5 open-source is available at
https://qt.gitorious.org/qt/digia-qt/commits/4.7.5 - and we do have the
open-source installers ready if those are needed. There just needs to be a
location where these can be placed.

I can understand the lack of interest for 4.7.5, but 4.8.1 is a different
case. It gets really ugly if Qt Project does not make any patch releases
out of 4.8.

Yours,

Tuukka

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development