Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] MPC not opening with space in install path - requesting respin

Hi Ed,

Thanks for those very valuable additions to the discussion.

On Sat, Jun 30, 2018 at 11:07 AM, Ed Merks <ed.merks@xxxxxxxxx> wrote:
Probably the worst case would be if the user's home folder name has spaces "C:\Users\john doe", but I suppose that in (almost?) all cases the user could choose to install to a location without spaces and in all cases the user can update MPC from a specific URL.}
In any case, the combination of "I install to a disk location with spaces"  (which is generally always a bad idea because something is bound not to work properly because it's not been tested) with "I actually use MPC" is probably relatively small, but who knows.

Several users were hit by this on the hours after the release and reported the bug. Although it does affect only a minority of users, it's still a critical issue IMO and we shouldn't try to minimize it in this discussion.
Maybe the conclusion will just be "we acknowledge that it's critical but didn't want to release the fix off-process" or maybe it'll be "let's do a respin", but the issue remains critical in both cases.

Given we are no longer in the business of providing update releases, to me it's a slippery slope to me if we start respinning releases to publish multiple releases.  My knee jerk reaction is to vote -1 on a respin.

That's a very valid point. And I agree we shouldn't have a "respin" but...

Certainly the decision of whether we will do respins affects the decision of whether for the September release can be a simple repository because there can/will never be updates versus whether it should be a composite to accommodate arbitrary/possible respins.

... what about publishing a respin labelled as 2018-07 ?

In the end, I think there are other approaches than a respin that would help minimize (and in many case eliminate) the problem.

What do you think is the main point that would make a re-build of SimRel with newer MPC worse than adding a composite or similar things?
Is this a process issue, or a technical pain point? It would be interesting to make SimRel build/respin/release so trivial that we shouldn't even have to think about alternatives for such cases.


Back to the top