Re: Beta-blockers ?

--===============7744344510513299891==
Content-Type: multipart/alternative; boundary="----R42IFCK7UYOYETZTYREQ4RGTR706GH"
Content-Transfer-Encoding: 7bit

------R42IFCK7UYOYETZTYREQ4RGTR706GH
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
 charset=UTF-8

About XML editor is near ok to beta try to merge my latest changes this wee=
kend=2E

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:
W=
e want to think if we ship the experimental icon theme, not affect code wis=
e
I'm in mobile about the branch you mentioned think is one of two about sh=
ipping inkscape with custom gtk themes
Is a decision we need to take


=E2=
=81=A3Enviado desde TypeApp =E2=80=8B

En 12 ago=2E 2019 21:59, en 21:59, M=
arc Jeanmougin <marc@jeanmougin=2Efr> escribi=C3=B3:
>Hi!
>
>
>I'd like to =
organize an IRC/RC release meeting to discuss, well, the
>release timing an=
d TODO=2E I guess the most practical would be 19h CEST,
>same as board meet=
ing (what about early next week ?)=2E I do have some
>questions prior to it=
 to better estimate the stuff to do, with people
>from whom I'd like some i=
nput=2E Would it be possible to get a clearer
>picture on the following poi=
nts before the meeting ?
>
>
>=3D=3D Extensions (Martin, Patrick, others) =
=3D=3D
>
>What is the state of extensions (#156) ? In particular, their
>tr=
anslatability (#333) ? Is the current submodule commit in a "good
>state" ?=
 What to do with the old uniconvertor extensions, do we update
>them to uni=
convertor 2=2E0rc5 ?
>
>=3D=3D Theming (Jabier, others) =3D=3D
>
>How stabl=
e and maintainable is the stuff we intend to ship with
>Inkscape
>? CSS, ic=
ons ? How do they interact with one another, and which one do
>we want to s=
how as default ? What was the goal of MR !811 and how does
>it comply with =
user expectations ?
>
>=3D=3D LPEs (Jabier) =3D=3D
>
>Are all LPEs stable e=
nough to be shipped ?
>
>=3D=3D Gtk General interface stuff (all) =3D=3D
>
=
>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 st=
ill reproducible ?
>
>=3D=3D Packaging (RdH, Patrick, others) =3D=3D
>
>App=
roximately how much work is still needed for macOS stable dmg
>production o=
r windows packaging ?
>
>What happens with the ubuntu bionic "dependency wa=
it" ? (
>https://launchpadlibrarian=2Enet/437056488/buildlog=2Etxt=2Egz )
>=

>=3D=3D Stability (Maren, Chris, all) =3D=3D
>
>How do people feel about g=
eneral stability ? any things that would
>definitely look bad in a beta ?
>=

>=3D=3D XML editor (Jabier) =3D=3D
>
>Is all the work on it finished ?
>
>=
=3D=3D Performance (all) =3D=3D
>
>Do we still have these massive performan=
ce problems as soon as the
>Objects dialog (or XML ?) has been opened ?
>
>=
=3D=3D Text (Tav, Jabier, others) =3D=3D
>
>How usable is the text tool ? D=
o we implement the "hamburger" toolbar ?
>Do we still have issues with vari=
able font sliders ? How understandable
>are our text tools, and are users a=
ble to "just write text" without
>surprises ? (with line heights for instan=
ce ?)
>
>=3D=3D SVG2 (Tav, all) =3D=3D
>
>I'm not sure we have discussed en=
ough the transition between SVG1=2E1 and
>SVG2=2E If we start producing svg=
2 documents that are not svg1=2E1-valid,
>should we use version=3D"2" in <s=
vg> ? how will it be understood by other
>renderers ? When and how do we in=
tend to switch the 1=2E2 flawed text
>into
>the newly flawed text, how will=
 we handle old documents, and how do we
>ensure they will render exactly th=
e same ? Do we provide a way to save
>in "valid SVG1=2E1 document without S=
VG2 stuff" ?
>
>=3D=3D Documentation (Maren) =3D=3D
>
>I saw https://gitlab=
=2Ecom/inkscape/inkscape-docs/documentation/issues/2
>,
>do we have more st=
uff to update ? By the way, how do we sync the
>inkscape/inkscape repo with=
 the inkscape/inkscape-docs ?
>
>=3D=3D Other business (all) =3D=3D
>
>Any =
other problem that I could be missing ?
>
>-- 
>Mc
>
>
>Le 08/07/2019 =C3=
=A0 15:54, Marc Jeanmougin a =C3=A9crit=C2=A0:
>> Le 07/07/2019 =C3=A0 15:3=
9, Patrick Storz a =C3=A9crit=C2=A0:
>>> Regarding the release schedule, co=
uld you clarify:
>>> - will this be the only beta release?
>>> - will there=
 be release candidates before the final Inkscape 1=2E0
>release
>>> (and if=
 yes how many and in what approx=2E 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=2E Crashes are regrettable, UI could be subject to smal=
l
>> change, new features should be testable, strings should not change=2E
=
>> Blockers for going beta would be bugs that prevent basic usage of
>> Ink=
scape, and focus is given to stability and bugfixes=2E I think we
>can
>> a=
im for releasing one beta every ~two weeks during the summer with
>the
>> a=
im for going to RC at the end of august, so ~4 beta at e=2Eg=2E 10/7,
>24/7=
,
>> 7/8, 21/8=2E Note that I still aim for string freeze at end of july,
>=
which
>> means between the second one and the third one=2E
>>
>> - For RC, =
UI should be fixed, and no bug should prevent someone to
>work
>> however h=
e/she wants with Inkscape=2E Priority should be given to
>fixing
>> edge-ca=
se crashes, checking compatibility with previous files, and
>> packaging pr=
eparations=2E Blockers for going to RC would be big UI
>> problems, renderi=
ng bugs, or crashes detected in beta that happen in
>any
>> "normal" usage=
=2E IMO, we could aim for one at end of August, then one
>per
>> week as lo=
ng as we have release blockers (which means one in total,
>> right ?)=2E
>>=

>> - 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
>> o=
perations (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
>the=
se
>> 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/expo=
rt PDF and SVG=2E
>>
>>
>>
>>> - XML/editor style dialog=2E 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=2E Line-height stuff is currently pretty broken after
>Alex=
'
>>> latest rewrite and Jabier/Tav are still thinking about ways to
>impro=
ve
>>> 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 f=
eeling I won't start with this unless I'm
>>> forced to by a deadline, so i=
t'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=2E
>;-)
>> We can aim for =C3=9F2^^=

>>
>>> On top of that I still think we should get the =2Einx format change=
s
>we
>>> were discussing into 1=2E0 (might not be absolutely necessary to
=
>already
>>> have for beta, though)=2E 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=2E
>> Sure!
>>
>> Le 05/07=
/2019 =C3=A0 23:09, Ren=C3=A9 de Hesselle a =C3=A9crit=C2=A0:
>>> Hi Mc and=
 all,
>>>
>>> I reviewed the open issues regarding macOS and I consider the=
se
>three
>>> as potential blockers for beta:
>>>
>>> - crash: https://gitl=
ab=2Ecom/inkscape/inkscape/issues/266
>>> - not sure how painful:
>https://=
gitlab=2Ecom/inkscape/inkscape/issues/278
>>> - annoying: https://gitlab=2E=
com/inkscape/inbox/issues/535
>>>
>>> Opinions?
>>>
>>> --
>>> RdH
>>
>> Th=
e second one is fixed, and the two other look like things that
>should
>> n=
ot prevent to launch a beta (the "font editor" is not the most used
>> thin=
g, and the other is certainly an annoyance but looks like
>something
>> hav=
ing 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 f=
orward with a plan, and if
>we
>> end up needing more time, then so be it :=
)
>>
>>
>>
>> _______________________________________________
>> Inkscape D=
evel mailing list -- inkscape-devel@lists=2Einkscape=2Eorg
>> To unsubscrib=
e send an email to
>inkscape-devel-leave@lists=2Einkscape=2Eorg
>
>
>
>----=
--------------------------------------------------------------------
>
>
>
=
>------------------------------------------------------------------------
>=

>_______________________________________________
>Inkscape-devel mailing l=
ist
>Inkscape-devel@lists=2Esourceforge=2Enet
>https://lists=2Esourceforge=
=2Enet/lists/listinfo/inkscape-devel

------R42IFCK7UYOYETZTYREQ4RGTR706GH
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div dir=3D"auto">About XML editor is near ok to b=
eta try to merge my latest changes this weekend=2E<br><br></div>
<div dir=
=3D"auto">About hamburger/line height I have a tested branch with good line=
 height ui but I want to know Tav opinion<br><br></div>
<div dir=3D"auto">A=
bout LPE need to give a turn but I'm super busy this next two months<br><br=
></div>
<div dir=3D"auto">About theming seems ok but pending:<br></div>
<di=
v dir=3D"auto">We want to think if we ship the experimental icon theme, not=
 affect code wise<br></div>
<div dir=3D"auto">I'm in mobile about the branc=
h you mentioned think is one of two about shipping inkscape with custom gtk=
 themes<br></div>
<div dir=3D"auto">Is a decision we need to take<br><br><b=
r></div>
<div dir=3D"auto"><!-- tmjah_g_1299s -->Enviado desde <!-- tmjah_g=
_1299e --><a href=3D"http://www=2Etypeapp=2Ecom/r?b=3D15283"><!-- tmjah_g_1=
299s -->TypeApp<!-- tmjah_g_1299e --></a><!-- tmjah_g_1299s --> <!-- tmjah_=
g_1299e --></div>
<div class=3D"gmail_quote" >En 12 ago=2E 2019, en 21:59, =
Marc Jeanmougin &lt;<a href=3D"mailto:marc@jeanmougin=2Efr" target=3D"_blan=
k">marc@jeanmougin=2Efr</a>&gt; escribi=C3=B3:<blockquote class=3D"gmail_qu=
ote" style=3D"margin: 0pt 0pt 0pt 0=2E8ex; border-left: 1px solid rgb(204, =
204, 204); padding-left: 1ex;">
<pre class=3D"blue">Hi!<br><br><br>I'd like=
 to organize an IRC/RC release meeting to discuss, well, the<br>release tim=
ing and TODO=2E I guess the most practical would be 19h CEST,<br>same as bo=
ard meeting (what about early next week ?)=2E I do have some<br>questions p=
rior to it to better estimate the stuff to do, with people<br>from whom I'd=
 like some input=2E Would it be possible to get a clearer<br>picture on the=
 following points before the meeting ?<br><br><br>=3D=3D Extensions (Martin=
, Patrick, others) =3D=3D<br><br>What is the state of extensions (#156) ? I=
n particular, their<br>translatability (#333) ? Is the current submodule co=
mmit in a "good<br>state" ? What to do with the old uniconvertor extensions=
, do we update<br>them to uniconvertor 2=2E0rc5 ?<br><br>=3D=3D Theming (Ja=
bier, others) =3D=3D<br><br>How stable and maintainable is the stuff we int=
end to ship with Inkscape<br>? CSS, icons ? How do they interact with one a=
nother, and which one do<br>we want to show as default ? What was the goal =
of MR !811 and how does<br>it comply with user expectations ?<br><br>=3D=3D=
 LPEs (Jabier) =3D=3D<br><br>Are all LPEs stable enough to be shipped ?<br>=
<br>=3D=3D Gtk General interface stuff (all) =3D=3D<br><br>Do we still have=
 interface problems like toolbars not showing up or<br>menus needing two cl=
icks, or anything of the sort, on any platform ? Is<br>#195 still reproduci=
ble ?<br><br>=3D=3D Packaging (RdH, Patrick, others) =3D=3D<br><br>Approxim=
ately how much work is still needed for macOS stable dmg<br>production or w=
indows packaging ?<br><br>What happens with the ubuntu bionic "dependency w=
ait" ? (<br><a href=3D"https://launchpadlibrarian=2Enet/437056488/buildlog=
=2Etxt=2Egz">https://launchpadlibrarian=2Enet/437056488/buildlog=2Etxt=2Egz=
</a> )<br><br>=3D=3D Stability (Maren, Chris, all) =3D=3D<br><br>How do peo=
ple feel about general stability ? any things that would<br>definitely look=
 bad in a beta ?<br><br>=3D=3D XML editor (Jabier) =3D=3D<br><br>Is all the=
 work on it finished ?<br><br>=3D=3D Performance (all) =3D=3D<br><br>Do we =
still have these massive performance problems as soon as the<br>Objects dia=
log (or XML ?) has been opened ?<br><br>=3D=3D Text (Tav, Jabier, others) =
=3D=3D<br><br>How usable is the text tool ? Do we implement the "hamburger"=
 toolbar ?<br>Do we still have issues with variable font sliders ? How unde=
rstandable<br>are our text tools, and are users able to "just write text" w=
ithout<br>surprises ? (with line heights for instance ?)<br><br>=3D=3D SVG2=
 (Tav, all) =3D=3D<br><br>I'm not sure we have discussed enough the transit=
ion between SVG1=2E1 and<br>SVG2=2E If we start producing svg2 documents th=
at are not svg1=2E1-valid,<br>should we use version=3D"2" in &lt;svg&gt; ? =
how will it be understood by other<br>renderers ? When and how do we intend=
 to switch the 1=2E2 flawed text into<br>the newly flawed text, how will we=
 handle old documents, and how do we<br>ensure they will render exactly the=
 same ? Do we provide a way to save<br>in "valid SVG1=2E1 document without =
SVG2 stuff" ?<br><br>=3D=3D Documentation (Maren) =3D=3D<br><br>I saw <a hr=
ef=3D"https://gitlab=2Ecom/inkscape/inkscape-docs/documentation/issues/2">h=
ttps://gitlab=2Ecom/inkscape/inkscape-docs/documentation/issues/2</a> ,<br>=
do we have more stuff to update ? By the way, how do we sync the<br>inkscap=
e/inkscape repo with the inkscape/inkscape-docs ?<br><br>=3D=3D Other busin=
ess (all) =3D=3D<br><br>Any other problem that I could be missing ?<br></pr=
e></blockquote></div></body></html>
------R42IFCK7UYOYETZTYREQ4RGTR706GH--



--===============7744344510513299891==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============7744344510513299891==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Inkscape-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

--===============7744344510513299891==--