1. Feb 02 12:15:59 <bryce> == Release Meeting ==
  2. Feb 02 12:16:23 <bryce> thanks board, and welcome release folks :-)
  3. Feb 02 12:16:57 <bryce> the purpose of this meeting is to kick off the 0.92.3 release
  4. Feb 02 12:17:17 <bryce> in theory this should be a pretty straightforward bog-standard point release,
  5. Feb 02 12:17:31 <Lazur> ---which is due when?
  6. Feb 02 12:17:53 <Lazur> ---would it worth a wide advertising?
  7. Feb 02 12:17:58 <doctormon> Tavmjong: What kind of travel info would you like?
  8. Feb 02 12:18:07 <bryce> so I'm not expecting to need to discuss a lot in depth, but there are some questions/plans to sort out
  9. Feb 02 12:18:13 <bryce> Agenda:
  10. Feb 02 12:18:13 <bryce> + Status of the 0.92 tree
  11. Feb 02 12:18:13 <bryce> - Any pending patches we should track?
  12. Feb 02 12:18:13 <bryce> - Are there more fixes worth cherrypicking from trunk?
  13. Feb 02 12:18:13 <bryce> - Are the release notes up to date?
  14. Feb 02 12:18:13 <bryce> + Status of platform packaging
  15. Feb 02 12:18:13 <bryce> - Any new issues compared with 0.92.2?
  16. Feb 02 12:18:13 <bryce> - Are all 0.92.2 packagers available for this go around?
  17. Feb 02 12:18:13 <bryce> + Release cycle plans
  18. Feb 02 12:18:13 <bryce> - One pre-release?
  19. Feb 02 12:18:13 <bryce> - Rough dates
  20. Feb 02 12:18:13 <bryce> + Conditions that might cause release delay
  21. Feb 02 12:18:13 <bryce> + Looking forward --- 0.93
  22. Feb 02 12:18:13 <bryce> - Dependency versions needing revved?
  23. Feb 02 12:18:13 <bryce> - Remaining licensing issues?
  24. Feb 02 12:18:13 <bryce> - GTK+ 3 stabilization / Windows performance bug
  25. Feb 02 12:18:13 <bryce> - Other stabilization work needed?
  26. Feb 02 12:18:13 <bryce> + Next meeting?
  27. Feb 02 12:18:13 <bryce> - March 2nd following board meeting?
  28. Feb 02 12:18:13 <bryce> + Other business
  29. Feb 02 12:18:35 <bryce> Lazur, good questions.
  30. Feb 02 12:20:35 <bryce> I'd like to get a better feeling of what tasks need done before fixing a date.
  31. Feb 02 12:21:27 <bryce> so what I'm wondering is, could we get it done in a month? sooner? longer?
  32. Feb 02 12:22:10 <bryce>
  33. Feb 02 12:22:20 <bryce> === Status of the 0.92.x Tree ===
  34. Feb 02 12:22:35 <Moini> If Ede_123 is okay with it, the gcodetools patch from the forums would be good to have.
  35. Feb 02 12:22:44 <bryce> has anyone been running the 0.92 tree? Opinions on it?
  36. Feb 02 12:23:02 <bryce> Moini, link?
  37. Feb 02 12:23:06 <Ede_123> yeah, as I wrote in the MR it's fine to have it
  38. Feb 02 12:23:11 <Moini> For work, it's what I always use.
  39. Feb 02 12:23:18 <Ede_123> the other comments were meant as a long-term goal if possible
  40. Feb 02 12:24:01 <Ede_123> I'm also using 0.92.x productively
  41. Feb 02 12:24:45 <Moini> https://gitlab.com/Moini/inkscape/commit/615927f4d64b63b5efccbb4ab0f73bccbbe4d2dc (merge request was for master, so won't work)
  42. Feb 02 12:24:51 <Ede_123> (it's actually what drove some of my latest work on patches)
  43. Feb 02 12:24:54 <bryce> I did a quick browse through the change history and it looks like there's quite a bit of good stuff in it.
  44. Feb 02 12:25:51 <bryce> https://gitlab.com/inkscape/inkscape/commits/0.92.x
  45. Feb 02 12:25:58 <Moini> Yes, I love the fixes :)
  46. Feb 02 12:26:21 <Moini> (and Windows users love them, too - I'm now pointing many to appveyor)
  47. Feb 02 12:26:32 <bryce> do either of you happen to know offhand if the Release Notes have been kept up to date with the changes?
  48. Feb 02 12:26:47 <Moini> Mostly, I think. Not complete.
  49. Feb 02 12:26:50 <bryce> I am planning on doing a scrub through the git changelog to check, but would be useful to know how far off we are if at all
  50. Feb 02 12:27:03 <Ede_123> I documented my changes, but nothing beyond - not sure what else needs documenting
  51. Feb 02 12:28:10 <Moini> I documented a couple things I found noteworthy, but not regularly.
  52. Feb 02 12:28:12 <bryce> Ede_123, thanks for doing that.
  53. Feb 02 12:28:14 <bryce> http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.3
  54. Feb 02 12:28:23 <Tavmjong> I've got a few changes that I probably haven't documented... I'll try to do that in the next week.
  55. Feb 02 12:28:44 <bryce> Tavmjong, thanks
  56. Feb 02 12:29:37 <bryce> the wording in the Important bugfixes looks good to me - basically describe the problem being fixed in terms an end user would find descriptive of errors they might have run into.
  57. Feb 02 12:31:07 <bryce> I'm not going to be making a push for translation updates this release. I'm guessing that not a huge amount has changed stringwise since last release to justify bugging translators. However if translations get updated that's dandy
  58. Feb 02 12:31:37 <Ede_123> I sent a mail to inkscape-translators already
  59. Feb 02 12:31:38 <Moini> Lol, just looked, remembered it wrongly. All done by Eduard :)
  60. Feb 02 12:31:47 <bryce> does that sound ok, or am I overlooking anything important?
  61. Feb 02 12:31:57 <Ede_123> (was updating the .pot this week)
  62. Feb 02 12:31:57 <bryce> ah, great then :-)
  63. Feb 02 12:32:33 <bryce> I suppose a question is whether a string freeze is needed. I was hoping to not bother this round, but can do so if anyone thinks it'd be warrented
  64. Feb 02 12:32:57 <bryce> I'm guessing the amount of change between now and release is probably going to be low anyway
  65. Feb 02 12:33:01 <Ede_123> depends if we plan to still backport something?
  66. Feb 02 12:33:16 <Ede_123> list in Launchpad is short: https://bugs.launchpad.net/inkscape/+bugs?field.tag=backport-proposed
  67. Feb 02 12:33:46 <bryce> thanks for that list, I'll plan on looking through it
  68. Feb 02 12:33:50 <Ede_123> I know su_v kept a list of commits worth backporting before - do you have one this time, too?
  69. Feb 02 12:34:10 <bryce> no, I don't
  70. Feb 02 12:34:17 <bryce> but such a list would indeed be useful
  71. Feb 02 12:34:41 <bryce> I would like to avoid anything too risky but obviously safe stuff I can take care of pulling in
  72. Feb 02 12:35:15 <Ede_123> My personal todo list for 0.92.3 includes updating bundled documentation / tutorials and some installer fixes on Windows (if I find the time).
  73. Feb 02 12:35:16 <bryce> and if there's anything highly important or urgent we can put special attention on getting those in
  74. Feb 02 12:35:22 <Ede_123> Should be fine risk-wise...
  75. Feb 02 12:35:55 <bryce> ok great
  76. Feb 02 12:36:06 <Ede_123> I migrated inkscape-docs to GitLab but I still need to get around updating and actually including it in the release
  77. Feb 02 12:37:10 <bryce> ACTION: Land MR for the gcodetools patch from the forums
  78. Feb 02 12:37:31 <bryce> ACTION: Scrub git changelog to identify changes needing documented in the Release Notes [bryce]
  79. Feb 02 12:38:04 <bryce> ACTION: Document Tav's recent 0.92.3 changes into the Release Notes [Tav]
  80. Feb 02 12:38:45 <bryce> ACTION: Notify translators [Ede_123] -- DONE
  81. Feb 02 12:39:30 <bryce> ACTION: Acquire or build a list of commits worth backporting (see https://bugs.launchpad.net/inkscape/+bugs?field.tag=backport-proposed for a start)
  82. Feb 02 12:40:05 <bryce> ACTION: Update bundled documentation / tutorials (inkscape-docs) in the release [Ede_123]
  83. Feb 02 12:40:18 <bryce>
  84. Feb 02 12:40:24 <bryce> === Status of platform packaging ===
  85. Feb 02 12:41:00 <bryce> Ede_123, ok you mentioned installer fixes for Windows. How are things looking for packaging?
  86. Feb 02 12:41:52 <bryce> Ede_123, also, if we were to release in march do you have any major time commitments that month we should schedule around to avoid?
  87. Feb 02 12:42:41 <Ede_123> Packaging for Windows should be fine - I tracked down many bugs we introduced with the switch to MSYS2 in 0.92.2 which are fixed now, so I suspect 0.92.3 to be one of the most stable releases since quite some time
  88. Feb 02 12:42:47 <bryce> tedg, same question for you -- I know you mentioned SCALE and am guessing you'll be at the Hackfest so early and late march I'm guessing would be no-go?
  89. Feb 02 12:43:20 <bryce> are any OSX or other packagers around? If so, same questions to you...
  90. Feb 02 12:43:48 <Ede_123> The installer fixes are for some annoying glitches but I'd consider them optional - it worked without them so far in most cases, so it would do without them in the worst case
  91. Feb 02 12:44:11 <bryce> Ede_123, ok
  92. Feb 02 12:45:04 <Ede_123> time-wise it should be fine in march, especially as I do not expect the release to be too time consuming this time (MSYS2 played out nicely and the build system is mostly automated now)
  93. Feb 02 12:45:56 <bryce> Ede_123, for 0.92.2 did you do a single package release of the installer or did you do updates of it as improvements came in? I'm guessing with installers the latter approach should be ok if there are problems?
  94. Feb 02 12:46:40 <jabiertxof> ooohhhh:(
  95. Feb 02 12:46:53 <bryce> jabiertxof, ?
  96. Feb 02 12:46:55 <jabiertxof> lost meetengs
  97. Feb 02 12:47:05 <Ede_123> there weren't any blockers, so I did not release updates. For individual issues we have CI builds now which came in very handy.
  98. Feb 02 12:47:58 <bryce> jabiertxof, ah sorry again. I'll be posting transcripts later
  99. Feb 02 12:48:14 <jabiertxof> thanks so much!
  100. Feb 02 12:48:17 <bryce> === Release cycle plans ===
  101. Feb 02 12:48:31 <jabiertxof> still one great!
  102. Feb 02 12:48:34 <tedg> bryce: I wasn't planning on going to the hackfest, I didn't think it'd really be worth sending me.
  103. Feb 02 12:49:18 <tedg> bryce: Generally the snap package is much improved in the 0.92.x branch, so I'm excited for an 0.92.3 release to get it out.
  104. Feb 02 12:49:20 <bryce> so given the shortlist of things to backport, I don't see a need for a very lengthy release process. A month is feeling like a workable timeframe so far
  105. Feb 02 12:49:25 <Tavmjong> tedg: Why not? You've got your name on a lot of the code?
  106. Feb 02 12:49:41 <tedg> bryce: FYI, I fixed the version number stuff so you control it entirely in the CMake files.
  107. Feb 02 12:49:52 <bryce> tedg, awesome thanks
  108. Feb 02 12:50:04 <tedg> Tavmjong: Not that much in the last few years.
  109. Feb 02 12:51:10 <Tavmjong> One thing I would like to do at the hackfest is have a review of Inkscape's code structure. Having experienced programmers around would really help.
  110. Feb 02 12:51:28 <Ede_123> Moini: One thing wrt to docs - how important do you think translations are for them?
  111. Feb 02 12:52:00 <bryce> tedg, yeah it'd be great to have you there. No need to decide now, but give it some thought.
  112. Feb 02 12:52:29 <Ede_123> Obviously we have some new command line options and after getting them documented they would not yet be translated - would that be acceptable?
  113. Feb 02 12:52:50 <Moini> Ede_123 : If they'll be online later, that would be good. Won't they just be added in in English?
  114. Feb 02 12:53:05 <Ede_123> No, we have also translated documentation
  115. Feb 02 12:53:21 <bryce> I'm going to do just a single pre-release this time. I know better than skipping pre-releases entirely. But at this point it's not sounding like there'd be much value in doing more than one.
  116. Feb 02 12:53:45 <Moini> Ede_123 : I meant the strings, they'll just be in English, but they'll be there in the translations?
  117. Feb 02 12:53:47 <bryce> at least, I'm hoping to continue work on the release scripts and docs, so doing a pre-release would be a useful exercise for me.
  118. Feb 02 12:54:48 <Ede_123> Moini: I guess - it's basically a gettext translation
  119. Feb 02 12:55:38 <Ede_123> But I guess most users will be reading on the website anyway...
  120. Feb 02 12:56:28 <Ede_123> (which will be another thing to tackle once inkscape-docs are up-to-date)
  121. Feb 02 12:56:41 <Moini> Ede_123 : Probably. Or on the command line. And we can expect those to speak English, for the most part.
  122. Feb 02 12:56:53 <bryce> regarding timeframe for releasing... I think we should have another meeting in a month after the next board meeting. We can do a go/no-go then
  123. Feb 02 12:57:33 <bryce> I'll try and get the pre-release done a week before that meeting so it gets a chance for some testing
  124. Feb 02 12:57:56 <jabiertxof> great!
  125. Feb 02 12:58:19 <bryce> if that all looks good, I could spin the release tarball that weekend, then notify packagers to package, then the release announcement would be when they're ready to go, say +2 days
  126. Feb 02 12:59:15 <Ede_123> Sounds good
  127. Feb 02 12:59:54 <bryce> if that plan all works out ok, that puts a release announcement at somewhere in the Mar 6-8 range, so that gets it out the door prior to SCALE
  128. Feb 02 13:00:19 <bryce> alright let's pencil that in as a plan. We can adjust if anything bad crops up
  129. Feb 02 13:00:46 <bryce> I wanted to talk a little about 0.93, but we're running over time and my wife's calling me down to lunch :-D
  130. Feb 02 13:01:00 <Moini> It's dinner here ;-)
  131. Feb 02 13:01:08 <bryce> but we can talk on that for the March 2nd meeting
  132. Feb 02 13:01:12 <bryce> === Other Business ===
  133. Feb 02 13:01:29 <bryce> any other release related topics to talk about?
  134. Feb 02 13:02:35 <bryce> ok if not, bon appetite !
  135. Feb 02 13:02:39 <bryce> == End of Meeting ==
  136. Feb 02 13:02:41 <bryce> thanks all, cya
  137. Feb 02 13:02:55 <doctormon> thanks bryce
  138. Feb 02 13:02:57 <Moini> Thanks, to you too.
  139. Feb 02 13:25:15 <jabiertxof> I loose the meeting again :(
  140. Feb 02 13:25:28 <jabiertxof> realy want the 15 min reminder!!!!
  141. Feb 02 13:26:30 <ryangorley> Today was the board meeting. Tomorrow is the Vectors meeting
  142. Feb 02 13:26:32 <Lazur> I couldn't enter earlier
  143. Feb 02 13:26:41 <jabiertxof> next time write it in my calendar!
  144. Title: Release 0.92.3 Meeting - February 2, 2018
  145. Text Format: IRC logs
  146. License: CC-BY-SA
 
 

674

Release 0.92.3 Meeting - February 2, 2018

Release 0.92.3 Meeting - February 2, 2018

PasteBin

Zeilen
147
Wörter
2257
Größe
13,0 KB
Erstellt
Typ
text/x-irclog
Creative Commons Attribution Share-Alike 3.0 (CC-BY-SA 3.0)
Bitte melde Dich an, um einen Kommentar zu verfassen!