[orca-list] Some technical questions for new branches development rule related

[Hammer Attila <hammera pickup hu>]

Hy Joanie,

I have got some technical questions for development rule related:
I prewious used master branch when I working development patches or new 
features the orca 3.1.2pre development version, because I using gnome 
2.x based systems my work.
When future I need writing a code, general what branch need the base branch?

For example, now I working an Orca contracted braille related feature, 
and working presenting mnemonics informations for braille display 
feature. Following bugreport attachments will be not compatible I think 
the latest this day master branch, see below the estimated list.

Already done the clipboard text presenting function, and some other 
oldest patches with now will be possible not compatible the actual 
master branch.
Clipboard related function link with possible will be compatible the 
latest master branch:
https://bugzilla.gnome.org/show_bug.cgi?id=648730

Possible need future editing patches to provide compatibility with 
latest this day master branch, if you accept this fixes:
1. Need do a setting with toggle always Orca spokening the group label 
of controls, for example the Enable progressbar updates check box:
https://bugzilla.gnome.org/show_bug.cgi?id=607206

2. Between accelerator modifyer and letters need a word with separate 
this informations:
https://bugzilla.gnome.org/show_bug.cgi?id=640795

3. If Orca preferences dialog enabled the contracted braille feature, 
not possible choosing Orca present uncontracted form the cursor selected 
word or not:
https://bugzilla.gnome.org/show_bug.cgi?id=651206

4. Need presenting the mnemonic informations with braille display, 
similar with speech speak object under mnemonics feature for Orca:
https://bugzilla.gnome.org/show_bug.cgi?id=651839

Future, when I go to home my holiday after with jul 4th, when final 
committed the already listed doed possible incompatible patches with 
latest this day master branch, I very would like doing presenting 
position index values for braille display, similar with speak child 
position feature. We trawelling next week tuesday.
Before this work critical important to finalize I already doed braille 
related patches to I possible right place putting the future position 
index related check box with src/orca/orca-setup.ui file.
I would like doing some braille related GUI setting possibility with now 
only possible editing hand, I doed a collected list for orca-list, but 
this is depending users answers.

So, future what method better you and easyest your work:
1. I need installing a gnome 3.0 distribution and using for example 
fallback mode, and developing the codes with actual master branch.
2. I need using the 2.x orca-xdesktop branch when developing a feature? 
This is simplest me because my working system is full stable, but I 
think not simplest your work.

Other question:
What will be happening if a feature need both gnome-3.2 development 
master branch and orca-xdesktop branch? For example the contracted 
braille related feature and perhaps the braille mnemonics related 
feature is typical this purpose importanter function, or other 
importanter braille related functions with future (position index 
presenting, some new braille gui settings, etc).
This situation need developing two style patch, because for example 
src/orca/settings.py file is different the two branches?
I full agree and understand why need this two differend branch, this is 
good for users with not have access gnome-3.0, only I would like seeing 
clear for technical related rules when developing a new feature. :-):-)

Attila