API Change - tidyReleaseDate()

--===============0741727652204777711==
Content-Type: multipart/alternative; boundary=047d7bb70a44025bba050eb270bf

--047d7bb70a44025bba050eb270bf
Content-Type: text/plain; charset=UTF-8

Cross-posted to
 [1]: https://lists.w3.org/Archives/Public/public-htacg/
 [2]: https://sourceforge.net/p/tidy/mailman/tidy-develop
 [3]: https://lists.w3.org/Archives/Public/html-tidy/

Good day all,

This is a request for comments about the treatment of `tidyReleaseDate()`.

HTACG' current proposal and working branch currently is working on the
assumption that we will move to a semantic versioning system as a
replacement for a date-based version system. This has been implemented on
the working branch using `tidyLibraryVersion()` in the API. Our goal is the
first 5.0.0-rc.1 by February's end.

While we will deprecate `tidyReleaseDate()` it still has to return a valid
date as TidyLib users may be using it. Current development branch returns
Unix epoch time (1970/1/1), which we feel should be enough of an indicator
to users that the `tidyReleaseDate()` is no longer trustworthy.

I seek your opinions on whether you or anyone you are aware of:

- currently use `tidyReleaseDate()` in a manner that justifies its
continued existence and support?
- currently use it in a way that returning Unix epoch would break your
application?
- unwilling to make changes to your existing application to support the
transition to `tidyLibraryversion()`?
- have a better suggestion for a suitable return value during the
deprecation period?

Please comment to any of these lists, or alternative on the [issues
tracker][1].

Thank you.


References:
  [1]: https://github.com/htacg/tidy-html5/issues/148


--
---
Jim Derry
Clinton Township, MI, USA
Nanjing, Jiangsu, China PRC

--047d7bb70a44025bba050eb270bf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Cross-posted to<br>=C2=A0[1]: <a href=3D"https://lists.w3.=
org/Archives/Public/public-htacg/">https://lists.w3.org/Archives/Public/pub=
lic-htacg/</a><br>=C2=A0[2]: <a href=3D"https://sourceforge.net/p/tidy/mail=
man/tidy-develop">https://sourceforge.net/p/tidy/mailman/tidy-develop</a><b=
r>=C2=A0[3]: <a href=3D"https://lists.w3.org/Archives/Public/html-tidy/">ht=
tps://lists.w3.org/Archives/Public/html-tidy/</a><br><br>Good day all,<br><=
br>This is a request for comments about the treatment of `tidyReleaseDate()=
`.<br><br>HTACG&#39; current proposal and working branch currently is worki=
ng on the assumption that we will move to a semantic versioning system as a=
 replacement for a date-based version system. This has been implemented on =
the working branch using `tidyLibraryVersion()` in the API. Our goal is the=
 first 5.0.0-rc.1 by February&#39;s end.<div><br></div><div>While we will d=
eprecate `tidyReleaseDate()` it still has to return a valid date as TidyLib=
 users may be using it. Current development branch returns Unix epoch time =
(1970/1/1), which we feel should be enough of an indicator to users that th=
e `tidyReleaseDate()` is no longer trustworthy.</div><div><br></div><div>I =
seek your opinions on whether you or anyone you are aware of:</div><div><br=
></div><div>- currently use `tidyReleaseDate()` in a manner that justifies =
its continued existence and support?<br></div><div>- currently use it in a =
way that returning Unix epoch would break your application?</div><div>- unw=
illing to make changes to your existing application to support the transiti=
on to `tidyLibraryversion()`?</div><div>- have a better suggestion for a su=
itable return value during the deprecation period?</div><div><br></div><div=
>Please comment to any of these lists, or alternative on the [issues tracke=
r][1].</div><div><div><br></div><div>Thank you.</div><div><br><br>Reference=
s:<br>=C2=A0 [1]: <a href=3D"https://github.com/htacg/tidy-html5/issues/148=
">https://github.com/htacg/tidy-html5/issues/148</a><br><br><br>--<br>---<b=
r>Jim Derry<br>Clinton Township, MI, USA<br>Nanjing, Jiangsu, China PRC
</div></div></div>

--047d7bb70a44025bba050eb270bf--


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

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
--===============0741727652204777711==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tidy-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tidy-develop

--===============0741727652204777711==--