Am 19.10.2026 um 21:41 schrieb [email protected]:
Am 19.10.2026 um 21:11 schrieb Jim Jagielski:
The search named 5.0.0 OpenIssues does not exist.
I've got a smashing idea... let's pick a method that works for
_everyone_... you know, let's work as a _team_ and _compromise_ and
universally agree to a method.
Are you saying that you are not able to handle Bugzilla?
I am sorry. I overstepped here.
I do try to get everyone into the same boat. I have prepared the list,
and wrote about the work to.
And it feels offending to me if you imply that I do not try to work
together. I snatched here.
I would like to ask you to assume that we all want to work together and
consider a counter proposal when one is offered. Even if it is not done
in the best way.
Thanks.
All the best
Peter
All you need to do is to set up a search to filter on target milestone
5.0.0
It should return 37 issues.
In the meantime i figure out how to share search lists.
On Oct 19, 2026, at 3:05 PM, [email protected] wrote:
Am 19.10.2026 um 18:56 schrieb Jim Jagielski:
Can we maybe use this wiki page to coordinate work on AOO5:
https://s.apache.org/AOO5-TODO
I dont like to maintain a confluence page.
https://bz.apache.org/ooo/buglist.cgi?cmdtype=runnamed&list_id=253306&namedcmd=5.0.0%20OpenIssues
Not sure if the list can be seen by others, but this is my reference
list. There is a list for 4.2.0 in confluence with almost same
issues open.
TIA
On Oct 19, 2026, at 7:08 AM, Jim Jagielski <[email protected]> wrote:
Thanks for the Email! Your timing is perfect.
Right now, the main effort is working on getting `trunk`, and
specifically the `AOO50X` branch to a relative stable place where
we could do a Developer's Release; let's work on stuff that has an
immediate positive impact and gets us closer to a release. So
things like checking if AOO50X builds for you, if it works and
where it doesn't. Things like that.
Sure, it would be great to rip-out our current build structure for
something "modern", for example, but focusing on that improves
where are _are_ and doesn't move us forward, if you get my
meaning. It's a lot of work that ends up with us being at the
exact spot where we are now. In fact, it actually means we step
back because now this whole new build system needs a lot more
testing before we can ensure parity with what we already have. I
am simply using the build system as a convenient example, nothing
more, btw.
AOO50X uses a newer version of C++ and baselines Python 3, so
those are other good things to check.
On Oct 19, 2026, at 6:00 AM, Gaurav <[email protected]> wrote:
Hi everyone,
I'm Gaurav, a master's student in Applied Data Science at USC (Los
Angeles). I work primarily in C++ and Python, and I'd like to
volunteer
with OpenOffice.
To start, I'm happy to help with bug reproduction and triage, or
small C++
bug fixes — whatever is most useful. I've gone through the New
Volunteer
Orientation modules [only say this if you actually do].
Could someone point me to where help is most needed right now, or
a good
first bug to look at?
Thanks,
Gaurav Nagalapuram Venkataramanan
--
Jim
"This is an outrage!"
Tony Harrison
--
Jim
"This is an outrage!"
Tony Harrison
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail: [email protected]
<mailto:[email protected]>
--
Jim
"This is an outrage!"
Tony Harrison
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
