[Releasing] Meeting minutes: Release team meeting Dec 11, 2012

Tue Dec 11 17:23:33 CET 2012

Hi,

Here are the minutes from today's release team meeting:

1. Need for an RC2
The release team agreed that the current RC is  not good enough to become a Qt 5.0.0 final, so we will instead target a RC2.

2. (Best case) schedule for RC2 and Qt 5.0.0 final
We will try to release RC2 tomorrow (Wednesday). There are still fixes that need to go in, so we will need to evaluate the packages that are built tonight to see if they are ready to become the RC2 packages. The release team will meet again tomorrow @12 - noon - CET on IRC to decide whether the mornings packages are good enough.
If we find out that we do not have enough information by then, we will postpone the meeting until 13.00. 
Hanne will send out meeting invitation, and adjust time as needed.

_If_ RC2 is released tomorrow, Wednesday, we will target to release Qt 5.0.0 final on Tuesday December 18th.

3. Next steps
* Evaluate all incoming P1s, and consider downgrading if not crucial for 5.0.0.
* Thiago send out email to Development ML asking people to re-review their P1s.
* Meet again tomorrow midday CET to evaluate packages and bug status. Hanne send out invitation.
* No meeting at 16.00 CET tomorrow.

Cheers,
Hanne

---
Meeting log:
hanne:lars thiago steveire kkoehne_ tijensse mauricek treinio iieklund akseli joaijala sahumada ZapB rosch : ping - for release team meeting
[4:00pm]mauricek:hanne: pong
[4:01pm]lars:hanne: pong
[4:01pm]treinio:hanne: pong
[4:01pm]kkoehne_:hanne: pong
[4:01pm] thiago_ joined the chat room.
[4:02pm]ZapB:hanne: pong
[4:02pm]tijensse:hanne: pong
[4:02pm]sahumada:pong
[4:03pm]•thiago_ guesses there was a ping
[4:03pm]hanne:thiago_: yes, just was - good morning 
[4:03pm] thiago_ is now known as thiago.
[4:03pm]hanne:guess we can start
[4:03pm]hanne:I have the following agenda:
[4:03pm]hanne:1. Need for an RC2
[4:03pm]hanne:2. (Best case) schedule for RC2 and Qt 5.0.0 final
[4:03pm]hanne:3. Next steps
[4:04pm]hanne:Anything anyone wants to add to the agenda?
[4:04pm]hanne:lets start with 1. Need for an RC2
[4:05pm]hanne:There seems to be common understanding that RC1 is not good enough for release, and that we need an RC2. This is a decision that should be made by the release team, so I would first like to know: Does anyone here disagree with us releasing an RC2?
[4:05pm]kkoehne_:hanne: yes
[4:05pm]kkoehne_:hanne: Sorry, I don't disagree 
[4:05pm]hanne:kkoehne_: 
[4:05pm]ZapB:+1 for RC2
[4:05pm]lars:+1 for RC2
[4:05pm]sahumada:+1
[4:05pm]treinio:already created an rc2 version in jita 
[4:05pm]treinio:*jira
[4:06pm]hanne:kkoehne_: sorry - maybe I should ask the other way around..
[4:06pm]hanne:ok - then we will have an RC2
[4:07pm]hanne:Next item: 2. (Best case) schedule for RC2 and Qt 5.0.0 final
[4:07pm]ZapB:RC2 tomorrow? Final +1 week?
[4:07pm]ZapB:if rc2 good enough of course
[4:08pm]hanne:there are still some fixes that we would like to see in
[4:08pm]hanne:hopefully we get them in today
[4:08pm]hanne:This would mean that we have package candidates for tomorrow morning.
[4:08pm]thiago:how is our showstopper list?
[4:08pm]hanne:treinio: ^
[4:08pm]treinio:thiago: https://bugreports.qt-project.org/secure/IssueNavigator.jspa?requestId=13651
[4:09pm]hanne:If the release team permits, we could do as last time: have a release team meeting around noon CET to agree whether the packages can be used for the RC2 or not.
[4:09pm]hanne:then we would still have a chance of releasing the RC2 tomorrow
[4:09pm]mauricek:is noon ok from a timing perspective?
[4:10pm]sahumada:treinio: you are missing "affects version = 5.0.0 rc2" I think
[4:10pm]hanne:mauricek: not sure, we might need more time
[4:10pm]treinio:sahumada: yes, haven't modified the bugs thenselves yet
[4:11pm]sahumada:treinio: I modified one that is not in the list 
[4:11pm]hanne:thiago: are you the only one on PST now?
[4:11pm]thiago:yes
[4:12pm]hanne:thiago:  would it be ok for you that we make the decision during your night?
[4:12pm]thiago:go ahead with a quicker meeting tomorrow noon to check the package sanity
[4:12pm]hanne:thiago: ok - thanks
[4:12pm]hanne:when is a good time?
[4:12pm]hanne:is 12-noon to early?
[4:12pm]thiago:if topi's list drop to zero entries, it's a clear RC
[4:12pm]thiago:if it's still non-empty, you guys make a subjective decision
[4:13pm]thiago:(by downgrading the remaining issues from P1 to P2)
[4:13pm]hanne:thiago: sounds resonable
[4:13pm]treinio:thiage: yes
[4:13pm]treinio:thiago, i meant
[4:14pm]hanne:let's hope we have done enough testing and verification by 12 - noon. If not, we delay until 1pm
[4:14pm]hanne:any objections?
[4:15pm]hanne:then to the timeline for the final:
[4:15pm]hanne:we see that we are running short on time to get the final out before Christmas, but it is still possible to do.
[4:15pm]hanne:there is a concern from support that if the release happens too close to Christmas, there will be a very high load of incoming support request when everyone really wants to be on vacation. 
[4:15pm]hanne:It would therefore be good to have the final release out sooner rather than later.
[4:16pm]hanne:so question is therfor: _If_ we manage to release the RC2 tomorrow, would it be acceptable to release the final on Tuesday next week?
[4:16pm]ZapB:on the plus side it would be great to releae before Xmas so peopel can play with it over the holidays
[4:16pm]hanne:ZapB: true
[4:16pm]ZapB:i'm sure people will understand if support is a little slow over the festive period
[4:16pm]kkoehne_:hanne: Sorry, so support rather wants to have it after Christmas/
[4:17pm]kkoehne_:hanne: ?
[4:17pm]hanne:kkoehne_:  no everyone wants to have it out before chrstmas
[4:17pm]hanne:just not too close to christmas
[4:17pm]hanne:so tuesday would be good
[4:17pm]hanne:wednesday a bit late
[4:18pm]hanne:..and thursday really not good, but maybe ok
[4:18pm]hanne:s/ok/doable
[4:19pm]hanne:we have agreed previously that we would need a week between the last RC and the final
[4:19pm]kkoehne_:hanne: Okay.
[4:19pm]hanne:but if we release RC2 tomorrow, and final on tuesday next week, that is one day short of a full week
[4:20pm]hanne:question is: would that be ok?
[4:20pm]ZapB:if the RC is good that woudl seem reasonable ot me
[4:21pm]hanne:anyone else want to comment?
[4:21pm]hanne:thiago: ^ ?
[4:22pm]rosch:hanne: good to me 
[4:22pm]•tijensse don't understands the hurry, but yes just try that, feeling for me would much better if we have a rc3 this year and just a release at the beginning of january, yes only a opinion of a small developer
[4:24pm]hanne:tijensse: i understand the concern, but at the same time it would be really nice to move on - and just fix for 5.0.1
[4:24pm]hanne:and get 5.0.1 soonish
[4:25pm] thiago left the chat room. (*.net *.split)
[4:25pm] hunger_ left the chat room. (*.net *.split)
[4:25pm] nezticle left the chat room. (*.net *.split)
[4:25pm] lars left the chat room. (*.net *.split)
[4:25pm]hanne:what - did they leave? 
[4:25pm]hanne:
[4:26pm] thiago joined the chat room.
[4:26pm] nezticle joined the chat room.
[4:26pm] lars joined the chat room.
[4:26pm] hunger_ joined the chat room.
[4:26pm]hanne:yay - back!
[4:26pm]hanne:ok - if no other responses, i assume this is ok for now, and move on to next agenda item:
[4:26pm]hanne:3. Next steps
[4:27pm] thiago left the chat room. (Changing host)
[4:27pm] thiago joined the chat room.
[4:27pm]thiago:sorry
[4:27pm]thiago:I've been trying to talk for 10 minutes
[4:27pm]thiago:freenode didn't help
[4:27pm]hanne:thiago: hehe
[4:27pm]hanne:thiago: go ahead
[4:27pm]thiago:07:16 < thiago> treinio: there's another P0 for you:  https://bugreports.qt-project.org/browse/QTBUG-27722
[4:27pm]thiago:07:16 < thiago> just get ossi to close it
[4:27pm]thiago:07:17 < thiago> btw, shall we send an email to the ML asking people to re-review all their P1s?
[4:27pm]thiago:07:18 < thiago> there are about 50 still valid
[4:28pm]hanne:thiago:  good idea
[4:28pm]ossi|tt:thiago: there are still a few pending patches, but i'm done with it
[4:28pm]thiago:ossi|tt: can you close it by the end of the day?
[4:28pm]ossi|tt:thiago: unrealistic
[4:28pm]thiago:by tomorrow noon?
[4:29pm]ossi|tt:thiago: if CI is in a good mood, yes
[4:29pm]thiago:ok, so I guess this is one of the verifications for tomorrow
[4:29pm]hanne:yes - noted
[4:30pm]sahumada:it wont be in tomorrow's packages if it gets merged after 18:00 today (CET)
[4:30pm]sahumada:*tomorrow's morning .. that is
[4:30pm] thiago left the chat room. (*.net *.split)
[4:30pm] hunger_ left the chat room. (*.net *.split)
[4:30pm] nezticle left the chat room. (*.net *.split)
[4:30pm] lars left the chat room. (*.net *.split)
[4:32pm] hunger_ joined the chat room.
[4:32pm] lars joined the chat room.
[4:32pm] nezticle joined the chat room.
[4:32pm] thiago joined the chat room.
[4:32pm]hanne:i think we also need to send out an email with the schedule
[4:32pm]hanne:i will send out minutes from this meeting
[4:33pm]thiago:as for the P1 task list, I'll take the task of reviewing all tasks that aren't assigned to anyone
[4:33pm]thiago:or assigned to closed Nokia identities
[4:33pm]hanne:thiago: great - thanks
[4:33pm]treinio:thiago: bare in mind that there's a lot of P1 for modules that aren't part of release
[4:33pm]hanne:who writes the email about reviewing own P1s?
[4:33pm]thiago:treinio: yes, I know
[4:34pm]thiago:treinio: I'll skip those
[4:34pm]thiago:hanne: I can do it
[4:34pm]treinio:thiago: ok, thanks
[4:34pm]hanne:thiago: thanks
[4:34pm]thiago:but it's unrealistic to expect any resolution by 18:00 CET today
[4:34pm]thiago:that's 90 minutes from now
[4:35pm]hanne:thiago: true.. we should probably plan to build new packages straight after tonights build is done
[4:35pm]thiago:finally, someone please check with the doc team on their readiness. There's a bunch of P1s relating to docs.
[4:35pm]hanne:iieklund: ok ^^  to build again tomorrow morning?
[4:36pm]treinio:thiago: i can check the remaining doc issues separately
[4:36pm]hanne:thiago: i think the docs are in pretty good shape, but still more can be done
[4:36pm]hanne:any other next steps we need to discuss now?
[4:36pm]treinio:thiago: we do have usable docs right now
[4:37pm]hanne:are we done?
[4:37pm]thiago:just asking because there are P1s
[4:37pm]hanne:thiago treinio : we might want to reevaluate the priorities
[4:38pm]kkoehne_:hanne: Who does that?
[4:38pm]hanne:or perhaps we are ok to still fix some doc tasks between the RC2 and the final?
[4:38pm]kkoehne_:hanne: We'd need decisions by tomorrow 12:00, and I guess some of them are controversal.
[4:38pm]treinio:hanne: yes, agreed
[4:38pm]treinio:hanne: about reprioritize
[4:39pm]hanne:kkoehne_: good point - we can go through the controversal ones in the meeting tomorrow?
[4:40pm]kkoehne_:hanne: I'm not sure we have all the expertise then, but we can try.
[4:40pm]kkoehne_:hanne: Just an example, one would have to convince me to drop https://codereview.qt-project.org/#change,42363 to P2 , since it just failed integration.
[4:41pm]kkoehne_:hanne: But that one I think we can handle tomorrow.
[4:42pm]andre_:maybe someone can come up with a list of changes that in theory should be integratable but currently don't 
[4:42pm]hanne:kkoehne_: understand - we still want a good quality release - we will see what we issues we have tomorrow
[4:42pm]andre_:I guess "we" could babysit a few of them through CI during the night
[4:43pm]hanne:sahumada: do you have an overview of what these would be?
[4:44pm]hanne:andre_: or how do we "come up with that list"?
[4:44pm]sahumada:so far .. this is what we are going to get in tomorrow's packages https://codereview.qt-project.org/42422
[4:45pm] hunger_ is now known as hunger.
[4:46pm]hanne:sahumada: but which ones are _not_ integrated - that should be? do we have any ideas for that?
[4:47pm]hanne:or it is each persons responsibility
[4:47pm]sahumada:hanne: no idea .. the only ones I am aware of are https://codereview.qt-project.org/42423 and https://codereview.qt-project.org/42434
[4:47pm]sahumada:otherwise we wont have packages tomorrow
[4:48pm]hanne:ok - we just have to follow the changes a bit
[4:49pm]hanne:i think we are done with the meeting
[4:49pm]hanne:thanks for joining!
[4:50pm]hanne:see you again tomorrow