Hi Sameera,
When I retire, I will consider it a promotion :)
My recommendation is to promote from Production into Retirement.a cleaner
path from an analytics perspective when determining 'How many apps moved from
production into retirement'.
Demoting out of retirement should take
Hi,
From a user's perspective an application goes into retirement at the end of
the lifecycle.
What we need to very, is, whether the current configurable life cycle stage
in AF can handle both pre-production and post-production scenarios in ALM
in general.
Maybe in this case the word demote is
I think that makes sense in the current scope as it does not include
governance in production environment.
I'm thinking ahead to when that is integrated, in which case retiring
needs to be an explicit action. Since, there's no direct equivalent in v1,
we'll be free to design that behavior at that
Hi Shiro, Dimuthu,
I was going through the AF Introduction slides [1] and have a question
related the Governance user story.
Slide 17 of the presentation says that life cycle stages are configurable
through GReg. Is this still valid? Slide 2 does say we may drop features
along the way.
In case
Couldn't actually find why it was made red as yet, but, it seems that many
people don't quite like it being red, [1].
[1] https://www.google.lk/search?q=gmail%20compose%20button%20red
Thanks,
Senaka.
On Mon, Jun 3, 2013 at 4:13 AM, Senaka Fernando sen...@wso2.com wrote:
Had a look into
Hi all,
If we are arguing about build and repositories page we are arguing about a
none-existence case. The attached wireframes shows as if there is a build
for each and every version - which is not the case. We can build only the
ones in development phase.
But if we are unhappy about the
On Fri, May 31, 2013 at 1:54 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi,
Gmail's compose button is red. :)
Do we know why?
Also note that, send button is Blue.
thanks,
dimuthu
On Fri, May 31, 2013 at 12:48 PM, Senaka Fernando sen...@wso2.com wrote:
Hi all,
Sorry couldn't
Hi all,
Sorry couldn't keep up with this thread. If there aren't gone to be that
many buttons in red, and if we have other higher priorities we can leave
this at it. But, I need to point out that a shade of red does give that
sense. For example, if you take a look at Google UIs (Gmail, Docs,
I feel that red is overdone on Builds and Repositories--we can show the
red buttons only when mouse hovers a particular row. Also, using the color
red for all the buttons gives a feeling that all of them share the same
priority. Red is best suited for Call-to-action buttons and the rest can be
+1
The page lists multiple versions and multiple possible actions: there's no
single, primary goal/task of this page. Information the given on the page
have almost equal importance as the actions; so the buttons shouldn't grab
all the attention by being in primary colors.
On Fri, May 31, 2013 at
Hi Shiroshica,
Any reason for using red coloured buttons in build/governance UIs? IMHO,
that sounds like something went wrong and some immediate action is needed.
Seeing a lot of red coloured buttons in the build UI gives the feeling that
a lot of things has gone wrong in the past.
Can this be
Hi Senaka,
On Wed, May 29, 2013 at 10:25 PM, Senaka Fernando sen...@wso2.com wrote:
Hi Shiroshica,
Any reason for using red coloured buttons in build/governance UIs? IMHO,
that sounds like something went wrong and some immediate action is needed.
Seeing a lot of red coloured buttons in the
Hi,
I had forgotten about the buttons being disabled / enabled based on
permissions - so we will not see all these buttons at once.
Given that we were adviced to keep the red in other areas to indicate
primary buttons and that we are in critical path to get the pages ASAP
there will be no
13 matches
Mail list logo
