I have decided to hang a big 1.0.0 version number on what is
otherwise not an interesting PVXS release. Although I suppose
that is the point. The API has been stable, and this seems
likely to continue.
This milestone does mean that my stated version numbering
policy comes into full force. So going forward, any backwards
incompatible change, not matter how slight, would trigger 2.0.0.
Conversely, any further 1.x.x releases should be fully
backwards compatible.
https://mdavidsaver.github.io/pvxs/details.html#release-policy
In terms of actual content, There is a bug fix and a minor
API addition (and ABI change).
download https://github.com/mdavidsaver/pvxs/releases
documentation https://mdavidsaver.github.io/pvxs
release notes https://mdavidsaver.github.io/pvxs/releasenotes.html
P4P is updated as well as 4.1.2 with a change by Juan Müller
@ESS to make the asyncio client less noisy on KeyboardInterrupt.
https://mdavidsaver.github.io/p4p/
https://pypi.org/project/p4p/
- Replies:
- PVXS release 1.1.0 and P4P 4.1.5 Michael Davidsaver via Tech-talk
- References:
- Re: PVXS release 0.3.0 and P4P 4.0.1 Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
Re: pyepics get_with_metadata inconstant behaviour Marco A. Barra Montevechi Filho via Tech-talk
- Next:
rpc.h of Asyn not found in Rocky 9 网易邮件中心 via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
<2022>
2023
2024
2025
- Navigate by Thread:
- Prev:
Re: PVXS release 0.3.0 and P4P 4.0.1 Michael Davidsaver via Tech-talk
- Next:
PVXS release 1.1.0 and P4P 4.1.5 Michael Davidsaver via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
<2022>
2023
2024
2025
|