I would like to find definitions of the term "controlled release" on
computer company websites (i.e., "controlled release" in the context
of computer software or hardware, not in the context of controlled
release medications or other chemicals).  In particular, I am not
trying to find whether or not there is a consensus on whether the term
has a connotation of lesser quality when compared to the terms
"general release", "commercial release" or just "released".

baai...

It seems likely that we will have to derive the 
meaning by taking it in context. It may be that
it has different meanings to different companies,
and, as rippo-ga notes, it isn't listed in any
dictionaries or glossaries.

I found numerous hits to the search I did, so let's
take a look at them

"With the initial market release of Symposium Call
 Center Server 1.0, the Meridian Link Services (MLS)
 andHost Data Exchange (HDX) components will be
 available on a Controlled Release basis. This is
 being done to ensure that users of these features
 receive the highest level of support from Nortel."
...
"To this end, we are implementing a controlled
 release process for these features that will allow
 us to:

* track the deployment of these capabilities
* offer implementation guidance to customers
* enhance our ability to support installations of
  these features
-------------------------------------------------
From a Product Bulletin for Enterprise Networks
http://216.239.53.100/search?q=cache:voEIvB5ZYTAC:www.gd-wts.com/widts/Bulletins/98013sl1.pdf+software+OR+hardware+%22controlled+release%22&hl=en&ie=UTF-8
=================================================

"Coredge Software Launches Controlled Release of Logik,
 a Knowledge Preview Tool"

"'We wanted to give those who have taken the time to
 get to know us and our product the first opportunity
 to experience Logik,' said Gabriel Cassis, president
 and CEO of Coredge Software. 'We also anticipate that
 this group will provide us with valuable feedback on
 the product to help further hone the product to
 address the needs of its users,' he concluded."
-------------------------------------------------
From the Coredge site:
http://www.coredge.com/news/010730.shtml
=================================================

"Error reduction through the controlled Release of
 hardware and software to the live environment, e.g.
 avoiding incorporating an incorrect version into
 the Release"
-------------------------------------------------
From ViaDyne.com:
http://www.viadyne.com/product/itil/itil_release.htm
********************NOTE*************************
The above page is an entire discourse on the subject
of Release Management, and is an answer in itself.
=================================================

"Solomon Software launched the controlled release
 of its new Solomon IV for BackOffice product line
 in August 1998. The new product line extends the
 Solomon IV product family, which also includes
 the award-winning flagship accounting information
 system, Solomon for Windows. Solomon IV for
 BackOffice, written in Microsoft Visual Basic 5.0,
 is optimized exclusively for the Microsoft
 BackOffice platform, including Microsoft SQL
 Server and Windows NT. General release of the
 product line is scheduled for Q3 1998, however,
 it will be formally launched to the Company's
 Channel Partners at the 1998 Solomon Software
 Channel Partner Conference, August 26-29 in
 Cincinnati, Ohio."
-------------------------------------------------
From SVA.com:
http://www.sva.com/is/solomon.htm
=================================================

"CNS 1.0 is a controlled release, available to
 selected network independent software vendor
 (ISV), systems integrator (SI), and service
 provider partners, as well as internal Cisco
 engineering teams."
-------------------------------------------------
From Cisco.com, re Cisco Networking Services 1.0:
http://www.cisco.com/warp/public/cc/pd/nemnsw/nesv/prodlit/cns34_qp.htm
=================================================

I think there's enough similarity in the entries above
to state that a "controlled release" is roughly 
equivalent to a 'beta' release, defined as follows:

beta

/bay't*/, /be't*/ or (Commonwealth) /bee't*/ n.

1. Mostly working, but still under test; usu. used
with `in': `in beta'. In the Real World, systems
(hardware or software) software often go through
two stages of release testing: Alpha (in-house) and
Beta (out-house?). Beta releases are generally made
to a group of lucky (or unlucky) trusted customers.

2. Anything that is new and
experimental. "His girlfriend is in beta" means that
he is still testing for compatibility and reserving
judgment. 

3. Flaky; dubious; suspect (since beta software is
notoriously buggy).

