Re: Seeking opinions on timestamps in version strings
I don't have a strong feeling.
I run a Jetty server that I upgrade maybe every two months or so and the number lets me get a quick read as to how old my Jetty is. I like to stay up to date, particularly because I run http/2 but if the upgrade is a distraction from a deadline I will put it off. I am sure there are better ways to manage version issues, but Jetty is just one of moving parts I am concerned with.
On Tue, Jan 5, 2016 at 1:05 PM, Joakim Erdfelt <[hidden email]> wrote:
Adding some more information here.
Here's some other Eclipse projects that don't release with timestamps
Lobos Studios | Phone: 877.919.4WEB | LobosStudios.com | Facebook.com/LobosStudios | @LobosStudios
Web Development - Mobile Development - Helpdesk/Tech Support - Computer Sales & Service
Acer Authorized Reseller - Computers, Windows and Android Tablets, Accessories
Steve Sobol - CEO, Senior Developer and Server Jockey
I agree its better, more standard (e.g. semantic) and clear without the timestamp. However, such changes tend to break downstream scripts, configs, etc. which previously had to cope with the date in the version. I suggest deferring the actual change to 9.4.0. In other words its deserves at least a MINOR release (which might have other incompatible changes) instead of just at PATCH release (9.3.7).
On Tue, Jan 5, 2016 at 9:34 AM, Joakim Erdfelt <[hidden email]> wrote:
Lets drop the timestamps from our versions strings on stable releases.
(pseudo snapshot/timestamps are still present outside of maven central)
That would mean our next release could be just "9.3.7"