From: [email protected] [mailto:[email protected]] On Behalf Of Michal Mocny Sent: Tuesday, October 07, 2014 11:25 AM To: Treggiari, Leo Cc: Michal Mocny; Marcel Kinard; dev Subject: Re: Independent platform release summary
> I don't think its a goal for us developers, but I understand that it has been > a goal for end users (resistance to change, averse to risk, been bitten with > bad upgrades in the past..) To me it is more about how much risk I want to take on at this point in time. For example, I may be fine with updating to latest and greatest at the beginning of a major release of my app. However, when I doing final testing, coming up on a deadline, I want minimal changes. Leo On Tue, Oct 7, 2014 at 2:20 PM, Treggiari, Leo <[email protected]<mailto:[email protected]>> wrote: > - enable users to easily obtain the latest-and-greatest > - clearly communicate to users what they have, so they can easily > understand how what they currently have differs from the latest-and-greatest I think there is another user goal, which may not be so easy to achieve. That is, the ability to easily understand how to take the Cordova release that I have, and do a selective update to get fixes that I need. I.e. I don't want the "latest and greatest", I want the minimal change that fixes the problems I have to fix. Does that have to be a goal? I don't think its a goal for us developers, but I understand that it has been a goal for end users (resistance to change, averse to risk, been bitten with bad upgrades in the past..) but I believe the way to strive to solve that is to simplify upgrades, not make it easier to ignore them. Leo -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Michal Mocny Sent: Tuesday, October 07, 2014 11:14 AM To: Marcel Kinard Cc: dev Subject: Re: Independent platform release summary Marcel, I added the goal for "latest-and-greatest" which is a good idea. I think your other goals are already covered with what's there. Again, I wanted to be brief. "Do not confuse developers" goal hopefully covers your points about communication and information (and going into detail is imposing specific strategies to reach that goal). -Michal On Tue, Oct 7, 2014 at 2:09 PM, Marcel Kinard <[email protected]<mailto:[email protected]>> wrote: > Yes, creating a doc is a great next step to solving this. Thanks for doing > that. > > Now that there is a doc to read, I think the goals are wrong. I suggest > the following: > > - enable releases to happen at a faster pace and lower cost > - enable users to easily obtain the latest-and-greatest > - clearly communicate to users what they have, so they can easily > understand how what they currently have differs from the latest-and-greatest > - (keep the hypotheticals as-is, since they make helpful specific stories) > > If folks agree, I can make that change in the doc. > > If we don't start with the right goals, then the rest of the conversation > is moot. > > On Oct 7, 2014, at 11:51 AM, Michal Mocny > <[email protected]<mailto:[email protected]>> wrote: > > > Created a doc to summarize. Trying to keep it concise and free of > > opinions/conclusions, only context & goals. > > > > > https://docs.google.com/document/d/1VqAVo2AA5vZ7LRmq_9jJ6oa7Nyr2OrjLCfEkBhO-X8U/edit?usp=sharing > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [email protected]<mailto:[email protected]> > For additional commands, e-mail: > [email protected]<mailto:[email protected]> > >
