File: ROADMAP.txt

package info (click to toggle)
bzr-explorer 1.3.0-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, jessie, jessie-kfreebsd, sid, stretch
  • size: 6,696 kB
  • sloc: python: 21,837; xml: 277; makefile: 31
file content (95 lines) | stat: -rw-r--r-- 2,911 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
***********************
Bazaar Explorer Roadmap
***********************

1.0 - Q3/Q4 2009
****************

Bazaar Explorer is nearly feature complete for a 1.0 release!
It's true that development only started in Jun 2009 but, by design,
it's meant be a *lightweight shell* for accessing the meatier
functionality in the plugins it builds on: QBzr and bzr-gtk.

Note: A lot of development is still required to make the *overall*
user experience crisp-and-clean. Most of that though is further
development/polishing of QBzr and bzt-gtk. By putting the energy
into those, multiple environments win including Bazaar Explorer,
TortoiseBzr and our IDE integration add-ons.

A summary of planned changes for 1.0 is given below. Everything
listed is subject to change though based on user feedback, my
free time in coming months and the number of people who step up
to help. In other words, don't assume any particular change will be
in or out.


Required
--------

* Testing, testing, testing.


Highly desirable
----------------

* Online help including User Guide.

* Working Tree Browser

  * Allow simple filtering based on status: All, Versioned,
    Unversioned (with toggle of ignored items enabled when appropriate).

* Local Changes tab in the repository view should check the shelf (and
  optionally display it) so working trees with shelved changes aren't
  accidentally deleted.

* More state-aware "What's next?" suggestions. These will often be
  based on the workflow style being used by each project (so that
  arguably needs to be set in locations.py or something like that).

* When the workflow makes sense, the display for a branch or checkout
  should have 2 tabs/panels:

  * Working Tree Status - current view

  * Branch Changes - preview of overall patch (bzr status -rsubmit:..-1)

* Launchpad integration

  * lp icon in status bar if public branch on lp (click runs lp-open)


Nice to have
------------

* Hat-specific tools on the status-bar as a menu to make them more
  visible. Automatic switching of hats based on project or location.

* Less bugs:

  * Fix progress monitoring, e.g. add a cancel button to the
    widget showing progress in the status bar.

  * App name on OS X should be "Bazaar Explorer", not "Python".

* Help > Keyboard Shortcuts action

* Check qbzr (and bzr-gtk if present) for the mapping of logical
  commands to actual commands, instead of trying to keep explorer in
  lock-step with the last qbzr release. (This will make testing of
  new qbzr commands via explorer much easier too.)

* Custom application suite defined in ini files say: allows mixing and
  matching of the best of QBzr, bzr-gtk and locally written dialogs.

* Enhanced Preferences dialog

  * Toolbar tab

    * Actions to include/exclude

  * Bookmarks tab

    * Custom editor (for those who prefer an XML editor to a plain text one)

* File > Open Recent menu (last 10 locations say).