[Linuxptp-devel] Time to make a 1.0 release?

[Richard Cochran]

Dear linuxptp users and developers,

The project is now just over one year old, and everything on my todo
list has been implemented (or at least everything important to me).
We have had a few bugs fixed via the email lists, and there have also
been a number of nice improvements contributed over that last few
months.

Up until now I haven't released any tar ball on SF.net, and so I
wonder whether it is time to publish a 1.0 version. I think the
present state is quite useable and stable, and there haven't been any
bugs reported recently.

The following features have already been finished:

- Hardware and software time stamping.
- Linux PTP Hardware Clock (PHC) subsystem, and
synchronizing the system clock to it.
- Boundary Clock and Ordinary Clock.
- IEEE 802.1AS-2011 in the role of end station.
- Transport over UDP/IPv4, UDP/IPv6, and raw Ethernet (Layer 2 and VLAN).
- Profile configuration via INI like files.
- Reading out of the data sets via management messages.
- Path trace TLV.
- Man pages.

Here some features that can wait for some future release, if demand
appears for them:

- Transparent clock.
- Asymmetry correction.
- Reading out individual data set elements via management messages.
- Reconfiguration (SET and COMMAND) via management messages.
- DeviceNET, ControlNET, and PROFINET transports.
- All other "optional" stuff, like unicast, alternate masters, and so on.

What do you all think, is it time for a release?
Or should we even bother with numbered releases at all?

Thanks,
Richard

[Richard Cochran]

Post by Richard Cochran
- Hardware and software time stamping.
- Linux PTP Hardware Clock (PHC) subsystem, and
synchronizing the system clock to it.
- Boundary Clock and Ordinary Clock.
- IEEE 802.1AS-2011 in the role of end station.
- Transport over UDP/IPv4, UDP/IPv6, and raw Ethernet (Layer 2 and VLAN).
- Profile configuration via INI like files.
- Reading out of the data sets via management messages.
- Path trace TLV.
- Man pages.

Forgot to add:

- Local IPC via UNIX Domain Sockets.
- Simple management client.

Thanks,
Richard

[Miroslav Lichvar]

Post by Richard Cochran
What do you all think, is it time for a release?

I'd say it has been for quite some time :).

Please also consider announcing the release on freshmeat, that should
help with getting new users quickly.

Post by Richard Cochran
Or should we even bother with numbered releases at all?

I think many users don't consider a project worth trying unless there
is a tarball which can easily downloaded.

Thanks for all the work you are doing on this project.

[Subhendu Ghosh]

Post by Miroslav Lichvar
I think many users don't consider a project worth trying unless there
is a tarball which can easily downloaded.

+1

On the futures list - wondering if there could be some tracepoint
support for debugging usage

-subhendu

[Keller, Jacob E]

-----Original Message-----
Sent: Friday, December 07, 2012 12:08 AM
Subject: [Linuxptp-users] Time to make a 1.0 release?
Dear linuxptp users and developers,
Here some features that can wait for some future release, if demand
- Transparent clock.
- Asymmetry correction.
- Reading out individual data set elements via management messages.
- Reconfiguration (SET and COMMAND) via management messages.
- DeviceNET, ControlNET, and PROFINET transports.
- All other "optional" stuff, like unicast, alternate masters, and so on.
What do you all think, is it time for a release?
Or should we even bother with numbered releases at all?

+1 for release. I think the project is stable. I recently attended the last IEEE 1588 Plugfest, and many companies and people were still using ptpdv2 (with hacks for hardware timestamping) and had never heard of ptp4l or the linuxptp project. I think announcing an official release is definitely a good idea. None of the features on the future list are high priority, but I think as more people see the project they can definitely be implemented in the future.

Official release is definitely great for getting many users who would otherwise avoid it.

In terms of future list, I definitely would like to see Asymmetry correction at some point.

Thanks again!

- Jake

[Richard Cochran]

Post by Keller, Jacob E
In terms of future list, I definitely would like to see Asymmetry correction at some point.

I thought this should be included in v1.0, and it wasn't too hard, so
I posted a patch today. Care to give it a try?

Thanks,
Richard

[Stephan Gatzka]

+1 for an official release.

We use ptp4l in our products, its stable and we are more than happy with it.

Regards,

Stephan

[Mario Molitor]

+1 for an official release.

I am more than happy with it.

Regards and thanks for all,
Mario