19:00:10 <jkurik> #startmeeting F24 Alpha Readiness Meeting
19:00:10 <zodbot> Meeting started Thu Mar 17 19:00:10 2016 UTC.  The chair is jkurik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:10 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:10 <zodbot> The meeting name has been set to 'f24_alpha_readiness_meeting'
19:00:19 <jkurik> #meetingname f24-alpha-readiness-meeting
19:00:19 <zodbot> The meeting name has been set to 'f24-alpha-readiness-meeting'
19:00:25 <jkurik> #topic Roll Call
19:00:28 <stickster> .hello pfrields
19:00:29 <zodbot> stickster: pfrields 'Paul W. Frields' <stickster@gmail.com>
19:00:32 <jkurik> .hello jkurik
19:00:32 <zodbot> jkurik: jkurik 'Jan Kurik' <jkurik@redhat.com>
19:00:35 * stickster waited for the bell this time ;-)
19:00:37 <pravins> .hello pravins
19:00:38 <zodbot> pravins: pravins 'Pravin Satpute' <psatpute@redhat.com>
19:00:41 <potty> .hello potty
19:00:42 <zodbot> potty: potty 'Abdel G. Martínez L.' <abdel.g.martinez.l@gmail.com>
19:00:50 <bowlofeggs> .hello rbarlow
19:00:51 <zodbot> bowlofeggs: rbarlow 'Randy Barlow' <rbarlow@redhat.com>
19:01:11 <mizmo> .hello duffy
19:01:11 <zodbot> mizmo: duffy 'Máirín Duffy' <fedora@linuxgrrl.com>
19:01:29 <nirik> .hello kevin
19:01:30 <zodbot> nirik: kevin 'Kevin Fenzi' <kevin@scrye.com>
19:02:15 <jflory7> .hello jflory7
19:02:16 <zodbot> jflory7: jflory7 'Justin W. Flory' <me@justinwflory.com>
19:02:23 <jkurik> adamw, mattdm, robyduck, dgilmore : are you with us ?
19:02:29 <adamw> .hello adamwill
19:02:30 <zodbot> adamw: adamwill 'Adam Williamson' <awilliam@redhat.com>
19:03:20 <jkurik> ok, lets move on, hopefully the rest of the people will join shortly
19:03:22 <jkurik> #topic Purpose of this meeting
19:03:35 <jkurik> #info Before each public release all of the groups participating the development of Fedora's next release meet to make sure the release is well coordinated.
19:03:37 <jkurik> #link https://fedoraproject.org/wiki/Release_Readiness_Meetings
19:03:48 <jkurik> #topic Current status
19:03:50 <jkurik> #info Fedora 24 Alpha is No-Go
19:03:51 <jkurik> #info Due to present blockers the Alpha release has been postponed
19:03:53 <jkurik> #info The next Go/No-Go meeting is planned on Wednesday, March 23rd
19:04:10 <b10n1k> .fas b10n1k
19:04:12 <zodbot> b10n1k: b10n1k 'jiannis Bonatakis' <jbonatakis@gmail.com> - jobo 'jiannis bonatakis' <california17@gmail.com>
19:04:30 <jkurik> even we are No-Go for now, lets check the readiness so we are sure there is no issue once the release is ready
19:04:45 <jkurik> #topic Design
19:04:54 <jkurik> mizmo: may I ask you please ?
19:04:59 <robyduck> .hello robyduck
19:05:01 <zodbot> robyduck: robyduck 'Robert Mayr' <robyduck@gmail.com>
19:05:11 <jkurik> anything we should be worried about ?
19:06:04 <mizmo> nope, design team is good for alpha
19:06:17 <jkurik> #info design team is good for alpha
19:06:27 <jkurik> good news, thanks
19:06:55 <jkurik> #topic Infrastructure
19:06:57 <jkurik> nirik: may I ask you please ?
19:07:08 <nirik> we should be all set.
19:07:18 <jkurik> great
19:07:24 <nirik> There is a storage upgrade planned for alpha release day, but I am asking them to move it.
19:07:30 <nirik> aside from that we should be ready
19:07:59 <jkurik> #info Infrastructure team is all set. There is a storage upgrade planned for alpha release day, but nirik is asking them to move it.
19:08:07 <jkurik> thanks
19:08:17 <jkurik> #topic Ambassadors
19:08:25 <jkurik> potty: may I ask you please for the readiness update from Ambassadors POV ?
19:09:44 <potty> we have not discussed about this topic but each region have everything set
19:09:50 <potty> So, no problems right now
19:10:34 <jkurik> #info Ambassadors have not discussed the readiness for Alpha, however each region have everything set.
19:10:43 <jkurik> thanks potty
19:10:55 <potty> :)
19:10:56 <jkurik> #topic Documentation
19:11:16 <jkurik> randomuser: may I ask you please provide us with readiness status for Documentation ?
19:12:41 <jkurik> hmmm... randomuser might be away for a while
19:12:54 <jkurik> anyone else from the Documentation team who can provide the status ?
19:13:03 <jflory7> I see in #fedora-docs he was caught up in some phone calls earlier
19:14:01 <jkurik> #action jkurik to check offline whether the Documentation team is ready for F24 Alpha release
19:14:18 <jkurik> #topic FESCo
19:14:28 <jkurik> anyone from FESCo here ?
19:14:30 <nirik> no fesco blockers.
19:14:35 <jkurik> wow :)
19:14:43 <nirik> should be good to go...
19:15:26 <jkurik> #info FESCo sees no blockers and should be good to go...
19:15:34 <jkurik> thank you nirik
19:15:40 <nirik> no problem
19:15:48 <jkurik> #topic Fedora Engineering Manager
19:16:00 <jkurik> stickster: is there anything, from your POV, why we should not be ready for the Alpha release of F24 ?
19:18:04 <jkurik> lets check with stickster later on ...
19:18:07 <jkurik> #topic Fedora Project Leader
19:18:16 <jkurik> mattdm: shall we go on with the release, or is there anything you might consider as a blocking issue ?
19:18:30 <stickster> Sorry jkurik, my notifier isn't working on IRC
19:18:42 <jkurik> #topic Fedora Engineering Manager
19:18:48 <stickster> jkurik: Thanks!
19:18:48 <jkurik> stickster: no problem
19:19:07 <stickster> I have no pending items in my area that would delay the release
19:19:43 <jkurik> #info Fedora Engineering Manager has no pending items in his area that would delay the release
19:19:48 <jkurik> stickster: thanks
19:19:57 <jkurik> #topic Fedora Project Leader
19:20:06 <jkurik> mattdm: are you with us ?
19:22:27 <jkurik> moving on for now...
19:22:27 <jkurik> #topic Marketing
19:22:28 <jkurik> jflory7: Justin, you have volunteered :) , so may I ask you for the Marketing status, please ?
19:22:38 <jflory7> Sure.
19:23:28 <jflory7> Currently no blockers from the release, but we are trying to generate talking points of all the "new things" in F24 from the Editions and Spins. Workstation + Cloud should be set, but we still need to gather info from Server and the Spins.
19:23:42 <jflory7> Anyone who might have info about F24 Server changes should see this post. https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/4RROCC2M6NAKLBRESLZ5DDA6PPEVKE63/
19:24:10 * randomuser is here now
19:24:23 <jflory7> And lastly, we should definitely have a F24 Alpha release announcement lined up for the Magazine. Not sure if anyone specific wants to take it on, otherwise the Magazine team can.
19:24:23 <jflory7> eof
19:24:32 <jkurik> #info no blockers from the releas but Marketing is trying to generate talking points of all the "new things" in F24 from the Editions and Spins.Workstation + Cloud should be set, but they still need to gather info from Server and the Spins.
19:25:09 <jkurik> #info People having info about F24 Server changes are requested to contribute
19:25:17 <jkurik> #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/4RROCC2M6NAKLBRESLZ5DDA6PPEVKE63/
19:26:05 <jkurik> jflory7: regarding the F24 Alpha release announcement - I believe mattdm is typically writing this
19:26:29 <jflory7> jkurik: Acknowledged -- will follow up with him.
19:26:45 <jflory7> #action jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine
19:26:55 <jkurik> thanks
19:27:07 <jkurik> #topic QA
19:27:14 <jkurik> adamw: may I ask you please ?
19:27:19 <adamw> hiya
19:27:42 <adamw> so we're...more or less on top of things, I think. Alpha 1.5 test coverage is nearly complete, only missing Server tests
19:27:50 <jkurik> adamw: no long emails, just a short status please :-)
19:28:20 <adamw> we've had to do a lot of work behind the scenes to keep the validation process working, but that should all be mostly done by now and stuff is...mostly working
19:28:33 <jkurik> #info QE is more or less on top of things. Alpha 1.5 test coverage is nearly complete, only missing Server tests.
19:29:23 <jkurik> #info QE is doing a lot of work behind the scenes to keep the validation process working , but that should all be mostly done by now and stuff is...mostly working
19:29:53 <jkurik> thanks adamw for the status
19:30:03 <jkurik> #topic Release Engineering
19:30:52 <jkurik> dgilmore: may I ask you please to share releng readiness status for F24 Alpha ?
19:32:12 <jkurik> do we have someone else from release engineering here ?
19:33:08 <jkurik> ok, moving on
19:33:13 <jkurik> #topic Documentation
19:33:28 * pravins waiting for my turn :)
19:33:32 <randomuser> hey, that's me
19:33:37 <jkurik> randomuser: Hi
19:34:15 <jkurik> pravins: in a while ...
19:34:24 <randomuser> Documentation is just getting started at this point in the release cycle.  I'm honestly behind schedule on some prep work and communication, but most of the active folks know what to do.
19:34:25 <pravins> sure.
19:34:45 <randomuser> We usually do not have much ready at this point in the cycle.
19:35:30 <jkurik> so, shall we consider this as an issue, or from your POV we are ready to go ?
19:35:30 <randomuser> but, plans:  I'll be sending out some 'how to relnotes' mails to devel-announce@ and docs@ and test@ asking for some help, soon
19:36:14 <randomuser> no, it is typical for Docs to not have a lot done at this point in the cycle, we like to wait until after freezes before digging in
19:36:23 <randomuser> no blocker, just reporting status
19:36:49 <jkurik> #info Documentation is just getting started. However there is no blocking issue for F24 Alpha at the moment.
19:36:57 <jkurik> randomuser: thanks
19:37:06 <jkurik> #topic Translations
19:37:21 <jkurik> pravins: so, we are here
19:37:28 <pravins> thanks jkurik
19:37:42 <pravins> From Translation side, Software String Freeze happened with Alpha freeze i.e. on 2016-03-08. We have just started doing translations. So no issues from translations side as well :)
19:38:14 <jkurik> #info Software String Freeze happened with Alpha freeze i.e. on 2016-03-08. The team have just started doing translations.
19:38:27 <pravins> Also would like to update on internationalization:- proposed 3 changes are already 100% complete.
19:38:45 <jkurik> #info The team sees no issues to go live with the Alpha
19:39:08 <jkurik> pravins: sounds good
19:39:16 <jkurik> thanks a lot
19:39:37 <jkurik> #topic Websites
19:39:43 <jkurik> robyduck: may I ask you please ?
19:39:53 <robyduck> hi
19:40:06 <robyduck> websites are all in a good shape, but we need to sync out with releng to fix paths and checksums, which apparently changed :/
19:40:25 <robyduck> but as always, we will get all the issues fixed in time and websites will show up at release time correctly updated, as always ;)
19:40:35 <robyduck> testers are welcome
19:40:55 <robyduck> and it would be nice to have more strings translated
19:40:56 <jkurik> #info websites are all in a good shape, however the team needs to sync out with releng to fix paths and checksums
19:41:00 <robyduck> nothing else from web-land
19:41:46 <jkurik> #info The Websites team welcomes testers
19:41:54 <jkurik> thanks robyduck
19:42:02 <robyduck> yw
19:42:12 <jkurik> #topic Scheduling of the Release time
19:42:27 <jkurik> During F23 release we were dealing with some mis-synchronization between availability of bits (deliverables) and marketing communication. To avoid this situation again I would agree on the timing for this release.
19:42:47 <jflory7> (CommOps is also available for a status update if required)
19:43:16 <jkurik> Even we do not have the date for the release (as the status is No-Go), we might agree on the hour, once the Alpha is ready
19:43:34 <robyduck> jkurik: so are we switching to UTC time? :)
19:43:40 <jkurik> The proposal from Release Engineering is to have everything live at 14 UTC
19:43:55 <jkurik> robyduck: well, that is the proposal
19:44:09 <jkurik> dgilmore: can you confirm please ?
19:44:30 <robyduck> 14 UTC: +1000
19:44:58 <jkurik> is this time suitable for other teams (especially Markering, Websites, FPL) ?
19:45:25 * robyduck wants to point out EU is also switching to CEST the last weekend of march
19:45:47 <robyduck> jkurik: websites wanted this since many releases, so +1
19:45:53 <jkurik> robyduck: good point
19:46:07 <jflory7> This will be early morning across the US (10AM US EST, 7AM US PST). Should be alright from a Marketing perspective.
19:46:22 <jkurik> fortunatelly, UTC has no summer/winter switch
19:47:17 <jkurik> mattdm: are you here ?
19:48:01 <jkurik> ok, so we are missing status from FPL and RelEng
19:48:10 <jkurik> I will get this status offline ...
19:48:52 <robyduck> jkurik: will you follow up with release time via ML?
19:49:01 <jkurik> #action jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng)
19:49:23 <jkurik> #action jkurik to follow up with release time via ML
19:49:37 <robyduck> release engineering should have the biggest changes, so if they are fine with it, all others can easily adapt the release workflow.
19:49:39 <jflory7> #action jflory7 For Magazine, F24 Alpha release: Unless release time changes, intend to schedule near 14:00 UTC
19:50:21 <jkurik> robyduck: yes, I have the same POV
19:50:26 <jkurik> jflory7: thanks
19:50:29 <mattdm> jkurik: here but in a meeting
19:50:36 <mattdm> I mean a different meeting with people in the room :)
19:51:00 <jkurik> mattdm: ok, are you ready for F24 alpha readiness status
19:51:18 <jkurik> mattdm: if not, I will follow up via email with you
19:51:31 <mattdm> jkurik: Not really, if I'm writing the annoucement :)
19:51:46 <mattdm> traditionally releng _sends_ the alpha and beta annoucements
19:51:51 <jkurik> #topic Fedora Project Leader
19:52:22 <jkurik> mattdm: the Alpha slips for a week, so you have more time now
19:52:36 <mattdm> jkurik: yeah, I saw :)
19:52:49 <mattdm> I'll make sure to be ready for next week
19:53:25 <jkurik> #info Fedora Project Leader will make sure to be ready for next week with the annoucement
19:54:46 <jkurik> mattdm: what about the timing of the release ? Any objections to have the release time set to 14:00 UTC ?
19:54:53 <stickster> jkurik: Sorry, I've been attending elsewhere. Is there someone from Marketing here?
19:55:08 <jflory7> stickster: o/
19:55:11 <jkurik> stickster: yes, jflory7
19:55:24 <stickster> jflory7: Do you have a link to the wiki page for the announcement? I only have There have been many changes to theming in GTK+ 3, where a stable API has not been declared. As a result, applications that use custom CSS theming, for example, may show issues with their appearance. This may include default applications that come with Fedora 24 Alpha Workstation. Users are asked to try out their favor
19:55:30 <stickster> ite GTK+ 3 based applications and report bugs upstream so they might be addressed in time for the final release.
19:55:31 <mattdm> jkurik: I didn't see that part, sorry. Is this a general change on the time of releases or juts for this one?
19:55:33 <stickster> oops
19:55:35 <stickster> darn, wrong paste
19:56:05 <stickster> sorry everyone. I only found this: https://fedoraproject.org/wiki/F24_Alpha_release_announcement
19:56:08 <stickster> jflory7: ^
19:56:19 <jkurik> mattdm: I believe RelEng wants this to be a general rule
19:56:44 <jkurik> mattdm: however we can agree on this release only and see how it will work
19:57:02 <jflory7> stickster: Acknowledged. We'll help with mattdm to get that formalized and prettied up for the announcement. CommOps is definitely greatly interested in helping with this as well. I'll put it on their radars as well.
19:57:25 <stickster> jflory7: Thanks.
19:57:32 <mattdm> I guess I don't have strong feelings, except I think morning is better for news
19:58:18 <jkurik> mattdm: ok, I will follow up on mailing list with this anyway
19:58:34 <jkurik> #topic Open floor
19:58:43 <jkurik> anything else anyone would like to discuss ?
19:59:02 <jflory7> I can give a quick update about CommOps.
19:59:17 <jkurik> #topic CommOps
19:59:29 <jkurik> jflory7: go on
19:59:39 <jflory7> decause sends his regrets, he's currently 15,000 feet in the air.
20:00:55 <jflory7> CommOps has no blockers for F24, but we have a lot on ongoing tasks to improve some areas in time for the full release of F24. The major focus right now is looking at Onboarding and building a strategy for the different sub-projects across Fedora with Badges. We're currently starting with CommOps and Infrastructure, but are working on this on a rolling basis.
20:01:35 <jflory7> Also, as a reminder, Google Summer of Code season is here, so if you are in a sub-project with a project on the wiki, expect to see some new folks coming into channels asking for help.
20:01:36 <jflory7> eof
20:02:02 <randomuser> jflory7++
20:02:02 <zodbot> randomuser: Karma for jflory7 changed to 38 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
20:02:14 <jkurik> thanks jflory7
20:02:16 <jflory7> Whooo, cookies :)
20:02:18 <jflory7> Yep, sure thing.
20:02:48 <jkurik> #info CommOps has no blockers for F24. The team has a lot on ongoing tasks to improve some areas in time for the full release of F24.The major focus right now is looking at Onboarding and building a strategy for the different sub-projects across Fedora with Badges.
20:03:16 <jkurik> #topic Open floor
20:03:22 <jkurik> anything else ?
20:03:29 <jflory7> Nothing from me.
20:04:51 <jkurik> ok, thanks all for comming and sharing the readiness ststatuses with us
20:05:10 <stickster> Thanks for running this, jkurik
20:05:16 <jkurik> #endmeeting