Hi all,
The toolbar bug seems fixed for most systems and only seems to appear on wayland (at least I can't trigger it on xorg), and is now reported upstream at https://gitlab.gnome.org/GNOME/gtk/issues/2000
The translation system seems better (#311), so … do anyone see any issue that would need to be fixed before releasing a beta ?
Hi Mc and all,
I reviewed the open issues regarding macOS and I consider these three as potential blockers for beta:
- crash: https://gitlab.com/inkscape/inkscape/issues/266 - not sure how painful: https://gitlab.com/inkscape/inkscape/issues/278 - annoying: https://gitlab.com/inkscape/inbox/issues/535
Opinions?
-- RdH
Am 05.07.2019 um 15:33 schrieb Marc Jeanmougin marc@jeanmougin.fr:
Hi all,
The toolbar bug seems fixed for most systems and only seems to appear on wayland (at least I can't trigger it on xorg), and is now reported upstream at https://gitlab.gnome.org/GNOME/gtk/issues/2000
The translation system seems better (#311), so … do anyone see any issue that would need to be fixed before releasing a beta ?
-- Mc
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Am 05.07.2019 um 15:33 schrieb Marc Jeanmougin:
Hi all, > > The toolbar bug seems fixed for most systems and only seems to
appear > on wayland (at least I can't trigger it on xorg), and is now reported > upstream at https://gitlab.gnome.org/GNOME/gtk/issues/2000 >
The translation system seems better (#311), so … do anyone see any >
issue that would need to be fixed before releasing a beta ?
Regarding the release schedule, could you clarify: - will this be the only beta release? - will there be release candidates before the final Inkscape 1.0 release (and if yes how many and in what approx. times before the release)?
IMHO this will change what needs to be fixed before releasing the beta. If we go for only one beta and at most one RC immediately before the release, we should try to make this beta count, i.e. make it as "finished" as possible so all functionality that will be in the final version can be thoroughly tested.
We're in a pretty solid state right now (yay, physics!) but there are a few things we should likely get wrapped up before the "final" beta: - XML/editor style dialog. I see Jabier is still actively working on that and there seem to be still some issues in it (for example I'm seeing assertion errors on the command line) - Text toolbar. Line-height stuff is currently pretty broken after Alex' latest rewrite and Jabier/Tav are still thinking about ways to improve the UI part (that wasn't ideal before) - Personally I'd like to get Windows-packaging finished for the beta release, however I have a feeling I won't start with this unless I'm forced to by a deadline, so it's probably best if you set a release date for the beta and make sure to let me know a week or so in advance. ;-)
On top of that I still think we should get the .inx format changes we were discussing into 1.0 (might not be absolutely necessary to already have for beta, though). I think I'll write up an issue with the intended changes one of these days, and if people agree with it I'd also be available to implement the changes.
Cheers, Patrick
Le 07/07/2019 à 15:39, Patrick Storz a écrit :
Regarding the release schedule, could you clarify:
- will this be the only beta release?
- will there be release candidates before the final Inkscape 1.0 release
(and if yes how many and in what approx. times before the release)?
- Ideally, no; - Yes, at least one:
Basically, here is how I see things:
- For beta, there should be no bugs that prevent "normal*" usage in most situations. Crashes are regrettable, UI could be subject to small change, new features should be testable, strings should not change. Blockers for going beta would be bugs that prevent basic usage of Inkscape, and focus is given to stability and bugfixes. I think we can aim for releasing one beta every ~two weeks during the summer with the aim for going to RC at the end of august, so ~4 beta at e.g. 10/7, 24/7, 7/8, 21/8. Note that I still aim for string freeze at end of july, which means between the second one and the third one.
- For RC, UI should be fixed, and no bug should prevent someone to work however he/she wants with Inkscape. Priority should be given to fixing edge-case crashes, checking compatibility with previous files, and packaging preparations. Blockers for going to RC would be big UI problems, rendering bugs, or crashes detected in beta that happen in any "normal" usage. IMO, we could aim for one at end of August, then one per week as long as we have release blockers (which means one in total, right ?).
- Bugs in release are inevitable, but if we could check that old files still work (and look the same), that no bugs happen with the basic operations (including exporting or exporting) or when using anything, and that the packages are ok for most platforms, then it would be good :)
*: "normal" or "basic" usage arbitrarily refer to anything using these tools : selector/node/rect/circle/star/pen/pencil/text; the whole "Object" and "Path" menus; fill&stroke dialog; align&distribute dialog; export PNG; snapping; extensions work as expected; Can open/import/export PDF and SVG.
- XML/editor style dialog. I see Jabier is still actively working on
that and there seem to be still some issues in it (for example I'm seeing assertion errors on the command line)
- Text toolbar. Line-height stuff is currently pretty broken after Alex'
latest rewrite and Jabier/Tav are still thinking about ways to improve the UI part (that wasn't ideal before)
- Personally I'd like to get Windows-packaging finished for the beta
release, however I have a feeling I won't start with this unless I'm forced to by a deadline, so it's probably best if you set a release date for the beta and make sure to let me know a week or so in advance. ;-)
We can aim for ß2^^
On top of that I still think we should get the .inx format changes we were discussing into 1.0 (might not be absolutely necessary to already have for beta, though). I think I'll write up an issue with the intended changes one of these days, and if people agree with it I'd also be available to implement the changes.
Sure!
Le 05/07/2019 à 23:09, René de Hesselle a écrit :
Hi Mc and all,
I reviewed the open issues regarding macOS and I consider these three as potential blockers for beta:
- crash: https://gitlab.com/inkscape/inkscape/issues/266
- not sure how painful: https://gitlab.com/inkscape/inkscape/issues/278
- annoying: https://gitlab.com/inkscape/inbox/issues/535
Opinions?
-- RdH
The second one is fixed, and the two other look like things that should not prevent to launch a beta (the "font editor" is not the most used thing, and the other is certainly an annoyance but looks like something having to be fixed before rc)
As usual, feel free to make any remarks on my thoughts on the subject, I by no mean plan to impose my views on How-Things-Should-Be or rush anyone, I just try to keep things moving forward with a plan, and if we end up needing more time, then so be it :)
Hi!
I'd like to organize an IRC/RC release meeting to discuss, well, the release timing and TODO. I guess the most practical would be 19h CEST, same as board meeting (what about early next week ?). I do have some questions prior to it to better estimate the stuff to do, with people from whom I'd like some input. Would it be possible to get a clearer picture on the following points before the meeting ?
== Extensions (Martin, Patrick, others) ==
What is the state of extensions (#156) ? In particular, their translatability (#333) ? Is the current submodule commit in a "good state" ? What to do with the old uniconvertor extensions, do we update them to uniconvertor 2.0rc5 ?
== Theming (Jabier, others) ==
How stable and maintainable is the stuff we intend to ship with Inkscape ? CSS, icons ? How do they interact with one another, and which one do we want to show as default ? What was the goal of MR !811 and how does it comply with user expectations ?
== LPEs (Jabier) ==
Are all LPEs stable enough to be shipped ?
== Gtk General interface stuff (all) ==
Do we still have interface problems like toolbars not showing up or menus needing two clicks, or anything of the sort, on any platform ? Is #195 still reproducible ?
== Packaging (RdH, Patrick, others) ==
Approximately how much work is still needed for macOS stable dmg production or windows packaging ?
What happens with the ubuntu bionic "dependency wait" ? ( https://launchpadlibrarian.net/437056488/buildlog.txt.gz )
== Stability (Maren, Chris, all) ==
How do people feel about general stability ? any things that would definitely look bad in a beta ?
== XML editor (Jabier) ==
Is all the work on it finished ?
== Performance (all) ==
Do we still have these massive performance problems as soon as the Objects dialog (or XML ?) has been opened ?
== Text (Tav, Jabier, others) ==
How usable is the text tool ? Do we implement the "hamburger" toolbar ? Do we still have issues with variable font sliders ? How understandable are our text tools, and are users able to "just write text" without surprises ? (with line heights for instance ?)
== SVG2 (Tav, all) ==
I'm not sure we have discussed enough the transition between SVG1.1 and SVG2. If we start producing svg2 documents that are not svg1.1-valid, should we use version="2" in <svg> ? how will it be understood by other renderers ? When and how do we intend to switch the 1.2 flawed text into the newly flawed text, how will we handle old documents, and how do we ensure they will render exactly the same ? Do we provide a way to save in "valid SVG1.1 document without SVG2 stuff" ?
== Documentation (Maren) ==
I saw https://gitlab.com/inkscape/inkscape-docs/documentation/issues/2 , do we have more stuff to update ? By the way, how do we sync the inkscape/inkscape repo with the inkscape/inkscape-docs ?
== Other business (all) ==
Any other problem that I could be missing ?
About XML editor is near ok to beta try to merge my latest changes this weekend.
About hamburger/line height I have a tested branch with good line height ui but I want to know Tav opinion
About LPE need to give a turn but I'm super busy this next two months
About theming seems ok but pending: We want to think if we ship the experimental icon theme, not affect code wise I'm in mobile about the branch you mentioned think is one of two about shipping inkscape with custom gtk themes Is a decision we need to take
Enviado desde TypeApp
En 12 ago. 2019 21:59, en 21:59, Marc Jeanmougin marc@jeanmougin.fr escribió:
Hi!
I'd like to organize an IRC/RC release meeting to discuss, well, the release timing and TODO. I guess the most practical would be 19h CEST, same as board meeting (what about early next week ?). I do have some questions prior to it to better estimate the stuff to do, with people from whom I'd like some input. Would it be possible to get a clearer picture on the following points before the meeting ?
== Extensions (Martin, Patrick, others) ==
What is the state of extensions (#156) ? In particular, their translatability (#333) ? Is the current submodule commit in a "good state" ? What to do with the old uniconvertor extensions, do we update them to uniconvertor 2.0rc5 ?
== Theming (Jabier, others) ==
How stable and maintainable is the stuff we intend to ship with Inkscape ? CSS, icons ? How do they interact with one another, and which one do we want to show as default ? What was the goal of MR !811 and how does it comply with user expectations ?
== LPEs (Jabier) ==
Are all LPEs stable enough to be shipped ?
== Gtk General interface stuff (all) ==
Do we still have interface problems like toolbars not showing up or menus needing two clicks, or anything of the sort, on any platform ? Is #195 still reproducible ?
== Packaging (RdH, Patrick, others) ==
Approximately how much work is still needed for macOS stable dmg production or windows packaging ?
What happens with the ubuntu bionic "dependency wait" ? ( https://launchpadlibrarian.net/437056488/buildlog.txt.gz )
== Stability (Maren, Chris, all) ==
How do people feel about general stability ? any things that would definitely look bad in a beta ?
== XML editor (Jabier) ==
Is all the work on it finished ?
== Performance (all) ==
Do we still have these massive performance problems as soon as the Objects dialog (or XML ?) has been opened ?
== Text (Tav, Jabier, others) ==
How usable is the text tool ? Do we implement the "hamburger" toolbar ? Do we still have issues with variable font sliders ? How understandable are our text tools, and are users able to "just write text" without surprises ? (with line heights for instance ?)
== SVG2 (Tav, all) ==
I'm not sure we have discussed enough the transition between SVG1.1 and SVG2. If we start producing svg2 documents that are not svg1.1-valid, should we use version="2" in <svg> ? how will it be understood by other renderers ? When and how do we intend to switch the 1.2 flawed text into the newly flawed text, how will we handle old documents, and how do we ensure they will render exactly the same ? Do we provide a way to save in "valid SVG1.1 document without SVG2 stuff" ?
== Documentation (Maren) ==
I saw https://gitlab.com/inkscape/inkscape-docs/documentation/issues/2 , do we have more stuff to update ? By the way, how do we sync the inkscape/inkscape repo with the inkscape/inkscape-docs ?
== Other business (all) ==
Any other problem that I could be missing ?
-- Mc
Le 08/07/2019 à 15:54, Marc Jeanmougin a écrit :
Le 07/07/2019 à 15:39, Patrick Storz a écrit :
Regarding the release schedule, could you clarify:
- will this be the only beta release?
- will there be release candidates before the final Inkscape 1.0
release
(and if yes how many and in what approx. times before the release)?
- Ideally, no;
- Yes, at least one:
Basically, here is how I see things:
- For beta, there should be no bugs that prevent "normal*" usage in
most
situations. Crashes are regrettable, UI could be subject to small change, new features should be testable, strings should not change. Blockers for going beta would be bugs that prevent basic usage of Inkscape, and focus is given to stability and bugfixes. I think we
can
aim for releasing one beta every ~two weeks during the summer with
the
aim for going to RC at the end of august, so ~4 beta at e.g. 10/7,
24/7,
7/8, 21/8. Note that I still aim for string freeze at end of july,
which
means between the second one and the third one.
- For RC, UI should be fixed, and no bug should prevent someone to
work
however he/she wants with Inkscape. Priority should be given to
fixing
edge-case crashes, checking compatibility with previous files, and packaging preparations. Blockers for going to RC would be big UI problems, rendering bugs, or crashes detected in beta that happen in
any
"normal" usage. IMO, we could aim for one at end of August, then one
per
week as long as we have release blockers (which means one in total, right ?).
- Bugs in release are inevitable, but if we could check that old
files
still work (and look the same), that no bugs happen with the basic operations (including exporting or exporting) or when using anything, and that the packages are ok for most platforms, then it would be
good :)
*: "normal" or "basic" usage arbitrarily refer to anything using
these
tools : selector/node/rect/circle/star/pen/pencil/text; the whole "Object" and "Path" menus; fill&stroke dialog; align&distribute
dialog;
export PNG; snapping; extensions work as expected; Can open/import/export PDF and SVG.
- XML/editor style dialog. I see Jabier is still actively working on
that and there seem to be still some issues in it (for example I'm seeing assertion errors on the command line)
- Text toolbar. Line-height stuff is currently pretty broken after
Alex'
latest rewrite and Jabier/Tav are still thinking about ways to
improve
the UI part (that wasn't ideal before)
- Personally I'd like to get Windows-packaging finished for the beta
release, however I have a feeling I won't start with this unless I'm forced to by a deadline, so it's probably best if you set a release
date
for the beta and make sure to let me know a week or so in advance.
;-)
We can aim for ß2^^
On top of that I still think we should get the .inx format changes
we
were discussing into 1.0 (might not be absolutely necessary to
already
have for beta, though). I think I'll write up an issue with the
intended
changes one of these days, and if people agree with it I'd also be available to implement the changes.
Sure!
Le 05/07/2019 à 23:09, René de Hesselle a écrit :
Hi Mc and all,
I reviewed the open issues regarding macOS and I consider these
three
as potential blockers for beta:
- crash: https://gitlab.com/inkscape/inkscape/issues/266
- not sure how painful:
https://gitlab.com/inkscape/inkscape/issues/278
Opinions?
-- RdH
The second one is fixed, and the two other look like things that
should
not prevent to launch a beta (the "font editor" is not the most used thing, and the other is certainly an annoyance but looks like
something
having to be fixed before rc)
As usual, feel free to make any remarks on my thoughts on the
subject, I
by no mean plan to impose my views on How-Things-Should-Be or rush anyone, I just try to keep things moving forward with a plan, and if
we
end up needing more time, then so be it :)
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to
inkscape-devel-leave@lists.inkscape.org
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (4)
-
Jabier Arraiza -
Marc Jeanmougin -
Patrick Storz -
René de Hesselle