Explorer 0.10.0 release plans - call for testing and translations

[A. S. Budden]

2009/12/11 Alexander Belchenko <bialix at ukr.net>:
> A. S. Budden пишет:
>>
>> 2009/12/11 Ian Clatworthy <ian.clatworthy at canonical.com>:
>>>>
>>>> Do you think there's any chance that
>>>> this merge request...
>>>>
>>>>
>>>>  https://code.launchpad.net/~abudden/bzr-explorer/remote-feature-branches/+merge/15487
>>>>
>>>> might land before 0.10.0?  It's been there for a while now, but I've
>>>> had no feedback at all.
>>>
>>> Sorry about that. It's been a rough week personally and I've been
>>> scrambling to wrap some other stuff up before heading off on leave.
>>>
>>> In a nutshell, 'easier initialization' didn't make the 0.10.0 cut. :-( I
>>> need some more time to think through the various options including your
>>> proposal (which looks fine conceptually).
>>
>> Ah well, that's a shame... I guess we'll have to apply the remote
>> feature branch patch manually on every install: I doubt there'll be a
>> new Windows installer with remote feature branches ready by the 7th
>> January!
>
> According to roadmap there should be rc1 release at 6 January:
> https://launchpad.net/bzr/2.1

Cool: I guess anything's possible then!  I'll keep my fingers crossed...

> There is better way for you anyway: push your branch to LP, merge into it
> latest trunk and then get copy on all machines at your work.

I've merged the latest trunk into the launchpad version with the
current merge proposal and am happy to say that it seemed to go in
very cleanly.  I guess I was just hoping that all the people who will
be installing Bazaar would be able to just install Bazaar rather than
installing Bazaar and then getting a different Bazaar Explorer
version.  My concern would then be that the current merge proposal
would be rejected and I'd have to actively monitor changes to the
initialisation dialog: they could require me to rewrite my patch so
that all the Bazaar users in the department could keep their
initialisation method.  I guess in the short term I could try to
figure out how to write an installer that applies the patch to the
Bazaar Explorer installation.  Then at least they wouldn't have to
learn to use Bazaar before getting it completely installed!

It may be easier in the long term to just show them the current, slow
way of creating a new project:

    initialise "feature branches" on the network drive
    figure out how to reconfigure the repository for no working trees;
    close the automatically opened branch
    go back to the main page
    check out the project locally using the QBzr dialog rather than
the Bazaar Explorer one
    open the working tree
    bookmark it

rather than the "remote feature branches" way:

    initialise "remote feature branches"
    bookmark the automatically opened working tree

I guess it's not something they'll do often, so with good
documentation and lots of screenshots it shouldn't be TOO bad.

As an unrelated aside, I was wondering about writing a patch to the
Bazaar Explorer checkout dialog to add an additional option to allow
heavyweight or lightweight checkouts (as we generally use the
heavyweight ones).  I realise that this could be considered to add
'clutter' to the dialog, so before I write it I was wondering: would
you have any objection to this?

Thanks again,

Al

-- 
http://sites.google.com/site/abudden