On 12/6/2012 23:11, Shenfeng Liu wrote:
Hi, all,
I suggest we update the planning items in 4.0 wiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning
I just updated the status of each items and added some more according to
my reading of the mails.
I hope every one can help to review the list and:
(1) input your name if you volunteer to any of the items (especially those
without owner now);
(2) for those in "Proposed" status, update the wiki or reply to this mail,
confirming if you still think you can/will deliver it in 4.0, or if you
prefer to move it to future releases, or think it is no longer important or
valid.
(3) add new items that you are working on or you plan to deliver in 4.0.
Then by the end of next week, I propose to move out those with no
volunteer (I intent to move most of those items to 4.1 planning wiki
temporary), then update the rest according to the response from volunteers.
Please tell me if any comments/suggestion. And very appreciate for the
update!
Thanks!
- Shenfeng (Simon)
The "Encryption GUI" item has not attracted a sponsor. I added this per
the resolution of a very long discussion in BZ [1]. Subsequently, Jürgen
wrote an extension to set "SHA256" mode, and I wrote a macro[2] to
toggle the settings; both are still available. (I have no idea whether
any or many users have used them.)
[1] <https://issues.apache.org/ooo/show_bug.cgi?id=119090#c31>
[2] <http://wiki.openoffice.org/wiki/User:TJFrazier/Encryption>
(this page includes text suitable for release notes)
If somebody wants to pick up on this, and implement a GUI (probably in
Tools > Options, possibly on the Save and Save As dialogs), that's
wonderful. Lacking all fu for SVN and C++, I can't volunteer for this.
If we let the GUI slide, and keep the status quo, then I have a couple
of suggestions:
1) I will try to enhance the macro to change the active settings.
Currently, it changes the values in rm.xcu, which do not take effect
until the suite is restarted (not very convenient, but much better than
having to edit the parameter file by hand). I have failed at this before
(the documentation has problems), but I will try again.
2) Add the macro to the Basic Tools library, possibly in its own module.
I can supply a .txt or .bas file, or it can simply be scraped off the
wiki page. This is the easiest way I know to distribute a macro whose
lifetime should be that of the version; easy to add, easy to refer to in
the notes, and easy for users to get at. If I can't update the macro by
code-cutoff time, we can go with what we have.
/tj/