Historical note: More formally, to beta-test is to
test a pre-release (potentially unreliable) version
of a piece of software by making it available to 
selected (or self-selected) customers and users.
-------------------------------------------------
From Dictionary.com, via Google:
http://dictionary.reference.com/search?q=beta&r=67
=================================================

I would infer that the differences would be these:
'Beta' is a more informal term, commonly used by 
individual programmers who write shareware and
freeware. These individuals often communicate with
friends, and eventually, prospective buyers, via
email and forums. They offer people the software
for free, noting that it is, or may be buggy, and
solicit feedback from users for the purpose of 
fixing bugs and making it user-friendly.

The term "controlled release" seems a more formal
term, for larger enterprises who have teams of 
developers jointly writing software. They also need
feedback, and enlist their partner organizations to
provide it following a controlled release to these
'priveleged' recipients. I would assume that because
these are businesses, and valued partners, that the
software is not released in quite as 'buggy' a state
as the typical shareware 'beta'. It would need to 
work sufficiently well for a business to use it 
without serious difficulties. Nonetheless, the 
'controlled release' would still provide the opportunity
to refine the product before a 'general release' to
the open market. It also provides the company producing
the software the opportunity to practice the art of 
providing support. It assists them in determining what
questions are frequently asked (which allows them to 
prepare documentation accordingly), and to allocate
resources for support needed for a 'general release'
based on an extrapolation of what they experience 
during the 'controlled release'.


Please do not rate this answer until you are satisfied that
the answer cannot be improved upon by means of a dialog with
the researcher through the "Request for Clarification" process.

sublime1-ga


Searches done, via Google:

software OR hardware "controlled release"
://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=software+OR+hardware+%22controlled+release%22

"definition of beta release"
://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=%22definition+of+beta+release%22

---

Request for Answer Clarification by baai-ga on 16 Dec 2002 20:41 PST

Sublime1--

I understand your likening "controlled release" to beta release, but
of the 4 web pages you site for context, only the Nortel site (the
first one) actually states something to the effect that the controlled
release product could require additional support (and therefore it
would seem that it must be of lesser quality like a beta).  The others
just reference controlled release as a way of limiting numbers of
users . . . which is not necessarily because of lesser quality (or so
some might argue).

I would tend to agree that the term -- even without definition --
tends to imply reduced quality and I have made that argument in a
legal dispute . . . the other side, however, takes the opposite
viewpoint and claims that theirs is the dominant one within the
computer industry.  Thus, I would sure like to find a couple of sites
that actually **define** the term.  I want to know the actual
connotation, even if it does not agree with my (and your) viewpoint.

FYI, I paid for prior research to come up with the number of
references to "controlled release" and they came up with the following
search:  <://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=%22controlled+release%22+%2Bsoftware+-science+-drug+-book+-fertilizer*+-situ+-society+-nitrogen&btnG=Google+Search>
which is a little more focused than the one you used.

---

Clarification of Answer by sublime1-ga on 16 Dec 2002 23:17 PST

baai...

The other search certainly limited the number of irrelevant
responses, however it only showed 8 of the 9 links I ended
up exploring. This is because Google automatically lists
the most relevant sites at the beginning of the search results,
so '+software' in the other search produced the same results
as 'software' in mine, and the -xxxx terms just removed
irrelevant sites which were already listed further down on
the list of results.

As for your comment:
"...only the Nortel site (the first one) actually states
something to the effect that the controlled release
product could require additional support (and therefore
it would seem that it must be of lesser quality like a
beta)."

I will summarize from the results I posted:

Coredge:
"We also anticipate that 
 this group will provide us with valuable feedback on 
 the product to help further hone the product to 
 address the needs of its users"
(hone = 'improve upon')

ViaDyne:
"Error reduction through the controlled Release of 
 hardware and software to the live environment.."
(error reduction = 'improve upon')

And did you read the page from ViaDyne, which I 
highlighted as a complete discourse on Release
Management? I can't duplicate the entire page
here, but the 'Scope' is as follows:
---------------------------------------------------
Scope:
 Release Management undertakes the planning, design,
 build, configuration and testing of hardware and
 software to create a set of Release components for
 a live environment. Activities also cover the
 planning, preparation and scheduling of a release
 to many customers and locations. Release Management
 is heavily dependant of Change Management and
 Configuration Management to ensure that the shared
 CMDB is kept up-to-date following changes
 implemented by new releases, and that the contents
 of those releases are stored in the DSL."

