Let's talk about rationales before votes ok?  I figure we're all on
the same page:  that since Save implies Review, the goal is to
integrate those two activities together on the Save dialog.  Are we
good so far?

Monticello-bf.540 addresses it very nicely except for the fact that
Review implies Fix.  When the actor arrives at Fix he's stuck, and the
original goal of Save+Review integration has been subverted.  Save,
once again, at this point must be a very separate, and now ungraceful
act, given what the actor is put through to simply save the contents
of the reviewed-and-fixed package as we can today.

Maybe I'm missing another use-case that describes what you want to do,
and if so maybe it should be a preference or a separate function with
its own button..?

On Fri, May 3, 2013 at 5:12 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>
> On 2013-05-02, at 20:49, Frank Shearar <frank.shearar at gmail.com> wrote:
>
>> On 2 May 2013 19:19, Chris Muller <asqueaker at gmail.com> wrote:
>>> Hmph -- since you were asking for consensus on something, it would be
>>> nice to have a little more time to respond -- as I did in < 24 hours,
>>> but still apparently too late.
>>>
>>>
>>> didn't get much discussion.  ay we please have more time
>>
>> Sure. In my defence, this was seriously getting in my way... but I
>> guess the response to that is "well keep the change in your image".
>> Ah, well.
>>
>> frank
>
>
> Maybe you should try my "allow partial commits" Monticello mod (Monticello-bf.540 in inbox). I have been using it for months now and it works really well. Back in January I got a few +1s but Chris was opposed so I did not put it into trunk, yet. I have not found the time to add the "do yet another snapshot when pressing save" Chris wanted because in my workflow it's not needed. But perhaps it's good enough? For me it certainly was a relief keeping some changes to my image while still being able to commit "clean" packages to trunk.
>
> - Bert -
>
>
>