bzr-explorer-dev team mailing list archive

[Ian Clatworthy <ian.clatworthy@xxxxxxxxxxxxxxxx>]

Hi all,

We aren't far off bzr 2.0 now so I'm going to think seriously about what
timeframe makes the most sense for calling something Bazaar Explorer
1.0. There are still some important things I want to land scope-wise,
e.g. an import wizard/dialog [1], but my gut feel is that qbzr may end
up being the bottleneck. Do others feel the same?

Don't get me wrong: qbzr is progressing in leaps and bounds. On the
positive side, I hope explorer usage has helped increase the testing of
what if offers. On the negative side though, explorer also tends to
highlight what qbzr is missing still. Javier has plugged quite a few of
those gaps in recent weeks (e.g. qsend) but some of his work still needs
review IIUIC. If anyone has time to help with that this week, please do!

So after Javier's stuff is reviewed, tweaked and landed, what's still
missing in qbzr that explorer needs? I believe the list is something
like this:

* quncommit
* qshelve
* qunshelve
* qplugins
* qcustom (or whatever name we talked about - I forget right now)

Of those, I suspect the top one is "mandatory", the next 3 could easily
come later, and the last one falls into both camps. :-)

If others agree, is there *any* chance someone could volunteer to take a
crack at quncommit real soon now? Even a *really* simple version would
be better than nothing I suspect.

Ian C.

[1] 10 days ago, I did have plans for coding that on the weekend just
gone but life ended up being more complex than I hoped.