ardovm merged PR #11:
URL: https://github.com/apache/openoffice-project/pull/11
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
ardovm opened a new pull request, #11:
URL: https://github.com/apache/openoffice-project/pull/11
Proposal for blog post about our latest development on the trunk branch.
**Note**: The post is dated 2 April.
--
This is an automated message from the Apache Git Service.
To respond
Gavin McDonald wrote:
Hi Keith,
On Tue, Jan 16, 2024 at 5:32 PM Keith N. McKenna
wrote:
Marcus wrote:
I would like to move the other Wiki content into Confluence as
management is better there. However, it's may too much for my free time.
Even if you could move it, the mwiki would need to
Am 16.01.24 um 17:32 schrieb Keith N. McKenna:
Marcus wrote:
I would like to move the other Wiki content into Confluence as
management is better there. However, it's may too much for my free time.
Even if you could move it, the mwiki would need to stay active as it
does not appear that cwiki
Hi Keith,
On Tue, Jan 16, 2024 at 5:32 PM Keith N. McKenna
wrote:
> Marcus wrote:
> > I would like to move the other Wiki content into Confluence as
> > management is better there. However, it's may too much for my free time.
>
> Even if you could move it, the mwiki would need to stay active as
Marcus wrote:
I would like to move the other Wiki content into Confluence as
management is better there. However, it's may too much for my free time.
Even if you could move it, the mwiki would need to stay active as it
does not appear that cwiki has a file upload to use it to distribute or
Am 14.01.24 um 18:44 schrieb Damjan Jovanovic:
On Fri, Jan 12, 2024 at 7:23 PM Marcus wrote:
Am 12.01.24 um 19:19 schrieb Marcus:
Am 10.01.24 um 06:36 schrieb Damjan Jovanovic:
[...]
Can someone please create such a Wiki page, or give me access to do so?
[...]
that's a good idea. I'll
On Fri, Jan 12, 2024 at 7:23 PM Marcus wrote:
> Am 12.01.24 um 19:19 schrieb Marcus:
> > Am 10.01.24 um 06:36 schrieb Damjan Jovanovic:
> >> [...]
> >>
> >> Can someone please create such a Wiki page, or give me access to do so?
> >>
> >> [...]
> >
> > that's a good idea. I'll create a new page
Hi Marcus,
Am 12.01.24 um 20:23 schrieb Marcus:
Am 12.01.24 um 19:19 schrieb Marcus:
Am 10.01.24 um 06:36 schrieb Damjan Jovanovic:
[...]
Can someone please create such a Wiki page, or give me access to do so?
[...]
that's a good idea. I'll create a new page in our Confluence Wiki.
Am 12.01.24 um 19:19 schrieb Marcus:
Am 10.01.24 um 06:36 schrieb Damjan Jovanovic:
[...]
Can someone please create such a Wiki page, or give me access to do so?
[...]
that's a good idea. I'll create a new page in our Confluence Wiki.
please have look here:
Am 10.01.24 um 06:36 schrieb Damjan Jovanovic:
[...]
Can someone please create such a Wiki page, or give me access to do so?
[...]
that's a good idea. I'll create a new page in our Confluence Wiki.
Marcus
-
To
s From ODF 1.2"
items from all the 1.3 documents (there's several), and then to read over
them and mark off the ones that are irrelevant or complete, and track
progress on the other items where we do have some development to do on our
side.
Can someone please create such a Wiki page, or give me acces
e me with an
incredible opportunity to contribute to an open-source project and
collaborate with talented individuals who share a passion for software
development. I am excited to contribute my skills and knowledge to enhance
the OpenOffice website and make it even more user-friendly and functional.
and
collaborate with talented individuals who share a passion for software
development. I am excited to contribute my skills and knowledge to enhance
the OpenOffice website and make it even more user-friendly and functional.
I am confident that working with the OpenOffice developers community
https://openoffice.apache.org/mailing-lists.html
important for development is the dev mailing list you already
communicate with. if you have questions or ideas feel free to share.
btw. there is also a archive. check this mail from damjan:
https://lists.apache.org/list?dev
Hey thanks Peter I really appreciate it.
At the risk of showing my ignorance I will say that if you can provide a
link demonstrating what you mean by working with mailing list that would be
a help.
Other than that I'm comfortable with GitHub and doing actual coding, of
course.
I look forward to
Hi Chris,
this is the right email mailing list. Do you know how to work with
mailing lists?
best way to hand in your work is through GitHub [1]. you can submit your
work there for review.
our priority list [2]
how to build AOO [3]
if you have questions just ask away...
all the best
Hello!
I am trying to locate the correct email address to get involved in working
on Apache OpenOffice. I am trying to bring my C++ skills up to date and am
looking for volunteer opportunities to do so. This sounds like the perfect
way to do so!
I followed the link from this page:
Hi Jim,
Am 20.07.21 um 17:21 schrieb Jim Jagielski:
>
>> On Jul 19, 2021, at 10:26 AM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> People need macOS builds more frequently to test.
>>
> Agreed. But every time I seem to encourage a test macOS build, it seems that
> people want to hold off...
> On Jul 19, 2021, at 10:26 AM, Matthias Seidel
> wrote:
>
> Hi Jim,
>
> People need macOS builds more frequently to test.
>
Agreed. But every time I seem to encourage a test macOS build, it seems that
people want to hold off...
Hi Jim,
Nothing is wrong, but we have this machine from MacStadium and we can
set it up as a build bot.
People need macOS builds more frequently to test.
It is also good when Arrigo is able to build for macOS (as he can now
build for Windows).
Regards,
Matthias
Am 19.07.21 um 16:14 schrieb
What is wrong w/ using the build stuff that we have used for years?
> On Jul 18, 2021, at 9:00 AM, Arrigo Marchiori wrote:
>
> Dear All,
>
> On Sat, Jul 17, 2021 at 03:27:54PM +0200, Arrigo Marchiori wrote:
>
>> Dear All,
>>
>> I just committed the "catalina" branch:
>>
On Sun, Jul 18, 2021 at 04:41:09PM +0200, Matthias Seidel wrote:
> Hi Arrigo,
>
> I did a short test and it seems that
>
> https://bz.apache.org/ooo/show_bug.cgi?id=127154
>
> is fixed in that build?
Thank you for the pointer... I tried to reproduce it and unfortunately
AOO hung on the dialog
Hi Arrigo,
I did a short test and it seems that
https://bz.apache.org/ooo/show_bug.cgi?id=127154
is fixed in that build?
However, "Checking for Updates" did crash AOO (once).
Regards,
Matthias
Am 18.07.21 um 15:00 schrieb Arrigo Marchiori:
> Dear All,
>
> On Sat, Jul 17, 2021 at
Hi Arrigo
I do not have any Apple devices :)
Did you build any Linux binaries (DEBs)? Can you share a link?
Thanks!
Pedro
> On 07/18/2021 2:00 PM Arrigo Marchiori wrote:
>
>
> Dear All,
>
> On Sat, Jul 17, 2021 at 03:27:54PM +0200, Arrigo Marchiori wrote:
>
> > Dear All,
> >
> > I just
Dear All,
On Sat, Jul 17, 2021 at 03:27:54PM +0200, Arrigo Marchiori wrote:
> Dear All,
>
> I just committed the "catalina" branch:
> https://github.com/apache/openoffice/tree/catalina
>
> The required environment variables on our Mac Mini are the following:
>
> export LC_CTYPE=en_US.UTF-8
>
Dear All,
I just committed the "catalina" branch:
https://github.com/apache/openoffice/tree/catalina
The required environment variables on our Mac Mini are the following:
export LC_CTYPE=en_US.UTF-8
export LANG=en_US.UTF-8
export
Hello,
On Thu, Jul 15, 2021 at 04:52:13PM +0200, Matthias Seidel wrote:
> Hi Arrigo,
>
> Thank you for the work!
>
> Indeed, we need macOS builds more often to let people test...
I hope I am close to the end.
I met a problem with the writerfilter module. It was given by the
proposed libxml
Hi Arrigo,
Thank you for the work!
Indeed, we need macOS builds more often to let people test...
Regards,
Matthias
Am 13.07.21 um 22:24 schrieb Arrigo Marchiori:
> Dear All,
>
> this is to inform you that I am trying to make our shared Mac Mini
> able to build AOO41X.
>
> The sources of
Dear All,
this is to inform you that I am trying to make our shared Mac Mini
able to build AOO41X.
The sources of information on this topic are:
- the Building guide on our Wiki [1] and [2],
- the build script for AOO 4.1.10 [3].
I am a bit struggling behind the differences between the two
n in OpenOffice could you help?
>>
>> - Mail original -
>>> De: "Juan Minor"
>>> À: dev@openoffice.apache.org
>>> Envoyé: Vendredi 19 Février 2021 00:48:13
>>> Objet: Contribution to open office development
>>>
>>> Ho
some resources to get started.
All the best
Peter
- Mail original -
De: "juan francisco Minor"
À: dev@openoffice.apache.org
Envoyé: Vendredi 19 Février 2021 16:28:50
Objet: Re: Contribution to open office development
I can help with any of them. Wherever help is ne
rancisco Minor"
>>> À: dev@openoffice.apache.org
>>> Envoyé: Vendredi 19 Février 2021 16:28:50
>>> Objet: Re: Contribution to open office development
>>>
>>> I can help with any of them. Wherever help is needed. Some assistance
>>> in u
to implement Apache POI.
If there is interest I can look up some resources to get started.
All the best
Peter
- Mail original -
De: "juan francisco Minor"
À: dev@openoffice.apache.org
Envoyé: Vendredi 19 Février 2021 16:28:50
Objet: Re: Contribution to open office development
ffice could you help?
>>>
>>> - Mail original -
>>>> De: "Juan Minor"
>>>> À: dev@openoffice.apache.org
>>>> Envoyé: Vendredi 19 Février 2021 00:48:13
>>>> Objet: Contribution to open office development
>>
o Juan,
> > Which application in OpenOffice could you help?
> >
> > - Mail original -
> >> De: "Juan Minor"
> >> À: dev@openoffice.apache.org
> >> Envoyé: Vendredi 19 Février 2021 00:48:13
> >> Objet: Contribution to open office developm
;
> - Mail original -
>> De: "Juan Minor"
>> À: dev@openoffice.apache.org
>> Envoyé: Vendredi 19 Février 2021 00:48:13
>> Objet: Contribution to open office development
>>
>> Howdy,
>>
>> My name is Juan Minor. I am a computer eng
Hello Juan,
Which application in OpenOffice could you help?
- Mail original -
> De: "Juan Minor"
> À: dev@openoffice.apache.org
> Envoyé: Vendredi 19 Février 2021 00:48:13
> Objet: Contribution to open office development
>
> Howdy,
>
> My name is Ju
Howdy,
My name is Juan Minor. I am a computer engineer with experience in
C/C++. I would like to volunteer my time to help out with this project
should any help be needed.
Best Regards,
Juan M.
-
To unsubscribe, e-mail:
The downloading part is never finished in the previous tries on the machine.
From: Dylan Pham
Sent: Sunday, January 17, 2021 4:08 AM
To: Peter Kovacs
Cc: dev@openoffice.apache.org ; hao...@live.com
Subject: Re: SCONS development state
Thank you Peter, this will be very
Thank you Peter, this will be very helpful.
Dylan
On Sat, Jan 16, 2021 at 10:33 AM Peter Kovacs wrote:
> Hello Dylan,
>
> Hello Ho Wang,
>
>
> I am sorry it took me a while. But here Damjan explains all about the
> SCONS implementation. Please if still time and interest is there have a
> look.
Hello Dylan,
Hello Ho Wang,
I am sorry it took me a while. But here Damjan explains all about the
SCONS implementation. Please if still time and interest is there have a
look.
fixed my issues.
Jim, I had an install issue with latest trunk of your epm repo:
make: INSTALL@: Befehl nicht gefunden (command not found)
Makefile:153: die Regel für Ziel „install“ scheiterte (install failed)
make: *** [install] Fehler 127
I think some sort of typo maybe? 4.4.2 works good.
On 4/23/20 10:44 AM, Peter Kovacs wrote:
Hi Jim,
dmake is not simple. I do know nothing Jim Jagielski...
Today the build system enjoys me with
checking whether the found dmake is the right dmake... configure:
WARNING: no
or
configure: error: no URL for dmake source code specified,
Hi Jim,
dmake is not simple. I do know nothing Jim Jagielski...
Today the build system enjoys me with
checking whether the found dmake is the right dmake... configure:
WARNING: no
or
configure: error: no URL for dmake source code specified, either. Use
--with-dmake-url to supply an URL;
IMO, dmake is simply a build-and-compile dependency. Considering that we pull
in lots of other external dependencies, keeping or dropping dmake will likely
not make any real difference in the people we can attract to help develop, test
and build AOO. At the very least, we know what dmake is
The goal is to move away from dmake. I do struggle with your point of
view, saying moving away from dmake is unimportant, and should be stopped.
I disagree with this position.
Am 16.04.20 um 23:04 schrieb Patricia Shanahan:
On 4/15/2020 10:08 AM, Damjan Jovanovic wrote:
On Wed, Apr 15,
On 4/15/2020 10:08 AM, Damjan Jovanovic wrote:
On Wed, Apr 15, 2020 at 3:15 PM Jim Jagielski wrote:
On Apr 15, 2020, at 3:01 AM, Damjan Jovanovic wrote:
We are also thin on new contributors, and I recall you saying they're
largely scared off by the current build system.
Two
On 4/14/20 9:46 PM, Peter Kovacs wrote:
If one wants to tap in our build system he needs to understand Perl,
shell, make, ant, XML, configure, ...
This is just way to complicated, especially if you want to bring in an
IDE to ease code development.
Damjan is not very happy
On Wed, Apr 15, 2020 at 3:15 PM Jim Jagielski wrote:
>
>
> > On Apr 15, 2020, at 3:01 AM, Damjan Jovanovic wrote:
> >
> >
> > We are also thin on new contributors, and I recall you saying they're
> > largely scared off by the current build system.
> >
>
> Two points:
>
> 1. I doubt that by
> On Apr 15, 2020, at 3:01 AM, Damjan Jovanovic wrote:
>
>
> We are also thin on new contributors, and I recall you saying they're
> largely scared off by the current build system.
>
Two points:
1. I doubt that by the time we finish porting to a whole new build system, we
will even
(they have mac server free for OpenSource Projects!)
# Maven development support for 3rd party contributors
# Various different Platform and distribution support.
## Distribution we might need distribution specific patch support.
# support of building our own dependencies.
## automated Signing
On Wed, Apr 15, 2020 at 6:46 AM Peter Kovacs wrote:
> If one wants to tap in our build system he needs to understand Perl,
> shell, make, ant, XML, configure, ...
>
> This is just way to complicated, especially if you want to bring in an
> IDE to ease code development.
>
>
everything on to it.
On 4/14/2020 9:46 PM, Peter Kovacs wrote:
If one wants to tap in our build system he needs to understand Perl,
shell, make, ant, XML, configure, ...
This is just way to complicated, especially if you want to bring in an
IDE to ease code development.
Damjan is not very happy
If one wants to tap in our build system he needs to understand Perl,
shell, make, ant, XML, configure, ...
This is just way to complicated, especially if you want to bring in an
IDE to ease code development.
Damjan is not very happy with the features gmake offers. I am not sure
where
Am 25.01.19 um 19:08 schrieb Mechtilde:
100 % translated Help are German and Dutch:
https://translate.apache.org/projects/aoo40help/
And here the link to the Ui
https://translate.apache.org/projects/aoo40/
You can sort them yourself at the top of the columns
thanks, I thought it would be
Hello Marcus
100 % translated Help are German and Dutch:
https://translate.apache.org/projects/aoo40help/
And here the link to the Ui
https://translate.apache.org/projects/aoo40/
You can sort them yourself at the top of the columns
Regards
Am 25.01.19 um 18:56 schrieb Marcus:
> Am 25.01.19
Am 25.01.19 um 18:39 schrieb Mechtilde:
Am 25.01.19 um 17:29 schrieb Marcus:
Am 10.01.19 um 16:50 schrieb Pedro Giffuni:
do you remember the BZ issues? I would like to add them to the list in
the new release notes (it's a first, very rough draft):
Hello,
Am 25.01.19 um 17:29 schrieb Marcus:
> Am 10.01.19 um 16:50 schrieb Pedro Giffuni:
>
> do you remember the BZ issues? I would like to add them to the list in
> the new release notes (it's a first, very rough draft):
>
>
Am 10.01.19 um 16:50 schrieb Pedro Giffuni:
Thank you to everyone getting involved in the new release. It is very
much needed and I was really tired of the continuous revamping of the
4.1 releases. It is now clear that we are also doing proper branching of
the releases.
Some of the issues
Hi Dave,
Am 18.01.19 um 06:54 schrieb Dave Fisher:
> What action is there to take? It is a valid action by a downstream. Do we
> wish they posted changes upstream? Yes! Can we require it? No!
It was just a funny side note for a fork that claims to be the "real"
successor of OpenOffice.org.
What action is there to take? It is a valid action by a downstream. Do we wish
they posted changes upstream? Yes! Can we require it? No!
Regards,
Dave
Sent from my iPhone
> On Jan 17, 2019, at 9:19 PM, Peter Kovacs wrote:
>
> The Question is:
>
> Do we want to take action here or not?
>
>
The Question is:
Do we want to take action here or not?
On 17.01.19 21:19, Matthias Seidel wrote:
> Hi Marcus,
>
> Am 17.01.19 um 20:42 schrieb Marcus:
>> Am 17.01.19 um 13:41 schrieb Matthias Seidel:
>>> Two of my commits were immediately picked by LO. [1] [2]
>>>
>>> Always nice to see, that
Hi Marcus,
Am 17.01.19 um 20:42 schrieb Marcus:
> Am 17.01.19 um 13:41 schrieb Matthias Seidel:
>> Two of my commits were immediately picked by LO. [1] [2]
>>
>> Always nice to see, that down streaming still works for the fork... :-D
>
> sure, better then to draw this on their own.
>
> Again with
Am 17.01.19 um 13:41 schrieb Matthias Seidel:
Two of my commits were immediately picked by LO. [1] [2]
Always nice to see, that down streaming still works for the fork... :-D
sure, better then to draw this on their own.
Again with a note who has tested and reviewed it - which is totally
Two of my commits were immediately picked by LO. [1] [2]
Always nice to see, that down streaming still works for the fork... :-D
Regards,
Matthias
[1]
https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073
[2]
wrote:
> Hi guys, I recently graduated with my bachelor's degree and would like to
> get into development and thought that some experience with open office
> would be a great start. I've never been a part of any development teams
> outside of my educational experience so any tips or po
+1 from me
up to the time of a beta release
Mechtilde
Am 14.01.19 um 16:46 schrieb Jim Jagielski:
> At this stage, I think just back porting (svn merge) to the AOO42X branch is
> fine.
> As we get close to a release, we'll need to either have an RM approve it
> or so something like creating a
At this stage, I think just back porting (svn merge) to the AOO42X branch is
fine.
As we get close to a release, we'll need to either have an RM approve it
or so something like creating a STATUS file, with a list of proposed backports
and requiring at least 3 +1s to backport (ie: RTC)
> On Jan
Hi Jim,
Am 09.01.19 um 21:54 schrieb Jim Jagielski:
>
>> On Jan 9, 2019, at 3:46 PM, Jim Jagielski wrote:
>>
>> Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
>> thinking...
How is the process to get commits merged from trunk to AOO42X?
I adjusted some pointers for
Hi guys, I recently graduated with my bachelor's degree and would like to
get into development and thought that some experience with open office
would be a great start. I've never been a part of any development teams
outside of my educational experience so any tips or pointers would be very
Win64 is also making good progress behind the scenes. The uncommitted Win64
UNO bridge I've been coding (a lot of it in AMD64 assembly) should now be
able to call arbitrary C++ methods from UNO and UNO methods from C++ (not
tested yet), but the poorly documented internals of MSVC C++ exception
Okay, have all special quick points to my OpenOffice overview[1]. (I
skipped the ODF, and Pivot part, since there are plenty Bugzilla Issues
which I will find at some point in the future ;P )
I think we have a lot of technical Debt, and Issues that needs to be
fixed. Not only in the building
+1 on doing what we can to move to gbuild as appropriate, but we also need
to find out what our long term plan is, esp as related to non-*Nix platforms.
I hope to get macOS more up-to-date and part of that is fixing the longstanding
confusion regarding UDK library versioning. Currently, AOO
Win64 is also making good progress behind the scenes. The uncommitted Win64
UNO bridge I've been coding (a lot of it in AMD64 assembly) should now be
able to call arbitrary C++ methods from UNO and UNO methods from C++ (not
tested yet), but the poorly documented internals of MSVC C++ exception
Hi again;
I just wanted to stop by and share some ideas of things that need to be
done in AOO after 4.2.
Easier things:
OpenSSL has to be updated, yet again, and while the future versions will
be under an Apache License, making things nicer for us, the API has been
changing so we may need
Hey guys!
Thank you to everyone getting involved in the new release. It is very
much needed and I was really tired of the continuous revamping of the
4.1 releases. It is now clear that we are also doing proper branching of
the releases.
Some of the issues off the top of my head that you may
Hello
Am 09.01.19 um 21:21 schrieb Marcus:
> Am 09.01.19 um 20:25 schrieb Mechtilde:
>> thanks for the branch.
>>
>> How do we handle the translation I think we should do the translation on
>> AOOO42X so we only tranlate for the next release.
>
> IMHO yes. But updates need to be done in the
> On Jan 9, 2019, at 3:46 PM, Jim Jagielski wrote:
>
> Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
> thinking...
>
Yeppers... for sure it's the udk versioning, which is more a Linux thing than a
macOS (or Windows) thing.
Will look into either hacking around it
Ahh... something w/ the cppuhelper stuff. Obviously, some UDK issue I'm
thinking...
76.372903 : lang : ##
76.372943 : lang : Registering extensions:
76.372991 : lang : ##
76.381173
Request for help...
Any ideas would be helpful:
% build --all:instsetoo_native
build -- version: 1775979
=
Building module instsetoo_native
=
Entering
/Users/jim/src/asf/AOO42X/main/instsetoo_native/inc_openoffice/windows/msi_languages
Entering
Am 09.01.19 um 21:20 schrieb Matthias Seidel:
Am 09.01.19 um 21:12 schrieb Marcus:
Am 09.01.19 um 20:44 schrieb Matthias Seidel:
There is more than minor.mk.
I will try to take care of it...
hm, don't we have now a little script for this? To identify all the
places that need tobe changed?
is because I wanted to adjust the links for the update
feed...
Development can, and should, continue on trunk, but ONLY
approved backports should be applied to AOO42X.
Now trunk (aka 420) needs a new internal version number.
What about 450?
Works for me
Hi Marcus,
Am 09.01.19 um 21:12 schrieb Marcus:
> Am 09.01.19 um 20:44 schrieb Matthias Seidel:
>> There is more than minor.mk.
>>
>> I will try to take care of it...
>
> hm, don't we have now a little script for this? To identify all the
> places that need tobe changed? IMHO it should be
If so, I don't know of it.
Agreed that such a beastie should exist.
> On Jan 9, 2019, at 3:12 PM, Marcus wrote:
>
> Am 09.01.19 um 20:44 schrieb Matthias Seidel:
>> There is more than minor.mk.
>> I will try to take care of it...
>
> hm, don't we have now a little script for this? To identify
Am 09.01.19 um 20:44 schrieb Matthias Seidel:
There is more than minor.mk.
I will try to take care of it...
hm, don't we have now a little script for this? To identify all the
places that need tobe changed? IMHO it should be somewhere in devtools.
Marcus
Am 09.01.19 um 20:41 schrieb
There is more than minor.mk.
I will try to take care of it...
Am 09.01.19 um 20:41 schrieb Jim Jagielski:
> All done
>
>> On Jan 9, 2019, at 2:21 PM, Matthias Seidel
>> wrote:
>>
>> 9800
>
smime.p7s
Description: S/MIME Cryptographic Signature
All done
> On Jan 9, 2019, at 2:21 PM, Matthias Seidel
> wrote:
>
> 9800
ntual branch for a 4.2.x release. All backports
> from trunk are done to that branch.
>
> Make sense?
>
>>
>> The reason I ask is because I wanted to adjust the links for the update
>> feed...
>>
>>>
>>> Development can, and should, cont
ronment on any
> Linux / Windows.
>
> Regards
> Vittal Sher
>
> From: Jim Jagielski
> Sent: Wednesday, January 9, 2019 11:10 PM
> To: OOo Apache
> Subject: AOO 4.2.x development branch created
>
> Trunk has been branched off to the (eventual) release branch
> for the
t ready. once done, we then tag AOO420 from 42X. That is, the 42X
> branch will always be the eventual branch for a 4.2.x release. All backports
> from trunk are done to that branch.
>
> Make sense?
Not really (for me).
But I am sure there are others that have an opinion...
>
>&g
t ready. once done, we then tag AOO420 from 42X. That is, the 42X
> branch will always be the eventual branch for a 4.2.x release. All backports
> from trunk are done to that branch.
>
> Make sense?
>
>> The reason I ask is because I wanted to adjust the links for the upd
l branch for a 4.2.x release. All backports from
trunk are done to that branch.
Make sense?
>
> The reason I ask is because I wanted to adjust the links for the update
> feed...
>
>>
>> Development can, and should, continue on trunk, but ONLY
>> approved backpo
The reason I ask is because I wanted to adjust the links for the update
feed...
>
> Development can, and should, continue on trunk, but ONLY
> approved backports should be applied to AOO42X.
Now trunk (aka 420) needs a new internal version number.
What about 450?
Regards,
, 2019 11:10 PM
To: OOo Apache
Subject: AOO 4.2.x development branch created
Trunk has been branched off to the (eventual) release branch
for the AOO 4.2.x series. The branch is:
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X
Development can, and should, continue on trunk, but ONLY
Trunk has been branched off to the (eventual) release branch
for the AOO 4.2.x series. The branch is:
https://svn.apache.org/repos/asf/openoffice/branches/AOO42X
Development can, and should, continue on trunk, but ONLY
approved backports should be applied to AOO42X.
Cheers
Dear,
We would like to invite you to participate in a survey on *interaction design
in distributed software development*.
The purpose of this survey is to identify the perception of people involved
in design or software development with geographically distributed teams on
interaction design
Dear,
We would like to invite you to participate in a study on interaction design
in distributed software development.
At first, we are identifying people who are currently participating or who
have already participated in design or software development with
geographically distributed teams
quot;make" involved at all - an unprecedented development
[LibreOffice can only build Java modules with their gbuild, in the shell;
Java IDEs certainly can't parse gbuild's eval-filled non-deterministic
makefiles, so their Java development must be quite a pain ;)].
Today I even got gbuild to extrac
that brings you closer to your whish.
Please describe more closely what you mean, or point at a dedicated
issue.
Thank you.
All the best
Peter
On 29.06.2018 10:51, Pavel Vlček wrote:
Dear devs,
is accessibility of Open Office in active development?
Thanks,
Pavel
1 - 100 of 213 matches
Mail list logo
