Meeting minutes from Qt release team meeting 17.02.2014

-        Feature freeze in effect now

o   Lars gave an exception to GL switching, QQuickWidget and the printing. 
Those will be taken in stable if not in dev when merge starts

o   Also agreed that it is ok to take SPDY in as well. reason for delay were in 
CI



-        Plan is to merge Qt 5.3 content from dev branch to stable tomorrow 
(18.2.2014)  morning (if fixes for merge conflicts from stable to dev are 
integrated successfully today)



-        Alpha release will be done as soon as possible, latest at the 
beginning of next week

o   Original plan for Alpha Thu 20.2.2014

o   It would be nice to get all changes related to those exceptions in before 
Alpha but we wouldn't delay alpha several days because of these.



-        Qt 4.8.6 status

o   new snapshot build available in 
http://download.qt-project.org/snapshots/qt/4.8/

§  mingw482 package included

§  some problems with two dll's (one missing, another one corrupted during 
packaging)

§  it is worth to try & test since dll's can be copied from mingw to 
qt4.8.6/bin folder. Akseli will sent details to ML



-        Next meeting Mon 24th Feb 2014 16:00 CET

Br,
Jani

Irc log below:
[17:00:49] <jaheikki3> akseli: iieklund: kkoehne: sahumada: thiago: fkleint: 
ZapB: tronical: wolfgang-b: vladimirM: aholza: peter-h: mapaaso: ankokko ping
[17:01:04] <akseli> jaheikki3: pong
[17:01:05] <sahumada> jaheikki3: pong
[17:01:19] <peter-h> jaheikki3: pong
[17:01:34] <kkoehne> jaheikki3: pong
[17:02:08] <jaheikki3> Time to start Qt release team meeting
[17:02:20] <jaheikki3> On agenda today
[17:02:30] <jaheikki3> Qt 5.3 Alpha release
[17:02:30] <jaheikki3> Qt 4.8.6 status
[17:02:43] <jaheikki3> Any additional items?
[17:04:29] <jaheikki3> OK, lets starts from Qt 5.3 Alpha release
[17:05:02] <jaheikki3> Feature freeze is now in effect. Lars gave an exception 
to GL switching, QQuickWidget and the printing.
[17:05:29] <peter-h> jaheikki3: I wonder: do I need a confirmed exception for 
my SPDY stuff?
[17:05:39] <peter-h> ... it is not yet in either, but hopefully today / 
tomorrow...
[17:05:51] <peter-h> but it was discussed on the releasing list
[17:06:55] <jaheikki3> peter-h: Yes, I think it was agreed that it is ok to 
take SPDY in as well. reason for delay were in CI if I remember correctly
[17:07:51] <jaheikki3> hoping you could get things in today so that it will be 
in coming merge tomorrow...
[17:08:10] <jaheikki3> Merge from dev to stable isn't done yet, there were some 
issues with building & couple of merge conflicts in merge from stable to dev.
[17:08:15] <peter-h> jaheikki3: ok, so can I still merge to dev?
[17:08:28] <peter-h> I mean cherry-pick
[17:09:32] <jaheikki3> peter-h: We should avoid new changes in dev to make 
merge as easy as possible but I think your changes were in dev already?
[17:10:16] <peter-h> jaheikki3: well it was staged for dev, but did not make it 
in
[17:10:42] <peter-h> fregl suggested to push to stable instead, but if the 
merge is not yet done, I wonder whether I can merge to dev instead
[17:11:18] <jaheikki3> Then you can then try to restage. If that doesn't 
succeed, let's wait until merge has happened & re-target those to stable instead
[17:11:59] <peter-h> ok
[17:12:15] <jaheikki3> we have still some work to do before merge: Build issue 
is already fixed but merge conflicts needs to be integrated. Let's hope we 
could get those integrated today
[17:13:00] <jaheikki3> Plan is to do merge tomorrow morning if conflicts are 
integrated successfully today
[17:13:33] <peter-h> ok I see
[17:15:16] <jaheikki3> It would be nice to get all changes related to those 
exceptions in before Alpha but after discussion with Lars I propose we wouldn't 
delay alpha several days because of these.
[17:16:30] <jaheikki3> Plan was to do Alpha this Thursday but if those aren't 
in early enough we could wait these until beginning of next week but no longer
[17:16:38] <jaheikki3> Any comments?
[17:19:29] <akseli> i guess silence equals approval:)
[17:19:41] <ankokko> yes :-)
[17:19:42] <jaheikki3> because no-one objects let's proceed with this plan...
[17:20:03] <jaheikki3> Then 4.8.6 status: Akseli^
[17:21:02] <akseli> just uploaded new snapshot build to 
http://download.qt-project.org/snapshots/qt/4.8/ which has mingw482 package 
included .. unfortunately it takes time to sync & become visible
[17:21:58] <akseli> that package has some problems with two dll's (one missing, 
another one corrupted during packaging) but i'll send email to ML with details
[17:22:38] <akseli> anyway it is worth to try & test since dll's can be copied 
from mingw to qt4.8.6/bin folder
[17:23:03] <akseli> and those packages have 11 changes compared to previous 
snapshot
[17:23:44] <akseli> if not including mingw installer related packaging issue it 
looks promising
[17:25:05] <akseli> but that is short status update, any questions?
[17:28:03] <akseli> i guess not... next item on agenda? jaheikki3^
[17:28:25] <jaheikki3> next meeting on next Monday at this same time?
[17:29:00] <akseli> ok for me
[17:29:10] <ankokko> +1
[17:29:49] <jaheikki3> OK, it seems we are ready at this time. Let's try to put 
Apha out as soon as possible, latest at the beginning of next week.
[17:30:03] <jaheikki3> Thanks for everyone.
[17:30:04] <jaheikki3> Bye
[17:30:12] <peter-h> bye
[17:30:14] <akseli> bye
[17:30:15] <ankokko> bye


------------------------------------------------------------------
Jani Heikkinen
Release Manager

Digia Plc
Elektroniikkatie 10, FI 90590 Oulu Finland
Email: [email protected]<mailto:[email protected]>
Mobile: +358-504-873-735
Visit us at: www.digia.com<http://www.digia.com/>
| Blog<http://blog.digia.com/> | Twitter<https://twitter.com/digiaonline> | 
LinkedIn<http://www.linkedin.com/company/5119> | 
YouTube<http://www.youtube.com/digiaonline> | 
Facebook<http://www.facebook.com/digiaonline> |
------------------------------------------------------------------
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named 
addressee and may contain privileged and/or confidential information. If you 
are not the named addressee you should not disseminate, copy or take any action 
in reliance on it. If you have received this message in error, please contact 
the sender immediately and delete the message and any attachments accompanying 
it. Digia Plc does not accept liability for any corruption, interception, 
amendment, tampering or viruses occurring to this message.
------------------------------------------------------------------

_______________________________________________
Releasing mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/releasing

Reply via email to