Emphasis on 'testing' and updating the CMDB (Change
Management Data Base) forllowing 'changes' implemented
by 'new releases' and we're again saying 'improve upon'

With all this emphasis on improving the product, it is
evident that there is no intention of waiting for a 
perfected product prior to releasing it, and that the
quality of the initial releases is, by definition less
than what they're working toward.

I found yet another instance of "controlled release"
used in reference to an 'alpha' version of software,
which is even more experimental than a beta version,
here, on a cached page for a jlabs.com press release:

* An alpha version of WebShield is available for
 trial now (JLabs web-site will soon include
 information on the controlled release of the product
 and list download locations)
* Beta version available for SPARC systems end
 November, and for Windows/NT early in December
* Final release of the product in January 1997 
http://216.239.53.100/search?q=cache:WriHt875-GcC:www.jlabs.com/html/newsflash_press_release_2.html+defined+%22controlled+release%22+software&hl=en&ie=UTF-8

In this case, 'controlled release' is being used
to describe the release of a pre-beta version
of the software!

In short, it seems clear that we are not dealing with
a strictly-defined term, with a uniform meaning which
is independent of context, anymore than 'controlled
descent' means the same thing when talking about a 
parachute, a plane, a bird, or a skydiver.

Nonetheless, it seems equally clear that one of the
major functions of a 'controlled release' is simply
to buy time and space in which to 'improve' a product
before releasing it, in mass quantities, to the public.
It's akin to greenhousing a plant and working with the
genetics before planting a field of the crop.

I recognize and share your preference to locate an
actual 'definition' for the term, but further searches
came up empty:

Searches done, via Google:

baai...

The other search certainly limited the number of irrelevant
responses, however it only showed 8 of the 9 links I ended
up exploring. This is because Google automatically lists
the most relevant sites at the beginning of the search results,
so '+software' in the other search produced the same results
as 'software' in mine, and the -xxxx terms just removed
irrelevant sites which were already listed further down on
the list of results.

As for your comment:
"...only the Nortel site (the first one) actually states
something to the effect that the controlled release
product could require additional support (and therefore
it would seem that it must be of lesser quality like a
beta)."

I will summarize from the results I posted:

Coredge:
"We also anticipate that this group will provide
 us with valuable feedback on the product to help
 further hone the product to address the needs of
 its users"
(hone = 'improve upon')

ViaDyne:
"Error reduction through the controlled Release of 
 hardware and software to the live environment.."
(error reduction = 'improve upon')

And did you read the page from ViaDyne, which I 
highlighted as a complete discourse on Release
Management? I can't duplicate the entire page
here, but the 'Scope' is as follows:
---------------------------------------------------
Scope:
 Release Management undertakes the planning, design,
 build, configuration and testing of hardware and
 software to create a set of Release components for
 a live environment. Activities also cover the
 planning, preparation and scheduling of a release
 to many customers and locations. Release Management
 is heavily dependant of Change Management and
 Configuration Management to ensure that the shared
 CMDB is kept up-to-date following changes
 implemented by new releases, and that the contents
 of those releases are stored in the DSL."

Emphasis on 'testing' and updating the CMDB (Change
Management Data Base) forllowing 'changes' implemented
by 'new releases' and we're again saying 'improve upon'

With all this emphasis on improving the product, it is
evident that there is no intention of waiting for a 
perfected product prior to releasing it, and that the
quality of the initial releases is, by definition less
than what they're working toward, though the relative
quality of initial releases may vary considerably.

I found yet another instance of "controlled release"
used in reference to an 'alpha' version of software,
which is even more experimental than a beta version,
here, on a cached page for a jlabs.com press release:

* An alpha version of WebShield is available for
 trial now (JLabs web-site will soon include
 information on the controlled release of the product
 and list download locations)
* Beta version available for SPARC systems end
 November, and for Windows/NT early in December
* Final release of the product in January 1997 
http://216.239.53.100/search?q=cache:WriHt875-GcC:www.jlabs.com/html/newsflash_press_release_2.html+defined+%22controlled+release%22+software&hl=en&ie=UTF-8

