Re: Beta-blockers ?

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============5770766369889249041==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="oqr50wrkcFAJZqPvf8EBKzajqClsDgLwU"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--oqr50wrkcFAJZqPvf8EBKzajqClsDgLwU
Content-Type: multipart/mixed; boundary="ZoghWc9R4aLNVdixcxryPnueaBplzOgcL";
 protected-headers="v1"
From: Marc Jeanmougin <[email protected]>
To: [email protected]
Cc: [email protected]
Message-ID: <968bd3e9-fc11-d4f1-1d70-0dd0eb41a199-1sOBi8b+1PADuAUI9svDHg@public.gmane.org>
Subject: Re: [Inkscape-devel] Beta-blockers ?
References: <949a9981-7919-eff7-c4a2-ac03eb2967df-1sOBi8b+1PADuAUI9svDHg@public.gmane.org>
 <c06f69a8-1319-c0d7-0e40-ca1bd6723322-1sOBi8b+1PADuAUI9svDHg@public.gmane.org>
 <9d00739c-69d0-1775-6d8d-856c674158e0-Mmb7MZpHnFY@public.gmane.org>
 <50473615-88a5-2ca2-f7c7-2da9ee95987c-1sOBi8b+1PADuAUI9svDHg@public.gmane.org>
In-Reply-To: <50473615-88a5-2ca2-f7c7-2da9ee95987c-1sOBi8b+1PADuAUI9svDHg@public.gmane.org>

--ZoghWc9R4aLNVdixcxryPnueaBplzOgcL
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

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 ?


=3D=3D Extensions (Martin, Patrick, others) =3D=3D

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 ?

=3D=3D Theming (Jabier, others) =3D=3D

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 ?

=3D=3D LPEs (Jabier) =3D=3D

Are all LPEs stable enough 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 still reproducible ?

=3D=3D Packaging (RdH, Patrick, others) =3D=3D

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 )

=3D=3D Stability (Maren, Chris, all) =3D=3D

How do people feel about general 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 performance 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 ? 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 ?)

=3D=3D SVG2 (Tav, all) =3D=3D

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=3D"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" ?

=3D=3D Documentation (Maren) =3D=3D

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 ?

=3D=3D Other business (all) =3D=3D

Any other problem that I could be missing ?

--=20
Mc


Le 08/07/2019 =C3=A0 15:54, Marc Jeanmougin a =C3=A9crit=C2=A0:
> Le 07/07/2019 =C3=A0 15:39, Patrick Storz a =C3=A9crit=C2=A0:
>> 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 relea=
se
>> (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 mos=
t
> 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, whic=
h
> 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 an=
y
> "normal" usage. IMO, we could aim for one at end of August, then one pe=
r
> 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 Ale=
x'
>> 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 da=
te
>> for the beta and make sure to let me know a week or so in advance. ;-)=

> We can aim for =C3=9F2^^
>
>> 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 intend=
ed
>> 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 =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 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/27=
8
>> - 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 :)
>
>
>
> _______________________________________________
> Inkscape Devel mailing list -- [email protected]
> To unsubscribe send an email to inkscape-devel-leave-IAPFreCvJWOGcOH861XKih2eb7JE58TQ@public.gmane.org=



--ZoghWc9R4aLNVdixcxryPnueaBplzOgcL--

--oqr50wrkcFAJZqPvf8EBKzajqClsDgLwU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQR06NoTmAVagSCydutfyyBO+IKwegUCXVG6eQAKCRBfyyBO+IKw
epq8AKDBqgY6fn0FFDZZVDsew209L1arvgCfWKmMH8m0ZEkC2SdozcITmE3RWdc=
=CmYs
-----END PGP SIGNATURE-----

--oqr50wrkcFAJZqPvf8EBKzajqClsDgLwU--


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


--===============5770766369889249041==
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

--===============5770766369889249041==--