Release Meeting: 09 March 2015

Details

1. Status update on Translations

JanKrueger has a server up and running. Integrated with github, push and pull operations.
  • 13294 (Closed): Translation quality issues with maketext source strings.
    Report strings issues that need developer assistance. For example, string snippets that need further context, missing or mis-located punctuation. If a translator finds an issue that should be fixed in the source, please add them to this task along with the weblate "Source String Location" information.
  • Translation underway for Italian, French, German. Czech, Traditional Chinese, Portuguese BR, Turkish and Danish See TranslationTeam for list of active translators.
  • We need to find translators for a number of languages. We have not heard from several of the translators, and a few have responded as unable to participate.
  • In addition to Item13294, the "Source string comment" feature has been enabled on Weblate. Comments on source strings are sent to the foswiki-svn developers list. This should help improve the quality of the translations.

2. Release blockers

6 "Blockers", (3 new)

  • Configure tasks:

  • New and escalated
    • 13285 (Closed): Resolve disconnect in extension forms can this be closed? Yes - closed

  • Being worked on
    • 8966 (Confirmed): Wysiwyg editor breaks standard topics Topics being reviewed for issues

  • Closed / Resolved / Defered blockers (as of this meeting)
    • 13220 (Closed): undefok NUMBERs generate a Number format error on an undef value Resolved but needs review.
    • 13291 (Closed): Wysiwyg swaps oder of query parameters and #anchor fixed, but pending feedback on a patch to "fixup" incorrect links
    • 13270 (Closed): No link to the wiki being configured

  • Not really blockers
    • 12855 (Closed): Audit core DEPENDENCIES - Admistrivia / Documentation update for when we are ready to build release packages.
    • 11262 (Closed): Update Installation Guide - We can solicit review from users testing the beta packages.
    • 13139 (Closed): Backwards compatibility issues with Foswiki 1.2 default extensions - Part of dependency review / testing effort. Need to test all 1.2 extensions against 1.1 (and 1.0.x?)
    • 12888 (Closed): Unit tests are failing - Catch-all. Currently no tests failing.

3. Proposed Schedule for Alpha / Beta / GA

Translators are asking for target dates. Is a 2-week cycle acceptable?. Releases 2-days ahead of our release meetings? Move from Beta to Release gate is: 1) Some feedback indicating that testing has happened and 2) No new tasks opened.

  • Alpha (underway) Florian reported only a few downloads of the alpha packages
  • Beta 1: 21 March
  • Beta 2: 4 April (Translations should be very close)
  • Release Candidate 4/18 (Translation complete) If no checkins in 24 hours, RC becomes release?

There was some discussion of the beta schedule and impact on translations. We generally agreed with the above tentative schedule. Beta will be built a couple of days prior to the regularly scheduled release meeting, but will delay if new blockers opened. This schedule will be communicated with the translators. Beta 1 will go without any pressure on translations. We'd like to have the languages that are 100% on Foswiki 1.1 in good condition before Beta 2.

4. Test Coverage

Should we track coverage of key features as part of an Alpha / Beta quality check? For example: See BetaTestCoverage

Please contribute test areas to the topic.

Next actions

Next meeting - - Monday March 23, 2015 1300Z

IRC Log