In this case, 'controlled release' is being used
to describe the release of a pre-beta version
of the software!

In short, it seems clear that we are not dealing with
a strictly-defined term, with a uniform meaning which
is independent of context, anymore than 'controlled
descent' means the same thing when talking about a 
parachute, a plane, a bird, scubadiver or skydiver.
Just because all but the scubadiver share the same
'medium', in no way solidifies the definition.

Nonetheless, it seems equally clear that one of the
major functions of a 'controlled release' is simply
to buy time and space in which to 'improve' a product
before releasing it, in mass quantities, to the public.
It's akin to greenhousing a plant and working with the
genetics before planting a field of the crop.

I recognize and share your preference to locate an
actual 'definition' for the term, but further searches
came up empty:

Searches done, via Google:

baai...

The other search certainly limited the number of irrelevant
responses, however it only showed 8 of the 9 links I ended
up exploring. This is because Google automatically lists
the most relevant sites at the beginning of the search results,
so '+software' in the other search produced the same results
as 'software' in mine, and the -xxxx terms just removed
irrelevant sites which were already listed further down on
the list of results.

As for your comment:
"...only the Nortel site (the first one) actually states
something to the effect that the controlled release
product could require additional support (and therefore
it would seem that it must be of lesser quality like a
beta)."

I will summarize from the results I posted:

Coredge:
"We also anticipate that 
 this group will provide us with valuable feedback on 
 the product to help further hone the product to 
 address the needs of its users"
(hone = 'improve upon')

ViaDyne:
"Error reduction through the controlled Release of 
 hardware and software to the live environment.."
(error reduction = 'improve upon')

And did you read the page from ViaDyne, which I 
highlighted as a complete discourse on Release
Management? I can't duplicate the entire page
here, but the 'Scope' is as follows:
---------------------------------------------------
Scope:
 Release Management undertakes the planning, design,
 build, configuration and testing of hardware and
 software to create a set of Release components for
 a live environment. Activities also cover the
 planning, preparation and scheduling of a release
 to many customers and locations. Release Management
 is heavily dependant of Change Management and
 Configuration Management to ensure that the shared
 CMDB is kept up-to-date following changes
 implemented by new releases, and that the contents
 of those releases are stored in the DSL."

Emphasis on 'testing' and updating the CMDB (Change
Management Data Base) forllowing 'changes' implemented
by 'new releases' and we're again saying 'improve upon'

With all this emphasis on improving the product, it is
evident that there is no intention of waiting for a 
perfected product prior to releasing it, and that the
quality of the initial releases is, by definition less
than what they're working toward.

I found yet another instance of "controlled release"
used in reference to an 'alpha' version of software,
which is even more experimental than a beta version,
here, on a cached page for a jlabs.com press release:

* An alpha version of WebShield is available for
 trial now (JLabs web-site will soon include
 information on the controlled release of the product
 and list download locations)
* Beta version available for SPARC systems end
 November, and for Windows/NT early in December
* Final release of the product in January 1997 
http://216.239.53.100/search?q=cache:WriHt875-GcC:www.jlabs.com/html/newsflash_press_release_2.html+defined+%22controlled+release%22+software&hl=en&ie=UTF-8

In this case, 'controlled release' is being used
to describe the release of a pre-beta version
of the software!

In short, it seems clear that we are not dealing with
a strictly-defined term, with a uniform meaning which
is independent of context, anymore than 'controlled
descent' means the same thing when talking about a 
parachute, a plane, a bird, or a skydiver.

Nonetheless, it seems equally clear that one of the
major functions of a 'controlled release' is simply
to buy time and space in which to 'improve' a product
before releasing it, in mass quantities, to the public.
It's akin to greenhousing a plant and working with the
genetics before planting a field of the crop.

I recognize and share your preference to locate an
actual 'definition' for the term, but further searches
came up empty:

Searches done, via Google:

baai...

The other search certainly limited the number of irrelevant
responses, however it only showed 8 of the 9 links I ended
up exploring. This is because Google automatically lists
the most relevant sites at the beginning of the search results,
so '+software' in the other search produced the same results
as 'software' in mine, and the -xxxx terms just removed
irrelevant sites which were already listed further down on
the list of results.

