|[eclipse.org-architecture-council] [Bug 262018] New: Revise the Version Numbering Guidelines to take external providers into account|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=262018 Product/Component: Community / Architecture Council Summary: Revise the Version Numbering Guidelines to take external providers into account Product: Community Version: unspecified Platform: PC URL: http://wiki.eclipse.org/Version_Numbering OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: Architecture Council AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx ReportedBy: martin.oberhuber@xxxxxxxxxxxxx Depends on: 262015 The recent case of the Platform moving from ICU4J 3.8 to ICU4J 4.0 (which does not contain any breaking API change) sparked off a discussion about how we can deal with 3rd party libraries following version numbering guidelines other than what we are accustomed to. Since 3rd party bundles are all to be consumed via Orbit, I have filed Orbit bug 262015 to create an infrastructure and policy for capturing and disseminating information about version numbering semantics other than Eclipse. At the same time, we should review our Version Numbering Guidelines  to make people aware of the fact that not all the world numbers their versions like we do. Once the Orbit infrastructure is in place, that document should also contain a link to the place where Orbit announces version semantics of its bundles.  http://wiki.eclipse.org/Version_Numbering -- Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
Back to the top