[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev][prov] Staged update
|
We also have a "sizing phase"
for computing the install size, which the UI decouples from the other phases
when a preview is shown to the user prior to downloading. There will likely
be other cases as the number of phases grows.
I definitely don't suggest such terminology
be exposed to end users. These kinds of options can likely be posed to
the user as simple questions or radio button options - Download updates
automatically (yes/no), Install updates automatically (yes/no), etc.
Jeff McAffer/Ottawa/IBM@IBMCA
Sent by: equinox-dev-bounces@xxxxxxxxxxx
10/14/2007 11:08 AM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
To
| Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [equinox-dev][prov] Staged update |
|
That has nice feel at least for the general category of technical discussions.
It may be a too general though to capture just the particular case
of decoupling downloading and install/configure. Do you see other
instances of split phase scenarios?
Seems like there is a bit of a struggle between end-user terminology and
design/implementation ideas. Things like "split phase"
may be a too technical for end-user terminology ("phase" is unlikely
to be exposed). We'll probably have to look at that later in a larger
context.
Jeff
John Arthorne/Ottawa/IBM@IBMCA
Sent by: equinox-dev-bounces@xxxxxxxxxxx
10/12/2007 05:53 PM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
To
| Equinox development mailing
list <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [equinox-dev][prov] Staged update |
|
Another possibility is "split phase install" for the case of
separating the download from the configuration. This follows the engine
terminology - it's really splitting the phases into separate invocations
of the engine. That term would also capture any situation where the phases
are broken apart, rather than being specific to the separate download/configure
case.
Jeff McAffer/Ottawa/IBM@IBMCA
Sent by: equinox-dev-bounces@xxxxxxxxxxx
10/12/2007 04:05 PM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
To
| Equinox development mailing
list <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [equinox-dev][prov] Staged update |
|
Thanks for the clarification. Suggested terms
- deferred install or staged install
- sequenced install
I am not happy with the term following "deferred" or "sequenced".
People may read too much into it (e.g., does sequenced updating sequence
installs too?). perhaps * "operation".
Jeff
Pascal Rapicault/Ottawa/IBM@IBMCA
Sent by: equinox-dev-bounces@xxxxxxxxxxx
10/12/2007 08:48 AM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
To
| Equinox development mailing
list <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [equinox-dev][prov] Staged update |
|
For context the item that Jim initially quoted came out of the questions
section of the wiki (http://wiki.eclipse.org/Equinox_p2_Plan). This section
list questions that we need to answer by the end of M3 to decide what we
deliver in 3.4 will look like. The download before the installation is
not
on this list because it is already decided that we will be doing it and
the
API work to allow that has been done as part of the refactoring of the
IDirector that got committed yesterday by Susan. I think I call that "eager
download".
To avoid further confusion which terms do you think we should use for each
of these?
My proposal: "eager download" to refer to download before installation
and
"staged updated" to refer to updates that must be happening.
Note that I'm not happy with any of these.
PaScaL
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Jeff McAffer/Ottawa/IBM@IBMCA
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|10/11/2007 06:38 PM
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [equinox-dev][prov] Staged update
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Interstingly I would have said that it referred to a decoupling between
the
downloading and installing of some IUs/artifacts. For example, you
might
push all the GBs of content to a few thousand machines over a couple weeks
and then trigger them to update all at once overnight or some such. Both
the scenario you outline and this one are important/interesting...
Jeff
James D Miles
<jdmiles@xxxxxxxxxx>
Sent by:
To
equinox-dev-bounces@eclipse. Equinox
development mailing list
org
<equinox-dev@xxxxxxxxxxx>
cc
Equinox development
mailing list
10/11/2007 11:15 PM
<equinox-dev@xxxxxxxxxxx>,
equinox-dev-bounces@xxxxxxxxxxx
Subject
Please respond to
Re: [equinox-dev][prov] Staged
Equinox development mailing update
list
<equinox-dev@xxxxxxxxxxx>
That is an important capability, We have had cases where it would have
been
helpful.
The easiest example is a bug in the director that would prevent a full
update without a fix.
(Embedded image moved to file: pic25903.gif)Inactive hide details for
Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>Pascal Rapicault
<Pascal_Rapicault@xxxxxxxxxx>
Pascal Rapicault
<Pascal_Rapicault@xxxxxxxxxx>
Sent by:
equinox-dev-bounces@xxxxxxxxxxx (Embedded image moved to file:
pic08939.gif)
10/11/2007 03:25 PM
To
(Embedded image moved to
file: pic04553.gif)
Please respond to
Equinox development mailing
Equinox development mailing list list
<equinox-dev@xxxxxxxxxxx>
<equinox-dev@xxxxxxxxxxx>
(Embedded image moved to file:
pic03405.gif)
cc
(Embedded image moved to
file: pic08336.gif)
(Embedded image moved to file:
pic21878.gif)
Subject
(Embedded image moved to
file: pic15030.gif)
Re: [equinox-dev][prov]
Staged update
(Embedded image moved to file:
pic23113.gif)
(Embedded
image moved to file:
pic08760.gif)
It refers to installing/using specific updates prior to other updates.
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|James D Miles <jdmiles@xxxxxxxxxx>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|equinox-dev@xxxxxxxxxxx
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|10/11/2007 11:32 AM
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[equinox-dev][prov] Staged update
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
On the Equinox p2 plan page, under "Questions for M3", one item
is "Staged
update"
Does this refer to downloading prior to running or to installing/using
specific updates prior to other updates?
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
(Embedded image moved to file: pic06507.gif)
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Attachment:
pic25903.gif
Description: GIF image
Attachment:
pic08939.gif
Description: GIF image
Attachment:
pic04553.gif
Description: GIF image
Attachment:
pic03405.gif
Description: GIF image
Attachment:
pic08336.gif
Description: GIF image
Attachment:
pic21878.gif
Description: GIF image
Attachment:
pic15030.gif
Description: GIF image
Attachment:
pic23113.gif
Description: GIF image
Attachment:
pic08760.gif
Description: GIF image
Attachment:
pic06507.gif
Description: GIF image
