홈 » Bryce Harrington » Resources » PasteBin » 0.92.2 Development Meeting ~ August 4, 2017
  1. Aug 04 13:02:06 <bryce> = 0.92.2 Development Meeting =
  2. Aug 04 13:02:11 <bryce> hi all
  3. Aug 04 13:02:12 <tedg> As an aside I might miss next month's meeting. I'll be on a plane, if it has Wifi I'll be here :-)
  4. Aug 04 13:02:34 <ryangorley> tedg excuses...
  5. Aug 04 13:02:37 <bryce> who's here for the development meeting?
  6. Aug 04 13:02:44 <rindolf> bryce: i am
  7. Aug 04 13:02:44 <ryangorley> ;)
  8. Aug 04 13:02:45 <Mc> o/
  9. Aug 04 13:02:54 <tghs> o/
  10. Aug 04 13:03:11 <Tavmjong> o/ for a few minutes
  11. Aug 04 13:03:12 <bryce> thanks for coming :-)
  12. Aug 04 13:03:15 <bryce> Agenda:
  13. Aug 04 13:03:15 <bryce> * QA status / issues
  14. Aug 04 13:03:15 <bryce> * Translation team status
  15. Aug 04 13:03:15 <bryce> * Vector team status
  16. Aug 04 13:03:15 <bryce> * Web team status
  17. Aug 04 13:03:15 <bryce> * Release team status
  18. Aug 04 13:03:15 <bryce> * Final Go/No-go on release
  19. Aug 04 13:03:15 <bryce> * Other business
  20. Aug 04 13:04:24 <bryce> I had planned do some 0.92.2 homework after work yesterday but unfortunately there was power outage all day (108° heat here in Portland) so got nothing done
  21. Aug 04 13:05:07 <bryce> so will be appreciating crib notes ;-)
  22. Aug 04 13:05:15 <Tavmjong> That's Fahrenheit, I presume.
  23. Aug 04 13:05:21 <bryce> ok, first question is how are we stability-wise?
  24. Aug 04 13:05:22 <rindolf> Tavmjong: yes
  25. Aug 04 13:05:30 <bryce> Tavmjong, given that I am alive, that would be yes
  26. Aug 04 13:05:57 <bryce> I've run Inkscape and just cursorily tested things but nothing in depth
  27. Aug 04 13:06:01 <Mc> I think that's around 303K
  28. Aug 04 13:06:13 <rindolf> Mc: heh
  29. Aug 04 13:06:16 <bryce> su_v, are you here by chance?
  30. Aug 04 13:06:17 <doctormon> And I'm here
  31. Aug 04 13:06:28 * su_v is lurking
  32. Aug 04 13:06:30 <Mc> 315*
  33. Aug 04 13:06:40 <bryce> has anyone else been using 0.92.2pre0 in earnest? Any observations?
  34. Aug 04 13:07:53 <Ede_123> From everything I did recently we're looking pretty good on Windows (much better than with 0.92.1 I think)
  35. Aug 04 13:08:10 <Ede_123> Obviously we have to wait for the stress-testing but MSYS2 seems to play out
  36. Aug 04 13:08:47 <doctormon> Probably a question for the inkscape-users list.
  37. Aug 04 13:08:57 <bryce> Ede_123, thanks for all your patch work lately, and dealing with me being hard assed about stuff
  38. Aug 04 13:09:29 <Ede_123> I cross-posted the 0.92.2pre0 announcement on inkscape-users but there wasn't too much feedback
  39. Aug 04 13:10:11 <bryce> in watching the git changelog, there's few patches that got in since 0.92.1 that I'm worried about
  40. Aug 04 13:10:39 <bryce> worst case is there might be a small oversight somewhere but I don't have a feeling that any serious regressions could have slipped in
  41. Aug 04 13:10:39 <Ede_123> bryce: no worries, just try to hit me with arguments in future (I can handle those ;-) )
  42. Aug 04 13:12:00 <Ede_123> One issue we have to "fix" before the release: https://gitlab.com/inkscape/inkscape/blob/master/src/file-update.cpp#L362
  43. Aug 04 13:12:01 <tghs> for the mac build I’ve not got any feedback yet (since I only got it out late), I’ve not hit any problems in my testing (beyond all the normal complaints with the X11 mac build)
  44. Aug 04 13:12:13 <su_v> Ede_123: could you close bugs 246597, 1650407 as 'Fix committed', please? (both are linked to the same commit fixing 1670688 )
  45. Aug 04 13:12:24 <bryce> rindolf, ryangorley, Mc, tghs, Tavmjong, doctormon have you guys run 0.92.2pre0 yourselves? If not, would any of you be willing to do so this weekend and kick tires a bit?
  46. Aug 04 13:12:36 <Ede_123> I can handle updating the code, but I'd prefer if somebody could write the FAQ entry for the DPI change
  47. Aug 04 13:12:56 <rindolf> bryce: i played with it a little
  48. Aug 04 13:12:59 <bryce> Ede_123, FAQ? or Release_Notes?
  49. Aug 04 13:13:02 <doctormon> bryce: Will do.
  50. Aug 04 13:13:17 <rindolf> bryce: i use inkscape very little\
  51. Aug 04 13:13:18 <Ede_123> su_v: will check after the meeting
  52. Aug 04 13:13:23 <Ede_123> bryce: FAQ
  53. Aug 04 13:13:40 <ryangorley> bryce: Sure. I run Solus (Linux) and need to figure out how to run it without borking my repo installed version that I use for work. Or maybe try in a vm...
  54. Aug 04 13:13:44 <Ede_123> The file uopdate dialog has a link to a non-existing FAQ entry
  55. Aug 04 13:13:50 <bryce> Ede_123, you might ping Brynn or Maren, although you might need to draft most of the entry for them
  56. Aug 04 13:13:55 <Ede_123> (nobody got to writing it yet)
  57. Aug 04 13:14:10 <Mc> sorry, I'll spend next week on holidays with little presence on my computer :/
  58. Aug 04 13:14:17 <Ede_123> It's hard as it should be user-facing and I think like a programmer ;-)
  59. Aug 04 13:14:25 <tghs> bryce: yup, I did a couple of days of playing around with a build while in guadec sessions
  60. Aug 04 13:14:27 <Ede_123> But I worked on such things with Marne before
  61. Aug 04 13:14:31 <bryce> for what it's worth, last week I practiced building and running it from trunk rather than having to install it, and got that behaving well on ubuntu
  62. Aug 04 13:14:34 <Ede_123> *Maren
  63. Aug 04 13:14:53 <Ede_123> I'm not sure she's available though
  64. Aug 04 13:15:15 <brynn> Ede_123, I could help
  65. Aug 04 13:15:38 <bryce> main problem was ensuring it could find the share/ stuff, but I think the INSTALL gives adequate tips
  66. Aug 04 13:15:42 <brynn> I couldn't write much of it, but I can help to make it understandable by the non-tech crown
  67. Aug 04 13:15:47 <brynn> crowd
  68. Aug 04 13:16:06 <Ede_123> that would be great!
  69. Aug 04 13:16:19 <Ede_123> Who did the original changes for the dpi switch?
  70. Aug 04 13:16:30 <bryce> so for other platforms, as long as you have the required build dependencies, I *think* you may have a good shot at building and running branch Inkscape 0.92.x easily without needing vm or so on.
  71. Aug 04 13:17:06 <Ede_123> It might help to get some background right (I wasn't involved in that change at the time)
  72. Aug 04 13:17:31 <ryangorley> I've not actually built much from source, so I'll be doing some Googling tonight. :)
  73. Aug 04 13:17:34 <bryce> Ede_123, does git log reveal it?
  74. Aug 04 13:17:45 <Mc> Ede_123: Probably Tav
  75. Aug 04 13:17:47 <Ede_123> surely, but I guessed somnebody would know it off-hand
  76. Aug 04 13:18:02 <Mc> what do you want to know about it ?
  77. Aug 04 13:18:21 <bryce> ryangorley, oh cool -- you might be good at identifying where INSTALL could be improved to make the process more paint by numbers for people unfamiliar with building from source.
  78. Aug 04 13:19:00 <Ede_123> Nothing specific, but I guess there was some "deep decision process" going on? (No idea if this interesting to users - especially after almost a year after the change)
  79. Aug 04 13:19:27 <bryce> ok anything else on QA? We're down to the wire for the release, but are there any critical bugs or last minute patches people want me to know about?
  80. Aug 04 13:19:32 <Mc> aligning with CSS spec
  81. Aug 04 13:19:45 <ryangorley> bryce: I'm guessing I'm in the minority as a Linux user in the first place, and probably even a smaller minority who aren't developers, but I'll keep notes of how I get it to work so someone else can follow
  82. Aug 04 13:19:50 <bryce> (this meeting is probably the final cut off for any last minute changes, so if there's anything remaining tell me now)
  83. Aug 04 13:20:17 <brynn> maybe not interesting to users, but in cases where people are having problems, we don't know how to help them, because we don't understand much ourselves
  84. Aug 04 13:20:18 <Mc> since SVG is usually web-facing, browsers already consider 96dpi, and in svg2 it will officially be the ratio for svg (while it was unspecifiefd in svg 1.1)
  85. Aug 04 13:20:20 <bryce> ryangorley, thanks that'd be great, feel free to msg me suggestions and I can do the incorporating if you'd like
  86. Aug 04 13:20:41 * ryangorley Thumbs up
  87. Aug 04 13:20:42 <tghs> bryce: for the mac build, just the git revision related change that I’ve got an MR assigned to you for
  88. Aug 04 13:20:52 <Ede_123> Mc: Ah, already something I wasn't aware of!
  89. Aug 04 13:21:11 <tghs> and autotools version bump
  90. Aug 04 13:21:14 <Mc> which part ? ^^
  91. Aug 04 13:21:25 <Ede_123> that it's part of SVG2
  92. Aug 04 13:21:36 <bryce> Ede_123, yes there were a lot of dpi discussions on mailing list and irc, and yes Tav would be a good resource for that. Mailing list archives would probably elucidate some too.
  93. Aug 04 13:21:44 <Mc> (SVG should say something like "SVG shares with CSS its list of identifiers and conversion values")
  94. Aug 04 13:22:18 <Ede_123> I'll probably update the Link to a "barebones" entry so it's correct for the release, then we can work from there
  95. Aug 04 13:22:27 <Ede_123> bryce: is it fine if I push that directly?
  96. Aug 04 13:22:38 <Ede_123> (if yes when do you want to package 0.92.2?)
  97. Aug 04 13:22:42 <Mc> "SVG follows the description and definition of common values and units from the CSS Values and Units Module [css-values]" (first line of https://www.w3.org/TR/SVG2/coords.html#Units )
  98. Aug 04 13:22:43 <bryce> tghs, yep landed it this morning
  99. Aug 04 13:22:54 <Mc> Ede_123: ^
  100. Aug 04 13:22:59 <tghs> bryce: ah okay, thanks
  101. Aug 04 13:23:43 <bryce> Ede_123, sorry, pushing what? A doc change?
  102. Aug 04 13:24:06 <Ede_123> Fixing the link at https://gitlab.com/inkscape/inkscape/blob/master/src/file-update.cpp#L362
  103. Aug 04 13:24:21 <Ede_123> (the dpi change FAQ entry we were discussing about)
  104. Aug 04 13:24:35 <bryce> Ede_123, ahh right. If you push it in the next 30 min, go for it
  105. Aug 04 13:24:48 <Ede_123> I won't make that in time
  106. Aug 04 13:25:10 <Mc> Ede_123: compared with https://www.w3.org/TR/SVG/coords.html#Units where, WARNING, the important part is "based on what the SVG user agent determines is the size of a px unit", and NOT the "_For_ _example_, […]1in equals 90px"
  107. Aug 04 13:25:19 <bryce> once the meeting is done, just to keep my local tree coherent I'd like to require all changes to the tree be landed by me.
  108. Aug 04 13:26:07 <Mc> (which explains that both browsers were compliant when they decided "let's take it from css" and inkscape "let's take it at 90 like the example in the standard")
  109. Aug 04 13:26:13 <bryce> Ede_123, if not in the next 30 min, then just shoot me an MR or a patch (or even just the replacement link and I'll hotpatch)
  110. Aug 04 13:26:30 <Ede_123> bryce: fine by me. I also have some translation changes pending...
  111. Aug 04 13:26:33 <su_v> Mc: to be precise: SVG 1.1 links to an earlier version of the CSS spec, which used 90dpi
  112. Aug 04 13:26:40 <bryce> ok translation patches too
  113. Aug 04 13:27:14 <Mc> su_v: yes but they just link to it for its list of allowed units, right ?
  114. Aug 04 13:27:24 <Mc> (unit identifiers)
  115. Aug 04 13:27:29 <su_v> (nothing you can blame inkscape for - it was the current recommendation at the time)
  116. Aug 04 13:27:32 <su_v> no
  117. Aug 04 13:28:05 <bryce> the issue here being not one of review/trust but just technicalities - I want to get the packaging process rolling but run tests and builds locally before I push my commits, so anything that changes the tree in the interim requires rebasing and starting over
  118. Aug 04 13:28:36 <Ede_123> bryce: Yeah, sorry, only had "Aug 5: 0.92.x Release Tarball" remembered
  119. Aug 04 13:28:40 <Mc> ah, you're right, at the beginning of the intro
  120. Aug 04 13:28:42 <bryce> but I can slot in changes in my local tree ok
  121. Aug 04 13:29:34 <bryce> ok speaking of translations, next agenda item
  122. Aug 04 13:29:39 <bryce> == Translation team status ==
  123. Aug 04 13:29:57 <bryce> Ede_123 you mentioned some translations to land, how are things looking generally?
  124. Aug 04 13:30:22 <Ede_123> I updated the inkscape.pot file and pushed an announcement to inkscape-translators
  125. Aug 04 13:30:25 <bryce> I saw maren send a de update
  126. Aug 04 13:30:44 <Ede_123> a few translations already landed, I'm doubtful we can expect more (at least none I know of)
  127. Aug 04 13:30:57 <Ede_123> (except the few fixes I'm working on now)
  128. Aug 04 13:31:16 <Mc> are all main languages updated? (en/fr/es/pt/ja)
  129. Aug 04 13:32:01 <Ede_123> Mc: No, dee https://gitlab.com/inkscape/inkscape/commits/0.92.x/po
  130. Aug 04 13:32:04 <Ede_123> *see
  131. Aug 04 13:32:47 <Ede_123> de/fr/uk/en_GB as far I can see
  132. Aug 04 13:33:07 <Mc> hum, I forgot de in my list, sorry ^^
  133. Aug 04 13:33:09 <bryce> hopefully strings haven't changed that broadly since 0.92.1
  134. Aug 04 13:33:28 <bryce> there is a script somewhere for showing what % translations are for each language
  135. Aug 04 13:33:35 <Ede_123> bryce: The dpi file update dialog is the most visible
  136. Aug 04 13:33:42 <Ede_123> (it wasn't in 0.92.1)
  137. Aug 04 13:33:51 <bryce> might be interesting to run, but honestly too late to do much for
  138. Aug 04 13:34:19 <su_v> Mc: jftr - https://www.w3.org/TR/CSS21/changes.html#q21.147 (describes the change in the CSS spec ref'd by SVG 1.1)
  139. Aug 04 13:34:25 <bryce> po/language_statistics.sh
  140. Aug 04 13:34:51 <su_v> ( changes between CSS2 and CSS 2.1 )
  141. Aug 04 13:34:54 <Mc> I wonder if pixels will shrink again in the future^^
  142. Aug 04 13:34:56 <Ede_123> https://inkscape.org/de/doc/devel/translations-statistics-092.html (if it's up to date? doctormon?)
  143. Aug 04 13:34:57 <bryce> ja 86%
  144. Aug 04 13:35:13 <Ede_123> ah no isn't updated...
  145. Aug 04 13:35:24 <Mc> Last updated: Mon, 02 Jan 2017 14:17:45 +0000
  146. Aug 04 13:36:04 <bryce> es 94%
  147. Aug 04 13:36:22 <Mc> maybe it's worth emailing directly the last translators of main langs
  148. Aug 04 13:36:24 <bryce> rest of majors are at 99/100%
  149. Aug 04 13:37:03 <doctormon> Back
  150. Aug 04 13:37:20 <bryce> zh_CN: 96%
  151. Aug 04 13:37:31 <bryce> ok, anything else on translation?
  152. Aug 04 13:37:46 <doctormon> So that pages comes from the docs team
  153. Aug 04 13:37:49 <bryce> maybe in a future release we could do a focused effort to bring up some of the rarer languages
  154. Aug 04 13:37:55 <doctormon> It's compiled and pushed to the docs-website git repository.
  155. Aug 04 13:38:19 <Ede_123> I see... "docs team" probably does not exist anymore right now (jazzynico was the main contributor)
  156. Aug 04 13:38:41 <bryce> doctormon, looks like something that should be straightforward to automate
  157. Aug 04 13:38:51 <doctormon> Ede_123: Maybe https://gitlab.com/inkscape/inkscape-docs
  158. Aug 04 13:39:01 <bryce> and there should be a https://inkscape.org/de/doc/devel/translations-statistics-093.html created too
  159. Aug 04 13:39:14 <Ede_123> Yes, we might/should bring new people on board
  160. Aug 04 13:39:27 <bryce> or maybe -statistics-trunk.html to be more future-proofed
  161. Aug 04 13:39:36 <Ede_123> bryce: https://inkscape.org/de/doc/devel/translations-statistics-trunk.html
  162. Aug 04 13:39:47 <bryce> ah good
  163. Aug 04 13:39:59 <bryce> so just needs to gain automatic updating
  164. Aug 04 13:40:34 <bryce> that's a really nice page btw
  165. Aug 04 13:42:06 <bryce> offhand, there's probably a threshold under which a translation is going to be unusable. Wonder if we should clean up and drop translations < N% if they've not been updated within the past year or so
  166. Aug 04 13:42:18 <bryce> alright, moving on.
  167. Aug 04 13:42:28 <bryce> == Vector team status ==
  168. Aug 04 13:42:36 <Mc> https://paste.fulltxt.net/x:RTpDg ← main usage places (BIASED SAMPLE: only has win10 users having installed inkscape thourgh the store)
  169. Aug 04 13:42:36 <ryangorley> Alive
  170. Aug 04 13:42:43 <bryce> ryangorley, hi! :-)
  171. Aug 04 13:42:49 <ryangorley> Is anyone else from the team here?
  172. Aug 04 13:43:06 <brynn> brynn
  173. Aug 04 13:43:07 <Mc> might be useful to get a rough estimate of what the "main languages" are
  174. Aug 04 13:43:13 <bryce> ryangorley, thanks for the work on the announcement text, sorry I didn't give feedback... going to blame the power outage. I'll try and catch up on it post-meeting
  175. Aug 04 13:43:40 <ryangorley> bryce: Still needs some work, apparently the release notes were not very complete. I'm still waiting for that to be updated.
  176. Aug 04 13:44:05 <ryangorley> As far as the announcement is concerned I'm still trying to wrap my head around it all.
  177. Aug 04 13:44:12 <Mc> but apart from en-speaking, top is Brazil/Germany/Italy/France/Japan/India/Mexico
  178. Aug 04 13:44:15 <bryce> oh I didn't realize the release notes had gotten behind
  179. Aug 04 13:44:55 <bryce> usually everyone's been very attentive at getting their changes documented there, I hope there's not too much missing?
  180. Aug 04 13:44:55 <ryangorley> Only Eduard Braun (don't know handle) had put in his bugfixes at the point when I wrote it.
  181. Aug 04 13:45:00 <Mc> ryangorley: Ede_123
  182. Aug 04 13:45:15 <ryangorley> Oh high Ede_123
  183. Aug 04 13:45:18 <ryangorley> hi
  184. Aug 04 13:45:23 <Ede_123> hi!
  185. Aug 04 13:46:10 <ryangorley> I tried looking at the list of commits to make sense of them, but it was just too much, so I'm hoping to work from the release notes instead.
  186. Aug 04 13:46:44 <bryce> yeah
  187. Aug 04 13:46:51 <doctormon> I might be here
  188. Aug 04 13:46:51 <ryangorley> Do we have a firm release date on this? (i.e. when I'm going to need to ping all the news outlets)?
  189. Aug 04 13:47:04 <bryce> would anyone like to volunteer to help on this? I'll chip in some time myself
  190. Aug 04 13:47:09 <su_v> ryangorley: the milestone page usually helps, too (for release notes of bug-fix releases)
  191. Aug 04 13:47:11 <bryce> ryangorley, yes
  192. Aug 04 13:47:15 <su_v> https://launchpad.net/inkscape/+milestone/0.92.2
  193. Aug 04 13:47:18 <Ede_123> ryangorley: https://launchpad.net/inkscape/+milestone/0.92.2 is usually a better starting point then the list of commits (it's linked from the wiki page)
  194. Aug 04 13:47:21 <Ede_123> ah ;-)
  195. Aug 04 13:47:22 <su_v> (don't know how up-to-date it is)
  196. Aug 04 13:47:37 <bryce> > Jul 22: 0.92.x Pre-release
  197. Aug 04 13:47:37 <bryce> > + String Freeze (0.92.x branch only)
  198. Aug 04 13:47:37 <bryce> > + Packagers package pre0 release as desired
  199. Aug 04 13:47:37 <bryce> > + Translators work on translations
  200. Aug 04 13:47:37 <bryce> > + Revert changes that introduced regressions
  201. Aug 04 13:47:37 <bryce> > + Code changes must be reviewed and landed by Bryce
  202. Aug 04 13:47:37 <bryce> > (0.92.x branch only)
  203. Aug 04 13:47:37 <bryce> > Aug 4: Final Freeze
  204. Aug 04 13:47:37 <bryce> > + Final deadline for all translation work
  205. Aug 04 13:47:37 <bryce> > + Only Release Warden may commit (0.92.x branch only)
  206. Aug 04 13:47:37 <bryce> > Aug 5: 0.92.x Release Tarball
  207. Aug 04 13:47:37 <bryce> > + Packagers package final tarball
  208. Aug 04 13:47:37 <bryce> > Aug 7: Announce
  209. Aug 04 13:47:38 <ryangorley> Gotcha, thanks.
  210. Aug 04 13:48:58 <bryce> ryangorley, the 5-7 period is building in some lag time for doing announcement work. The 7th is adjustable if needed by packagers or announcers
  211. Aug 04 13:49:34 <bryce> ryangorley, in the past we've learned a lesson that delaying too long after the release is cut can be bad because news sites will scoop us, before we're ready
  212. Aug 04 13:50:07 <ryangorley> bryce: The Vectors team is still a bit unorganized, so most of it is falling to me and my schedule. I'll do my best though.
  213. Aug 04 13:50:16 <bryce> but 2 days is usually safe, esp. if I'm careful not to announce the tarball too visibly
  214. Aug 04 13:50:27 <bryce> ryangorley, count me in to help a lot too
  215. Aug 04 13:50:39 <bryce> ryangorley, I'm glad to have the help at all to be honest :-)
  216. Aug 04 13:50:41 <ryangorley> bryce: okay, thanks! I'm sure brynn is willing as well
  217. Aug 04 13:51:01 <bryce> ryangorley, we'll get the team more organized as we go, and gather experience
  218. Aug 04 13:51:08 <brynn> Sure, if it's something I can do
  219. Aug 04 13:51:23 <doctormon> ryangorley: new teams are always a mess, until they have momentum.
  220. Aug 04 13:51:23 <bryce> the more often we do releases, the more we'll get the process boiled down
  221. Aug 04 13:51:29 <ryangorley> My next next todo is to build out a launch checklist like this (http://wiki.inkscape.org/wiki/index.php/AnnouncePlanning092) in Gitlab
  222. Aug 04 13:51:41 <bryce> yes that would be great
  223. Aug 04 13:52:24 <bryce> ryangorley, make sure to drop a note on inkscape-docs@ and inkscape-translators@ once that's up
  224. Aug 04 13:52:38 <bryce> folks there can be resources to assist at taking some of those tasks once they're scoped out
  225. Aug 04 13:52:40 <ryangorley> Will do. Guessing that will be late tonight or tomorrow.
  226. Aug 04 13:52:57 <bryce> ok, anything else on translation? else moving on
  227. Aug 04 13:53:13 <ryangorley> Who do I need to ping to translate the announcement?
  228. Aug 04 13:53:23 <Mc> inkscape-translator@
  229. Aug 04 13:53:48 <bryce> ryangorley, maren if she's available has been awesome at shepherding translators, but yeah inkscape-translator@ is where they be
  230. Aug 04 13:54:17 <bryce> mainly just need to be clear about what text needs translation, and where the translation should be pasted
  231. Aug 04 13:54:42 <ryangorley> Yeah, I'll see if Maren can help me sort that out this go around.
  232. Aug 04 13:55:21 <bryce> and emphasize they can start posting stuff on language specific sites of their choice once the release is announced on the 7th, and before that to hold off
  233. Aug 04 13:55:39 <bryce> == Web team status ==
  234. Aug 04 13:56:11 <bryce> doctormon, are there any concerns about traffic surges?
  235. Aug 04 13:56:15 <Mc> "what's the web team?" :p
  236. Aug 04 13:56:47 <brynn> bunch of spiders
  237. Aug 04 13:56:53 <bryce> heh
  238. Aug 04 13:57:50 <doctormon> Web status!
  239. Aug 04 13:57:50 <bryce> yeah I ought to make use of that nifty list of teams for proper team names...
  240. Aug 04 13:57:51 <brynn> I think is referring to https://inkscape.org/en/*editor
  241. Aug 04 13:58:07 <doctormon> Usage of the inkscape has cooled, the webservr is more responsive.
  242. Aug 04 13:58:17 <Mc> :)
  243. Aug 04 13:58:40 <Mc> might be hell again when the .92.2 announce is posted ?
  244. Aug 04 13:59:04 <doctormon> Website development: We've just deployed a big move, we've moved alerts, cmsplugin_alerts, cmspugin_diff and cmsplugin_objects into their own GitHub based projects.
  245. Aug 04 13:59:09 <bryce> here I'm interested both in web infra able to handle the load, and web editors for news items and the usual release-related adjustments
  246. Aug 04 13:59:32 <doctormon> The development of cmsplugin_diff was a huge job, it was reimplimenting work already done to give django-cms a diff based view.
  247. Aug 04 13:59:43 <bryce> maren did a lot of the heavy lifting here the last few releases; if her availability is limited we might need new volunteers
  248. Aug 04 14:00:06 <doctormon> Maren has stopped contributing to the inkscape website. Except for german translations.
  249. Aug 04 14:00:24 <bryce> rats, that's a shame
  250. Aug 04 14:00:40 <doctormon> New diff app can be seen here by website staff: https://inkscape.org/en/diff/
  251. Aug 04 14:01:17 <Ede_123> doctormon: by everybody?
  252. Aug 04 14:01:26 <Ede_123> (I'm not signed in but have access)
  253. Aug 04 14:01:33 <bryce> doctormon, we had been talking about using your new release management system for the 0.92.2 release?
  254. Aug 04 14:01:56 <doctormon> Ede_123: Or everybody, I'm not that concerned.
  255. Aug 04 14:02:18 <Ede_123> Yeah, I guess that's fine... (just was not sure who "website staff" is)
  256. Aug 04 14:02:19 <doctormon> bryce: the release system is here: https://inkscape.org/en/release/
  257. Aug 04 14:02:23 <su_v> tghs: just curious - ports for the OSX packages are not latest?
  258. Aug 04 14:02:32 <su_v> package*
  259. Aug 04 14:02:39 <doctormon> With the diff work complete, I'm opening up to patching and fixing remaining issues with the releases app
  260. Aug 04 14:03:48 <doctormon> But much like the packages themselves, the app needs testing.
  261. Aug 04 14:03:52 <su_v> tghs: (question is based on a quick look only: noticed cairo listed at 1.14.8 - macports ports repo shows latest 1.14.10 ...)
  262. Aug 04 14:04:18 <Mc> is there a webpage to tell people how to help us test pre0 ?
  263. Aug 04 14:04:24 <Mc> (in mac/windows/linux)
  264. Aug 04 14:04:36 <Ede_123> Mc: None I'm aware of
  265. Aug 04 14:04:39 <tghs> su_v: yup, I did try an update on the macports tree, but I hit some package build breakages
  266. Aug 04 14:04:49 <bryce> su_v, yeah I did a 1.14.10 release in June. But there's not a huge amount changed there.
  267. Aug 04 14:05:02 <doctormon> Yes, so pre0 should have been created in the releases app, but wasn't
  268. Aug 04 14:05:09 <doctormon> So there's no place to land people ATM
  269. Aug 04 14:05:56 <tghs> su_v: didn’t have time to debug it as I was already late to get pre0 out so I just reverted to the old working macports package tree I was using before
  270. Aug 04 14:05:58 <su_v> tghs: thx (yes, the usual issues with rolling releases ... breakages occur any time, and more so on "legacy" systems)
  271. Aug 04 14:06:41 <tghs> su_v: yup, looking forward to “reproducible” dependency sets/builds going forward
  272. Aug 04 14:07:24 <su_v> tghs: if there's any specific detail to test (beyond the changes in 0.92.x itself), let me know
  273. Aug 04 14:07:59 <doctormon> bryce: OK raw page here for the 0.92.2pre0, can you play with deploying to it? https://inkscape.org/en/release/0.92.2pre0/
  274. Aug 04 14:08:51 <bryce> doctormon, what do I do?
  275. Aug 04 14:08:58 <su_v> I assume the pre0 package is as stable as the latest unofficial 0.92.1 package (no changes wrt packaging)
  276. Aug 04 14:09:03 <doctormon> I think a known issue is the inability to select the resource from the massive list of uploaded resources.
  277. Aug 04 14:09:28 <doctormon> bryce: If you're logged in, you should see the bar at the top. Release > Edit Release
  278. Aug 04 14:09:28 <tghs> su_v: yup, no changes to packaging, just the expected 0.92.x changes
  279. Aug 04 14:09:53 <tghs> packaging-wise I’ve just been focusing on master
  280. Aug 04 14:09:54 <bryce> doctormon, I am logged in but not seeing that
  281. Aug 04 14:10:42 <doctormon> bryce: Is there an box with an arrow in the top right corner of the page?
  282. Aug 04 14:10:59 <bryce> http://picpaste.com/release_tool_bryce.png
  283. Aug 04 14:11:27 <bryce> same in Opera
  284. Aug 04 14:11:41 <doctormon> bryce: It's right there in bold, top left.
  285. Aug 04 14:12:19 <bryce> ok
  286. Aug 04 14:12:28 <bryce> oh jeez, that's a lot to fill out
  287. Aug 04 14:13:40 <bryce> ok, moving on
  288. Aug 04 14:13:50 <bryce> == Release team status ==
  289. Aug 04 14:14:13 <bryce> mainly wanted to check with packagers if there are packaging issues, although there's already been a fair amount of discussion.
  290. Aug 04 14:14:41 <bryce> but just to check if there are any blockers for any packages that might necessitate delaying or postponing the release?
  291. Aug 04 14:15:19 <tghs> nothing for me
  292. Aug 04 14:15:49 <Mc> Ede_123: anything wrt windows installers ?
  293. Aug 04 14:16:48 <Ede_123> no, I guess we're fine. I didn't get around to fix creation of shortcuts 7 file associations (there are some minor issues) but that's nothing that would block a release
  294. Aug 04 14:17:06 <Ede_123> (never worked properly, so... yeah)
  295. Aug 04 14:17:31 <Ede_123> .msi still is living hell ;-)
  296. Aug 04 14:18:43 <bryce> ok
  297. Aug 04 14:18:58 <Mc> I may already have told you, but I wonder if it's possible to generate the msi installers and/or the appx) from appveyor
  298. Aug 04 14:19:34 <Ede_123> AppVeyor will automatically create .7z / .exe / .msi now (fully automated)
  299. Aug 04 14:19:53 <Ede_123> it's probably not the version I'll release though (missing dictionaries)
  300. Aug 04 14:19:56 <bryce> I've told my wife I'll be busy with release stuff this weekend so will be focusing on all the release tasks, and should be around if anyone needs me for anything.
  301. Aug 04 14:20:18 <Ede_123> appx: Depends on what AppVeyor offers
  302. Aug 04 14:20:20 <su_v> tghs: any chance you could verify this workaround: http://www.inkscapeforum.com/viewtopic.php?f=5&t=21709#p100111 ? (I don't have an external monitor myself). if it works, would it be helpful to mention on the download page for macOS?
  303. Aug 04 14:20:48 <Mc> Ede_123: nice work @automation
  304. Aug 04 14:21:18 <Ede_123> yeah, it's also great for packaging manually! simply run "ninja dist-win-all" and lean back!
  305. Aug 04 14:21:19 <Mc> I completely missed that (a week ago apprently)
  306. Aug 04 14:21:55 <Ede_123> Made the process *a lot* easier and quicker
  307. Aug 04 14:22:23 <bryce> I'll post the meeting minutes for the two meetings, extract action items (particularly mine), do a review of ryan's release announcement and the ML discussion, practice inserting pre0 into the release tool (I just tried but got an error), search the ML for any remaining MR's or patches needing landed, update the Creating Inkscape Dists wiki page (both for remaining git/cmake adjustments, and docs for the new release tool)
  308. Aug 04 14:22:38 <bryce> I'll try and spend some time helping on getting the Release Notes page up to date
  309. Aug 04 14:23:03 <bryce> then will do the release process... tag release, run distcheck, make dist, etc.
  310. Aug 04 14:23:19 <ryangorley> bryce: Ping me when you feel like that is good and I'll revise the announcement accordingly
  311. Aug 04 14:24:04 <bryce> when it's ready I'll post an email to packagers and vector team folks, and will mention it here on irc. The link will be live on the website, but I won't post to the mailing list until we're ready to announce formally
  312. Aug 04 14:24:28 <bryce> == Final Go/No-go on release ==
  313. Aug 04 14:24:55 <bryce> so, with those tasks about to kick off, if anyone has any reasons why we should postpone the release now's the time to voice them
  314. Aug 04 14:26:35 <Mc> translations ?
  315. Aug 04 14:27:42 <bryce> Mc, ok what's the concern?
  316. Aug 04 14:29:00 <Mc> concern is that some important parts to translate (eg the old-file-import dialog) should at least be translated to brazilian an japanese
  317. Aug 04 14:29:05 <Mc> italian if possible
  318. Aug 04 14:29:40 <Mc> or at least usual translators be emailed and asked
  319. Aug 04 14:29:58 <Ede_123> Mc: Do you really think we can expect anything? I didn't here anything from those translators so I assumed they were not interested.
  320. Aug 04 14:30:06 <Ede_123> *hear
  321. Aug 04 14:30:08 <bryce> Mc, would you mind dropping them an email right now? If they can get me updates within 24 hrs I'll make sure they're included
  322. Aug 04 14:30:51 <Mc> I can try
  323. Aug 04 14:31:07 <Mc> also, more testing cannot be bad
  324. Aug 04 14:31:30 <Ede_123> At least a fair chance...
  325. Aug 04 14:31:33 <bryce> sure, can't be bad although we're out of time to do anything about findings for this release
  326. Aug 04 14:31:46 <bryce> (aside from postponing)
  327. Aug 04 14:32:41 <bryce> well, testing to validate that all is good would be valuable
  328. Aug 04 14:32:49 <bryce> so yeah, more testing +1 :-)
  329. Aug 04 14:33:28 <bryce> == Other Business ==
  330. Aug 04 14:33:36 <bryce> ok, any other release or development stuff?
  331. Aug 04 14:33:40 <Mc> (ideally, having windows installers and mac binary on a webpage for people to test)
  332. Aug 04 14:33:49 <Mc> (a .deb too ?)
  333. Aug 04 14:34:03 <Ede_123> maybe we can put the pre0 up?
  334. Aug 04 14:34:14 <su_v> what's the status of flatpak / snap packages?
  335. Aug 04 14:34:15 <bryce> a .deb would be very nice, but I won't be able to commit to producing one
  336. Aug 04 14:34:18 <Ede_123> Then test the releases app and the releses at the same time?
  337. Aug 04 14:34:55 <bryce> alex fixed the PPA, so possibly that can be used. I haven't checked the builds myself and noticed there's still some scattered build errors being returned so am not 100% sure
  338. Aug 04 14:35:19 <bryce> tedg, ^ snaps?
  339. Aug 04 14:36:20 <su_v> re flatpack: https://inkscape.org/en/~matze ... ( https://github.com/matze/inkscape-flatpak )
  340. Aug 04 14:36:50 <Mc> (I'll email jazzynico asking him if he has the contact for the translator, I only have their names in nicolas' commits)
  341. Aug 04 14:36:55 <bryce> doctormon, is there any documentation for the release app? I'm finding myself a bit perplexed by a few things
  342. Aug 04 14:37:14 <ryangorley> A flatpak of the pre0 what make it a ton easier to test out in the future, btw
  343. Aug 04 14:38:35 <Ede_123> Mc: https://bugs.launchpad.net/inkscape/+bugsfield.tag=translationsearch=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED might help
  344. Aug 04 14:38:46 <bryce> doctormon, can I send feedback to you via email? I hesitate on posting bug reports since the "issues" are probably just ignorance on my part
  345. Aug 04 14:38:53 <su_v> bryce: https://launchpad.net/~inkscape.dev/+archive/ubuntu/stable-daily hasn't been updated yezt
  346. Aug 04 14:39:14 <Mc> Ede_123: I get an error
  347. Aug 04 14:39:22 <su_v> (wrt 0.92.2pre0 trunk PPAs aren't really relevant)
  348. Aug 04 14:39:26 <bryce> su_v, hrmmm ok, thought alex had updated that but I'll take a look
  349. Aug 04 14:40:46 <Ede_123> Mc: sorry, https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.tag=translation
  350. Aug 04 14:40:57 <Ede_123> (basically bugs with tag "translation")
  351. Aug 04 14:41:13 <Ede_123> many translations were submitted via bugs
  352. Aug 04 14:41:50 <Ede_123> Ha, we have an update: https://bugs.launchpad.net/inkscape/+bug/1574561
  353. Aug 04 14:42:30 <Ede_123> Ah, it was posted into a "fix released" status bug (they're hidden)
  354. Aug 04 14:47:27 <Ede_123> bryce: I can submit the italian translation update along with my changes if you want?
  355. Aug 04 14:47:34 <bryce> ok
  356. Aug 04 14:48:10 <Mc> mmh
  357. Aug 04 14:48:45 <Ede_123> old .pot file unfortunately :-(
  358. Aug 04 14:48:52 <Mc> ./update_po_files.sh was not run
  359. Aug 04 14:49:11 <Ede_123> Mc: no I didn't run it on purpose
  360. Aug 04 14:49:18 <Mc> running it generates a diff of 1089101 lines
  361. Aug 04 14:49:29 <Ede_123> Will create a huge diff and is not required for the release
  362. Aug 04 14:49:51 <Ede_123> I asked in my mail to inkscape-translators about that
  363. Aug 04 14:50:24 <Ede_123> Those who answered told me the updated .pot file was sufficient
  364. Aug 04 14:50:26 <Mc> so translators know how to update
  365. Aug 04 14:50:27 <Mc> ?
  366. Aug 04 14:50:41 <Ede_123> Those who answered... (not many :-/ )
  367. Aug 04 14:50:59 <Ede_123> I also offered the updated .po files as separate download
  368. Aug 04 14:51:25 <Mc> (why not keep po files up to date automatically ?)
  369. Aug 04 14:51:40 <bryce> ok, I've updated inkscape-stable-daily for git instead of bzr... will have to check back to make sure it builds tho; not sure if it needs more adjustments.
  370. Aug 04 14:51:42 <doctormon> bryce: Please email away
  371. Aug 04 14:51:48 <tedg> bryce: Yeah, I need to update them from the transition to git. They're still pointing to the bazaar repo.
  372. Aug 04 14:51:52 <Ede_123> Mc: Huge diffs...
  373. Aug 04 14:52:21 <tedg> bryce: It looks like someone has already set up the git mirror in LP, that'll help.
  374. Aug 04 14:52:44 <Ede_123> Mc: I'm not we even should keep the translations in the main repo, but as long as we don't want to use submodules I'm unsure if there's a better option
  375. Aug 04 14:53:10 <Mc> Ede_123: should we care about commit size ? (eg if a ci tool makes separate commits)
  376. Aug 04 14:53:36 <Ede_123> Sorry, don't understand the question
  377. Aug 04 14:54:46 <Mc> is the problem with the huge diffs "end up with with a commit containing 1% useful info and 99% pofile" or "will make the repo huge"
  378. Aug 04 14:55:24 <Ede_123> I think "will make the repo huge" (I didn't measure it for git but definitely for bzr)
  379. Aug 04 14:55:28 <bryce> ok, need to nip out for lunch, closing out the meeting but feel free to keep discussion going
  380. Aug 04 14:55:31 <bryce> = EOM =
  1. More ...
 
 

781

0.92.2 Development Meeting ~ August 4, 2017

by Bryce Harrington

-

PasteBin

Lines
380
Words
5766
Size
34.5 KB
Created
Revisions
2
타입
text/plain
Creative Commons Attribution Share-Alike 3.0 (CC-BY-SA 3.0)
Please log in to leave a comment!

Inkscape is Free and Open Source Software licensed under the GPL.