Re: Release Notes work -- AOO 4.1.2 issues/other inclusions
On Mon, Sep 28, 2015 at 1:08 AM, FR web forum wrote: > Maybe this patch submitted by hanya could be included: > https://bz.apache.org/ooo/show_bug.cgi?id=126557 > This patch is now submitted to trunk and needs additional testing. > > - Mail original - > De: "Andrea Pescetti" > À: dev@openoffice.apache.org > Envoyé: Lundi 28 Septembre 2015 01:13:11 > Objet: Re: Release Notes work -- AOO 4.1.2 issues/other inclusions > > On 28/09/2015 Kay Schenk wrote: > > It is likely that not all approved issues have > > actually been committed to the AOO410 trunk. > > Correct. A few are still pending. And, conversely, all AOO410 commits > are related to blocker issues, except the CoinMP update (which is a > requested blocker at the moment, but is already committed). > > > A BZ query of items (approved release blockers for 4.1.2) > > that can be run if you have a BZ account > > > https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.1.2_approved_and_fixed&sharer_id=7 > > Thanks! If you found the trick, it would be very handy to have the four > links at > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 > updated directly in the wiki page, so as to track approved blockers, > requested blockers, [maybe even denied blockers?], approved+requested > and RESOLVED ones. Once we have those, we can put QA volunteers at work > as soon as we have builds to test. > > Regards, >Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- - MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu
Re: Inquiries about a Manual for this Office Suite.
On Mon, Sep 28, 2015 at 5:19 AM, Mike McClay wrote: > Hi, > Please can you tell me if One can purchase a Manual for this Disc? > Many thanks, > Mike. > Hi Mike -- We only distribute Apache OpenOffice from direct download here. If you need some additional resources for using Apache OpenOffice, please take a look at the offerings on our wiki in the Documentation area: https://wiki.openoffice.org/wiki/Documentation -- - MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu
Re: Release Notes work -- AOO 4.1.2 issues/other inclusions
On 09/27/2015 04:13 PM, Andrea Pescetti wrote: > On 28/09/2015 Kay Schenk wrote: >> It is likely that not all approved issues have >> actually been committed to the AOO410 trunk. > > Correct. A few are still pending. And, conversely, all > AOO410 commits are related to blocker issues, except the > CoinMP update (which is a requested blocker at the moment, > but is already committed). > >> A BZ query of items (approved release blockers for 4.1.2) >> that can be run if you have a BZ account >> https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.1.2_approved_and_fixed&sharer_id=7 >> > > Thanks! If you found the trick, it would be very handy to > have the four links at > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 > updated directly in the wiki page, so as to track approved > blockers, requested blockers, [maybe even denied blockers?], > approved+requested and RESOLVED ones. Once we have those, we > can put QA volunteers at work as soon as we have builds to > test. > > Regards, > Andrea. Hi. I updated the wiki page with some BZ searches. I didn't include the 'release denied'. -- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
OpenOffice 4.1.2 release date
I've been very reluctant so far to provide an explicit release date for OpenOffice 4.1.2, because of some processes that were not under control yet. A generic "late 2015" or "last quarter 2015" would be all you got from me. This is still true, but I want it to be very clear that we are targeting October not December here. There are at least two good reasons for us to target October. On one side, patience is over. Users deserve some good news. We, the volunteers, need to feel useful and involved again. And, for a lot of different reasons, everyone (including people you would never imagine) would be happy to see an OpenOffice release in the very short term. So OpenOffice 4.1.2 must be released as soon as we are able to ship a release. On the other side, progress is remarkable lately. The last weeks marked a surge in activity that is unprecedented in months. This week is ApacheCon Europe time, so some actions (not decisions of course) will appear on the dev list after the fact, but I expect that we iron out the last Infra blockers. And QA will be reactivated as soon as possible, with some volunteers already lining up for receiving bugs to check. Here is a list of the current blockers: 1) Bugfixes: most of the patches for 4.1.2, especially the "risky" ones, have been merged; we still have a few left, as well as a few fixes still to apply to the already merged code; but this is mostly done. Besides the really wanted bugfixes, the rest will be left out of 4.1.2 if it delays our release. 2) SNAPSHOT binaries (actually SNAPSHOT will have to be moved due to a Mac build breaker in the CoinMP upgrade, now fixed) must be available; they will come; we will not use the buildbots since they are not usable for release builds due to wrong OS versions. 3) We need a place to upload dev builds to. That place is ready as of today at https://dist.apache.org/repos/dist/dev/openoffice/ ; but it will still need some Infra work (access and quota settings) which I expect to have ready soon. 4) QA. We need and want good QA on the snapshot, so that our first Release Candidate has high chances of approval; 4.1.2 won't be revolutionary after all, it is a normal release. But several people and processes have changed, and we need a team of people ready to check the builds. So a realistic schedule, which is to be used mostly as a guideline but which we should aim at respecting, is: - Now (28 Sept, but also earlier): The AOO410 branch is in review then commit mode. Don't commit to it unless you know what you are doing. We can't enforce a delay between committing to trunk and AOO410, but be careful. - This week (by 4 Oct): we get all we need from Infra in terms of access, disk space and information; last bugfixes get committed and from that point on we only fix... the bugfixes themselves. - By 7 Oct: we have a build available for testing (I do hope we have it earlier, a build from the current SNAPSHOT tag would work too!); we give QA and all volunteers a full week to test this snapshot. - By 14 Oct: we have feedback from QA, hopefully we manage to quickly apply fixes - By 18 Oct: the Release Candidate is available as both source and binaries. We vote. - By 25 Oct: Vote passes. Site is ready. Builds are copied. - Last week of October: release is announced. There is some flexibility in both directions (if we are able to upload test builds already tomorrow, why not? and conversely if we need an extra Release Candidate, let it be); but it is clear that if you have some time to spare for the project, it's better to allocate it in October. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] Fwd: Re: FOSDEM 2016 - Call for Participation
On 28/09/2015 RA Stehmann wrote: as promised Mechtilde and I will join the Apache booth (stand) team at FOSDEM 2016. So you think it's better not to apply (additionally) as OpenOffice? We don't have any assurance that the ASF will be granted a stand, and OpenOffice has always been granted one for years. It's a great pleasure for us, that the greater Apache Community joins FOSDEM with a booth. I was assuming/understanding that we would have sent both the OpenOffice request (highly likely to be approved; but less important) and the ASF request (new, so less likely; but more important). And that, if both were approved, we would merge the tables, or if one was approved we would share the table. So no doubt we would all be together, in any case; I thought we would try and maximize the chance of getting a presence. It appears Daniel has already sent a request on behalf on the ASF (deadline is in November) but I haven't seen it at https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2016 or on the lists, so I have no idea about the contents. I just want to be sure that the ASF at large, and OpenOffice as part of it, get a presence under whatever name; and that we maximize our chances to be at FOSDEM. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] Fwd: Re: FOSDEM 2016 - Call for Participation
Hi, I'm intending to come to help you on the stand for french speakers. It will be a real pleasure to meet you again. Regards -- gw 2015-09-28 9:48 GMT+02:00 RA Stehmann : > Hello, > > as promised Mechtilde and I will join the Apache booth (stand) team at > FOSDEM 2016. > > It's a great pleasure for us, that the greater Apache Community joins > FOSDEM with a booth. > > Kind regards > Michael > >
4.1.2_release_blocker granted: [Issue 126305] WebDAV lock on 4.1.1 does not work
Andrea Pescetti has granted Andrea Pescetti 's request for 4.1.2_release_blocker: Issue 126305: WebDAV lock on 4.1.1 does not work https://bz.apache.org/ooo/show_bug.cgi?id=126305 --- Comment #19 from Andrea Pescetti --- Reopening due to the (easy) fix proposed on the dev list: http://www.mail-archive.com/dev@openoffice.apache.org/msg25156.html Giuseppe, are you going to implement the change yourself? Due to the nature of this change, a patch with respect to the current trunk would be best. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Trunk for building testing
On 09/28/2015 01:31 AM, dav...@flossconsulting.it wrote: > I've finally a little bit of time to try if my building > stack on Win7 is ok. > > I've searched online info about what trunk to use to build > AOO but there are tons of outdated information. > > The question is simple: what is the AOO 4.1.2 devel trunk to > use for building testing purpose? > > Davide https://svn.apache.org/repos/asf/openoffice/tags/SNAPSHOT SNAPSHOT was reset on 2015-09-27. A bit of clarification. This is not really a "development" trunk, but a pre-release branch. Development continues in: https://svn.apache.org/repos/asf/openoffice/trunk with previously tested changes merged into AOO412 as needed. -- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Inquiries about a Manual for this Office Suite.
Hi, Please can you tell me if One can purchase a Manual for this Disc? Many thanks, Mike.
Re: Trunk for building testing
davide wrote: I've finally a little bit of time to try if my building stack on Win7 is ok. Thanks, nice! The question is simple: what is the AOO 4.1.2 devel trunk to use for building testing purpose? The 4.1.2 release will be done from this branch: $ svn co https://svn.apache.org/repos/asf/openoffice/branches/AOO410 It is named AOO410, but it was used for 4.1.0, 4.1.1 and will be used for 4.1.2 too. This means that changes committed to trunk will NOT be released unless explicitly merged to AOO410. This is why you see a lot of "release_blocker" e-mails here: they are for merging fixes from trunk into AOO410. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Incompatible change of oslFileError?
On 28/09/15 11:07, Stephan Bergmann wrote: >> $ svn diff -c1705196 sal/inc/osl/file.h >> Index: sal/inc/osl/file.h >> === >> --- sal/inc/osl/file.h(revision 1705195) >> +++ sal/inc/osl/file.h(revision 1705196) >> @@ -132,6 +132,7 @@ >> osl_File_E_USERS, >> osl_File_E_OVERFLOW, >> osl_File_E_NOTREADY, >> +osl_File_E_LOCKED, >> osl_File_E_invalidError,/* unmapped error: always last >> entry in enum! */ >> osl_File_E_TIMEDOUT, >> osl_File_E_NETWORK, > > Are you sure that this incompatible change is worth it? By placing the > new enumerator somewhere in the middle of the existing enum, you > unnecessarily not only break compatibility with older versions of AOO, > but also with other OOo derivatives. > Stefan is correct, this should be changed and the new enumerator should be better added to the end. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Incompatible change of oslFileError?
$ svn diff -c1705196 sal/inc/osl/file.h Index: sal/inc/osl/file.h === --- sal/inc/osl/file.h (revision 1705195) +++ sal/inc/osl/file.h (revision 1705196) @@ -132,6 +132,7 @@ osl_File_E_USERS, osl_File_E_OVERFLOW, osl_File_E_NOTREADY, +osl_File_E_LOCKED, osl_File_E_invalidError,/* unmapped error: always last entry in enum! */ osl_File_E_TIMEDOUT, osl_File_E_NETWORK, Are you sure that this incompatible change is worth it? By placing the new enumerator somewhere in the middle of the existing enum, you unnecessarily not only break compatibility with older versions of AOO, but also with other OOo derivatives. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
sporadic sdext build failures
I've occasionally seen the sdext module fail to build:
Making:minimizer.srs
: &&
LD_LIBRARY_PATH=/tmp/openoffice/aoo-4.2.0/main/solver/420/unxfbsdx.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
/tmp/openoffice/aoo-4.2.0/main/solver/420/unxfbsdx.pro/bin/rsc -presponse
-verbose @/tmp/mkZY5FmB
/usr/local/bin/bash:
/tmp/openoffice/aoo-4.2.0/main/solver/420/unxfbsdx.pro/bin/rsc: No such file or
directory
dmake: Error code 127, while making '../../unxfbsdx.pro/srs/minimizer.srs'
1 module(s):
sdext
need(s) to be rebuilt
The latest FreeBSD buildbot run seems to have encountered this as well:
When running single-threaded builds, I've noticed that the order that
the modules are built seems to be kind of non-deterministic. I'm
guessing that this is a property of build.pl. In that case the failure
could be the result of a missing dependency specification, and sometimes
the ordering is such that it triggers a build failure. Interestingly, I
don't believe I've ever seen this failure in a parallel build.
The build system is pretty mysterious to me, but my best guess is that
adding "rsc" to the first line of main/sdext/prj/build.lst will fix the
problem.
dx sdext : L10N:l10n offuh comphelper unotools readlicense_oo
cpputools cppuhelper sal javaunohelper officecfg LIBXSLT:libxslt xmlhelp NULL
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Trunk for building testing
I've finally a little bit of time to try if my building stack on Win7 is ok. I've searched online info about what trunk to use to build AOO but there are tons of outdated information. The question is simple: what is the AOO 4.1.2 devel trunk to use for building testing purpose? Davide - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Release Notes work -- AOO 4.1.2 issues/other inclusions
Maybe this patch submitted by hanya could be included: https://bz.apache.org/ooo/show_bug.cgi?id=126557 - Mail original - De: "Andrea Pescetti" À: dev@openoffice.apache.org Envoyé: Lundi 28 Septembre 2015 01:13:11 Objet: Re: Release Notes work -- AOO 4.1.2 issues/other inclusions On 28/09/2015 Kay Schenk wrote: > It is likely that not all approved issues have > actually been committed to the AOO410 trunk. Correct. A few are still pending. And, conversely, all AOO410 commits are related to blocker issues, except the CoinMP update (which is a requested blocker at the moment, but is already committed). > A BZ query of items (approved release blockers for 4.1.2) > that can be run if you have a BZ account > https://bz.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.1.2_approved_and_fixed&sharer_id=7 Thanks! If you found the trick, it would be very handy to have the four links at https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 updated directly in the wiki page, so as to track approved blockers, requested blockers, [maybe even denied blockers?], approved+requested and RESOLVED ones. Once we have those, we can put QA volunteers at work as soon as we have builds to test. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] Fwd: Re: FOSDEM 2016 - Call for Participation
Hello, as promised Mechtilde and I will join the Apache booth (stand) team at FOSDEM 2016. It's a great pleasure for us, that the greater Apache Community joins FOSDEM with a booth. Kind regards Michael signature.asc Description: OpenPGP digital signature
