> ----- Message from "Jim Lawrence" <[EMAIL PROTECTED]> on Thu, 12
>
>
> I understand from my R&D and Product Management teams that there are
> issues with easy access to a previous version of OpenHPI.
There is easy access to previous versions of OpenHPI. It is a matter of
modifying the url (given to Pothier earlier) to get the version you want.
However, we remove versions from view when we find it contains serious
bugs that have been fixed in the next patch release. We do this to
encourage use of the fixed versions. Still, all are available by invoking
the url and it is common SourceForge.net knowledge.
>
> Please let me offer some thoughts…
>
> With ENEA customer’s as an example, telecom equipment manufactures
> require a very long and rigorous testing and certification process
> prior to deploying any software release into their live revenue
> generating networks. Depending on the complexity of integration,
> this process can collectively take from 3 to 9 months. This of
> course is after many months of development and validation testing by
> the software vendor. So it is not unusual to require a stable
> release from OpenHPI to be available for up to a year. But, it is
> actually much longer than that as most equipment manufactures
> require SW to be supported for at least 5 years.
The length of these processes is unfortunate. It seems to me that with
such rigourous processes, time restrictions, and support requirements, it
would make sense for you to keep the version you are using in a safe place
rather than relying on a free open source project to continue to support
and/or host old releases. That is the best way to cover you bases on that
side for this or any open source project you make use of in such manner.
Expecting old versions to be kept around on other people's servers for 5+
years is not wise given you are so dependent on them. For example,
SourceForge.net could suffer major data loss, or they can decide to purge
files at any moment based on their own criteria.
Also, I think quality is better than process, and when process blocks you
from providing a version that has serious bugs in the protocol library
fixed, it would make me think twice. However, I do understand that serious
bugs to us are not necessarily serious to you depending on your use of the
library code.
In conclusion, you can use the url that I provided Pothier and change the
version, to get the version you want. However, I recommend keeping a few
copies on your side to be safe.
--Renier
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
