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

Bug 419486

Summary:	Use semantic version numbers for Orion npm package
Product:	[ECD] Orion	Reporter:	Mark Macdonald <mamacdon>
Component:	Node	Assignee:	Project Inbox <orion.server-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	john.arthorne
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Mark Macdonald

2013-10-15 12:52:37 EDT

The version numbers we publish to npm are meaningless. For example, the 'orion' package on npm is currently at v0.0.21, which contains the Orion client code from after 4.0M1 but before 4.0M2.

We do tag each npm release in the client repo, but currently the only way to tell what is in a given npm version of orion is to checkout the repo, and inspect the tag.

We should start using npm version numbers that correspond to Orion releases somehow, so you can easily tell what you're getting.

We could simply start matching minor version numbers to Orion releases, like this:
> 4.0M1     v0.4.0-beta.1
> 4.0M2     v0.4.0-beta.2
> 4.0RC1    v0.4.0-rc.1
> 4.0RC2    v0.4.0-rc.2
> 4.0       v0.4.0

The major and minor version numbers are supposed to make meaningful guarantees about API compatibility.

More info about version ranges is here:
https://npmjs.org/doc/misc/semver.html#Ranges
http://semver.org/

Comment 1 John Arthorne

2015-05-05 16:18:14 EDT

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:


https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html