As for your comment:
"...only the Nortel site (the first one) actually states
something to the effect that the controlled release
product could require additional support (and therefore
it would seem that it must be of lesser quality like a
beta)."

I will summarize from the results I posted:

Coredge:
"We also anticipate that 
 this group will provide us with valuable feedback on 
 the product to help further hone the product to 
 address the needs of its users"
(hone = 'improve upon')

ViaDyne:
"Error reduction through the controlled Release of 
 hardware and software to the live environment.."
(error reduction = 'improve upon')

And did you read the page from ViaDyne, which I 
highlighted as a complete discourse on Release
Management? I can't duplicate the entire page
here, but the 'Scope' is as follows:
---------------------------------------------------
Scope:
 Release Management undertakes the planning, design,
 build, configuration and testing of hardware and
 software to create a set of Release components for
 a live environment. Activities also cover the
 planning, preparation and scheduling of a release
 to many customers and locations. Release Management
 is heavily dependant of Change Management and
 Configuration Management to ensure that the shared
 CMDB is kept up-to-date following changes
 implemented by new releases, and that the contents
 of those releases are stored in the DSL."

Emphasis on 'testing' and updating the CMDB (Change
Management Data Base) forllowing 'changes' implemented
by 'new releases' and we're again saying 'improve upon'

With all this emphasis on improving the product, it is
evident that there is no intention of waiting for a 
perfected product prior to releasing it, and that the
quality of the initial releases is, by definition less
than what they're working toward.

I found yet another instance of "controlled release"
used in reference to an 'alpha' version of software,
which is even more experimental than a beta version,
here, on a cached page for a jlabs.com press release:

* An alpha version of WebShield is available for
 trial now (JLabs web-site will soon include
 information on the controlled release of the product
 and list download locations)
* Beta version available for SPARC systems end
 November, and for Windows/NT early in December
* Final release of the product in January 1997 
http://216.239.53.100/search?q=cache:WriHt875-GcC:www.jlabs.com/html/newsflash_press_release_2.html+defined+%22controlled+release%22+software&hl=en&ie=UTF-8

In this case, 'controlled release' is being used
to describe the release of a pre-beta version
of the software!

In short, it seems clear that we are not dealing with
a strictly-defined term, with a uniform meaning which
is independent of context, anymore than 'controlled
descent' means the same thing when talking about a 
parachute, a plane, a bird, or a skydiver.

Nonetheless, it seems equally clear that one of the
major functions of a 'controlled release' is simply
to buy time and space in which to 'improve' a product
before releasing it, in mass quantities, to the public.
It's akin to greenhousing a plant and working with the
genetics before planting a field of the crop.

I recognize and share your preference to locate an
actual 'definition' for the term, but further searches
came up empty, so we seem to be stuck with context,
which, I think, we've covered. Additionally, I'm
willing to bet that if you asked various software
development companies/teams, you'd come up with
varying definitions, dependent on how the term is
used in their company.

Searches done, via Google:

defined "controlled release" software
://www.google.com/search?num=50&hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&q=defined+%22controlled+release%22+software

"controlled release defined" software
://www.google.com/search?num=50&hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&q=%22controlled+release+defined%22+software

"definition of controlled release" software
://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=%22definition+of+controlled+release%22+software

Please don't hesitate to request another clarification
if there's any possible way to improve this answer.

sublime1-ga

---

Clarification of Answer by sublime1-ga on 16 Dec 2002 23:22 PST

baai...

Forgive the accidental quadruple post!
I'm still trying to figure that one out.
I even noticed that this was somehow 
occurring in the post window, and cut 
and pasted it into notepad, then removing
the duplicates. Somehow, when I pasted it
back into the clarification box, it 
again multiplied like rabbits...very strange..

sublime1-ga

Hi baai,

Did some searching at online tech-specific dictionaries/glossaries,
and "controlled release" is not in any of them. This may be because
these dictionaries are not updated often, but may equally reflect the
fact that "controlled release" is more of a colloquial term. Hopefully
another researcher can prove me wrong. For reference, here are a few
related definitions that may be of assistance:

http://wombat.doc.ic.ac.uk/foldoc/foldoc.cgi?query=release

Best,
Rippo