Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361756

Summary:	Use human-readable bundle version qualifiers
Product:	[Technology] EGit	Reporter:	Markus Keller <markus.kell.r>
Component:	Releng	Assignee:	Project Inbox <egit.releng-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert, leohliveira, remy.suen, robin.rosenberg
Version:	1.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Markus Keller

2011-10-23 11:08:19 EDT

The JGit/EGit nightly builds use bundle versions like this: 1.2.0.201110222014

The qualifier is very hard to parse for mere mortals, since the most interesting info (day and maybe month) is embedded in a long sequence of numbers.

Could you change this to e.g. 1.2.0.20111022-2014? That would match the format used everywhere else in Eclipse.

Comment 1 Robin Rosenberg

2011-10-29 06:07:46 EDT

(In reply to comment #1)
> Could you change this to e.g. 1.2.0.20111022-2014? That would match the format
> used everywhere else in Eclipse.

From my JEE workbench plugins directory:

$ ls|grep "eclipse.*\-[0-9][0-9][0-9][0-9]\.jar"|wc -l
     176
$ ls|grep "eclipse.*[0-9][0-9][0-9][0-9][0-9]\.jar"|wc -l
     619

Counting features the "illegible" format is still in majority.

There are a number of variants in there, with/without a v, with milestone, with hyphen before time, without time, with - or _ as separator, etc.  

Before we change, if someone issues a patch; What is the foundations recommendation?

Comment 2 Markus Keller

2011-10-29 15:00:31 EDT

Unfortunately, the foundation doesn't have common rules about this. But http://wiki.eclipse.org/index.php/Version_Numbering#When_to_change_the_qualifier_segment recommends vYYYYMMDD-HHMM.

The exact format doesn't really matter, as long as it increases monotonically.