(09:00:56 AM) gac410: Good morning / good day everyone. http://foswiki.org/Development/ReleaseMeeting01x02_20150309
(09:01:22 AM) ***gac410 is still not awake due to daylight-savings-time-lag
(09:08:04 AM) MichaelDaum: Hi there
(09:08:19 AM) jast  entered the room.
(09:08:35 AM) JulianLevens  entered the room.
(09:08:38 AM) andreli  entered the room.
(09:09:06 AM) gac410: hi everyone.
(09:09:12 AM) JulianLevens: Hi
(09:09:13 AM) jast: hi - FWIW Iʼll probably be busy with other things but will be trying to follow along
(09:10:14 AM) gac410: Okay thanks jast. First on agenda was status update on translations. It's looking very good.
(09:11:09 AM) gac410: Italian, French, German and Danish are getting there. We really need to find some of the missing translators, or get some new voluneteers
(09:11:53 AM) RaulFR: hi all
(09:12:03 AM) gac410: Hi Raul
(09:12:49 AM) gac410: I just got an email from Justin Kim, So someone for Korean now too.
(09:13:42 AM) gac410: Oh and Czech is being translated too.
(09:14:23 AM) gac410: Team status is http://foswiki.org/Community/TranslationTeam So if anyone has personal contacts with the missing translators and can find out if they are willing to translate, please check in with them!
(09:15:29 AM) jast: hey, I got promoted to team member while I wasnʼt paying attention. yay! :)
(09:15:50 AM) RaulFR: haha
(09:15:51 AM) gac410: Anything else on translations. Other than translators, it seems we are in good shape.
(09:16:19 AM) gac410: jast, Sorry. I was just adding names of people actually doing the work. You have been busy and deserve to be listed.
(09:16:41 AM) jast: Iʼm fine with it either way, donʼt worry
(09:17:08 AM) jast: if anyone wants to provide feedback on weblate, feel free to talk to me. Iʼm not really involved in its development, though, so I may not be able to adress everything.
(09:17:18 AM) gac410: Anybody with any other translation concerns..
(09:17:46 AM) jast: oh, and I highly recommend setting up translation glossaries for each language. weblate has a feature for that.
(09:17:51 AM) jast: thatʼs all from me, I think.
(09:18:31 AM) RaulFR: ther are a lot of languages with nobody for doing the translation work
(09:18:36 AM) RaulFR: tehre*
(09:18:36 AM) gac410: We opened Item13294 to document source string issues. May not fix them all in 1.2, but get them on the list. Easy to report now too. Just log a "Source String Comment" in weblate and it will send an email to the developers.
(09:18:54 AM) RaulFR: the former translators that have working e-mail addresses we know of could be asked if they are avaibale or not, and if not, if they can look for someone to replace them, or know someone who would be interested to dedicate some time to it
(09:19:04 AM) gac410: I already did that.
(09:19:41 AM) gac410: Harvested their emails from the foswiki.org passwd file and sent them private email
(09:19:42 AM) RaulFR: there are certainly also big users of Foswiki in theses countries, who are not warae of this, and have an interest of ensuring that 1.2 has a proper translation ofr them
(09:19:49 AM) RaulFR: aware*
(09:20:43 AM) gac410: If anyone has personal contacts / working history with any of the translators, Facebook, LinkedIn, etc. Please reach out.
(09:22:05 AM) gac410: We've gotten 3 refusals that I moved to the "former translators" section. AndreUrlich, ArthurClemens and TorbenGB
(09:23:17 AM) gac410: And 3 emails are bouncing. That leaves us with no translator for Russian
(09:23:58 AM) RaulFR: what I mean is that person who accepted this task in the past, may be aware of persons using Foswiki profesionnaly and having the same language knowledge, whoʼs contact we could have through them (though they stated a refusal to perform the translation themselves)
(09:24:37 AM) RaulFR: I am using Item13294 and also the reporting facility within Weblate (both)
(09:25:10 AM) RaulFR: I duplicate the report
(09:26:01 AM) gac410: RaulFR: Okay thanks. I was planning on doing something like that so the emails don't get lost. So that helps.
(09:27:09 AM) gac410: RaulFR: I'll have to go back and read the email I sent. I'm pretty sure I did ask them to refer coworkers to help if they could not.
(09:28:42 AM) RaulFR: will this be a release blocker? (if we donʼt have enough languages translated)
(09:28:55 AM) JulianLevens: FWIW Iʼve just push my tools/git_excludes.pl et al for Item13135, Therefore you **MUST** run the script to clean up git ignore handling
(09:29:21 AM) gac410: JulianLevens: You merged to master?
(09:29:27 AM) JulianLevens: y
(09:30:10 AM) gac410: RaulFR: I don't think we should block, especially if the language was low on 1.1.x as well.
(09:30:43 AM) gac410: If it was ~100 on 1.1, and 50% on 1.2, then we have to think about it.
(09:30:57 AM) RaulFR: gac410, ok, I understand
(09:31:03 AM) gac410: Some of the languages were pretty thin on 1.1 already.
(09:31:50 AM) gac410: Okay ... Next on agenda. Release Blockers
(09:32:13 AM) gac410: I think two new ones just got opened. :(
(09:32:51 AM) gac410: Item13301, we are not encoding the single-quote entity in url query parameters.
(09:33:45 AM) gac410: Seems to be an issue on 1.1.9 as well, but the issue is subtle. Only fails if language selector is displayed (i18n enabled) And copyright pops to the heading of the page.
(09:34:10 AM) gac410: Much worse on 1.2.0 because we now use single quotes in html.
(09:35:36 AM) gac410: Item13300 also new. EDITTABLE has issues.
(09:36:07 AM) gac410: And Item13295 also new. I've fixed part. But I believe there are deeper issues.
(09:37:39 AM) gac410: We need CDot for 13300 and maybe for 13295 He seems to have been away for a few days.
(09:38:58 AM) gac410: Any other comments on blockers ... or new concerns?
(09:41:11 AM) gac410: No... ??? everyone still lagged from daylight savings time?
(09:41:50 AM) gac410: Okay .. Release Schedule. I've been asked for schedule by translators who want a target completion date.
(09:42:45 AM) RaulFR: gac410, I donʼt have anthing to add. About Item13300 I did not classify it as Urgent, but I agree with you that it does not looks good, and consistency should be there wit hthe tableʼs behaviour, so "Urgent" is ok with me
(09:43:09 AM) JulianLevens: No comments (I donʼt know enough about the blockers), No new concerns
(09:44:06 AM) gac410: I bumped it. The behavior is confusing and different enought from 1.1, that it needs visibilty. With the size of the Normals, the only way to get tasks looked at is to make them urgent :P
(09:44:54 AM) gac410: I'd consider alpha testing underway. I just asked florian if he had any download stats.
(09:45:43 AM) gac410: What I proposed is that we build Beta 1 in 2 weeks. and try to get on a 2-week beta cycle, depending upon task volume.
(09:46:34 AM) RaulFR: people should be encouraged to daily use htt://trunk.foswiki.org too, including translators
(09:46:37 AM) gac410: Assuming a Beta 2, that would put us to Release Candidate, around April 18th. So that's a good date for the translators.
(09:47:19 AM) JulianLevens: Sounds good
(09:47:29 AM) jast: agreed
(09:47:39 AM) gac410: fsfs reports 3 downloads. so not a stellar response.
(09:48:44 AM) andreli: Beta in 2 weeks. So we would have the beta for the Foswiki Camp, no
(09:49:44 AM) RaulFR: I canʼt comment on these dates, but the French translation should be 100% by this date without any problem
(09:50:34 AM) gac410: I was figuring to try to build a beta on Friday's before a release meeting. So has a couple of days of availability prior to our meetings. So beta 1 would be built on 3/20
(09:51:04 AM) gac410: How does that work for the camp?
(09:51:24 AM) gac410: 20 March (sorry using american date formatting )
(09:53:48 AM) gac410: I'm also proposing we create a "Test coverage" topic of some sort. Due to the complexity of 1.2, I think we need to identify specific areas that need closer scrutiny
(09:54:57 AM) gac410: MichaelDaum: You've been quiet ... are you hiding :)
(09:55:03 AM) MichaelDaum: yes
(09:55:59 AM) MichaelDaum: I have not much to say atm. thats all :)
(09:57:04 AM) gac410: okay. Did you and JulianLevens remember to hook up on camp notifications. I mentioned it in the release update, but it probably needs a more focused invite.
(09:57:15 AM) JulianLevens: 20 March is the date of the GA, 25 March first day of the camp, so we should be ready to test it
(09:57:31 AM) JulianLevens: Ooh yes, that really needs to be done
(09:57:45 AM) JulianLevens: jast, do you know if youʼre coming yet?
(09:58:42 AM) MichaelDaum: JulianLevens, can you take over the action item to create an announcement on the ml?
(09:59:15 AM) JulianLevens: y, stupid question is how do I do that and or do I have/need relevant access
(09:59:50 AM) gac410: Just send email to foswiki-announce@lists.sourceforge.net It will get moderated, and I can release it.
(10:00:03 AM) JulianLevens: Ok, will do
(10:00:04 AM) gac410: I think MichaelDaum is also a moderator? Yes?
(10:00:07 AM) MichaelDaum: thanks
(10:00:13 AM) MichaelDaum: not that I know
(10:00:42 AM) gac410: The maybe pass a draft by MichaelDaum JulianLevens
(10:00:59 AM) JulianLevens: Ok
(10:01:36 AM) gac410: Any new business for the release meeting?
(10:03:44 AM) gac410: Okay I'm going to create a topic Development/BetaTestCoverage ... and start a table of areas where we think we need special coverage of the testing. It would be helpful if everyone could "pile on" areas that need special consideration
(10:04:13 AM) jast: JulianLevens: will discuss this today in our dev meeting
(10:04:58 AM) JulianLevens: thanks
(10:05:42 AM) gac410: http://foswiki.org/Development/BetaTestCoverage please contribute
(10:06:12 AM) gac410: Okay. unless anything else, I think we can wrap up.
(10:06:31 AM) gac410: I hope CDot is just on a few day break. We need him for some of the new blockers
(10:06:41 AM) RaulFR: thanks gac410
(10:06:53 AM) gac410: Thanks everyone.
(10:07:05 AM) JulianLevens: Thanks to you too
(10:15:26 AM) JulianLevens left the room (quit: Remote host closed the connection).
(10:15:48 AM) JulianLevens  entered the room.
(10:18:00 AM) CDot entered the room.
(10:18:46 AM) CDot: just got internet back.... am I too late?
(10:20:01 AM) gac410: well we wrapped up... but I have time if you want to go over stuff.
(10:20:19 AM) andreli left the room (quit: Ping timeout: 246 seconds).
(10:20:24 AM) gac410: A couple of new blockers
(10:20:28 AM) CDot: not overmuch... was there anything specific you needed me for?
(10:20:42 AM) CDot: I saw you had raised one against ERP
(10:20:56 AM) gac410: EDITTABLE and a entity encoding issue .. that i'd like to discuss in another channel :)
(10:21:48 AM) gac410: it looks like we are not encoding single quotes. Item13301
(11:57:30 AM) JulianLevens left the room (quit: Quit: JulianLevens).
 

Topic revision: r3 - 14 Mar 2015, GeorgeClark
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy