Emanuele wrote:
Would you mind trying to download from the following sourceforge mirror?
https://netix.dl.sourceforge.net/project/openofficeorg.mirror/4.1.5/binaries/en-US/Apache_OpenOffice_4.1.5_Linux_x86-64_install-rpm_en-US.tar.gz
Works for me.
$ curl -s
On 12/01/2018 Simon Phipps wrote:
informal dinner on the Saturday evening at FOSDEM (February 3rd, 8pm) in
Brussels
I'll have other commitments for the evening, thanks. Still, this is a
good occasion to remind that, for the fifth year in a row, we'll have a
shared devroom running for the
On 10/01/2018 Greg Stein wrote:> status.apache.org reports services that
are *down*, rather than individual
bugs/problems.
Just to be clear, we had two different issues here:
1. Some advanced search options broke due to incompatibility with the
new SQL server (and this is fixed, which is
Kay Schenk wrote:
I know we have a number of Google tests incorporated currently. I don't
know much about how to construct these, but I'd like to help as well.
Sure, this would be very nice to have!
But the discussion here (especially on the QA list) is mostly focused on
manual testing by
FR web forum wrote:
It's time for Infra to take a look.
Did you follow this ask or should I do it?
The preferred way to contact INFRA is by creating an issue in JIRA.
I went ahead and created it this time:
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-15822
You can subscribe to
Dave Fisher wrote:
What is the full url you are using?
Would you try to run a traceroute and dig on that domain?
I've tested again. Same results as reported in the other discussion.
Basically, one IP from the DNS record is working and the other is not
(so if you incur in the non-working one,
imacat wrote:
Can anybody help me publish my extension? >
https://extensions.openoffice.org/project/pokemon-go-iv-calculator
This (as well as removing spam comments) can be done by any site
moderator; we have several PMC members with these privileges, me
included. I've republished your
Matthias Seidel wrote:> Am 08.01.2018 um 22:06 schrieb Marcus:
Hm, do we had notifications for 3.3.x when 4.1.4 (and older) was out?
Yes, until 2014. [1]
Somehow we stopped notifying our "old" users after 4.1.1 came out.
I always found it irritating that the notification did not mention the
Hagar Delest wrote:
For the record, I think that the forums (or at least the English one)
are also less responsive. Maybe due to the server change.
I'm not sure it's the same problem. The problem being discussed here is
not about the site being responsive, but about something like: I open
On 05/01/2018 Dave Fisher wrote:
See the IP Addresses and if they are on the same continent as you when
you have trouble. See if the trace route has high latency.
Thanks, this will indeed help a lot in troubleshooting and I have
interesting results:
$ wget it.openoffice.org
On 05/01/2018 Marcus wrote:
Am 05.01.2018 um 17:26 schrieb Matthias Seidel:
why our homepage for Ukrainian links to "ua" [1] and not to
uk (or uk-UA)?
same difference: country = "ua" [2] and language = "uk" [3].
Probably the project was setup (at the time) with a wrong convention
that
On 04/01/2018 mseidel wrote:
Author: mseidel
Date: Thu Jan 4 16:56:16 2018
New Revision: 1820131
URL: http://svn.apache.org/viewvc?rev=1820131=rev
Log:
Some (minor) corrections to ReadMe
Note that this will result in a lot of strings needing translation
updates. We may have different
CCing Chris for the two messages below. Maybe a SQL version issue?
Regards,
Andrea.
On 04/01/2018 21:59, Hagar Delest wrote:
Note: same for the other languages (Italian anf French tested).
The DISTINCT 3065 thing seems a common one:
In French forum:
Erreur générale
SQL ERROR [ mysqli ]
On 03/01/2018 Ash Blade wrote:
I saw that you are looking for help with building Open Office from source and I
think my current set of skills could be put to good use with this task.
Welcome, Ash! Yes, we can surely put your skills to good use here.
With your current experience I think you
Matthias Seidel wrote:
I think holidays are over now (sigh) and we can revert to the "normal"
OpenOffice logo.
Should I change it for the Italian page, too?
Not yet (for the Italian page) thanks. Traditionally Italian holidays,
for example school holidays, run 25 Dec to 6 Jan, and it is still
Chris Lambertus wrote:
This is ONLY to move the back-end MySQL database onto a new box.
Thanks for the explanation. Then this is indeed low-risk and the more
challenging tasks will come with
https://issues.apache.org/jira/browse/INFRA-13281
which I will continue to monitor.
Regards,
Chris Lambertus wrote:
At 0100 UTC on Thursday January 4th, I will be moving the OpenOffice PHPBB
forum databases to a new server.
Can you elaborate more, or tell us what the best place for further
discussions is?
This is good news in itself, but I believe I'm the only active project
Rory O'Farrell wrote:
Andrea Pescetti wrote:
The best archive build to use to the purpose would be the following:
https://ci.apache.org/projects/openoffice/install/linux64/
(5th entry)
I'll also try the OO 4.2.0 version you indicated.
For the record, I've tried it on my system (Ubuntu 14.04
Rory O'Farrell wrote:
Jose R R wrote:
Issue is present in my computing environment, too.
"out of the box" Xubuntu 16.04.3 386 ... There was no problem on that system.
I tested too and I wasn't able to reproduce the problem:
- 4.1.5 on an RPM-based system (operation took a few seconds)
-
Rory O'Farrell wrote:
I have tested this on Xubuntu 16.04.3 (XFCE), Ubuntu 16.04.3 (Gnome), Debian
9.30 (XFCE), all showing the same freeze.
On Centos 7 and Antergos 17.12 (RPM distros) ToC rebuilds in about 10 seconds.
I wouldn't blame it on the package format, since DEB and RPM versions
a lot of manual work and we
could try to split it and make it accessible to people who can't fully
build OpenOffice too.
Regards,
Andrea.
Andrea Pescetti wrote:
Further updates, with some numbers based on Portuguese (one of the
several languages that are reported as 100% complete in Po
error-free in order to test a full import.
Regards,
Andrea.
Il 30/12/2017 00:42, Andrea Pescetti ha scritto:
Some further notes (then someone else may want to reorganize this, but
for the moment I'm just collecting them):
- The problem (not a problem actually; just the need to translate s
Pedro Lino wrote:
Hi Andrea, all
Impress document and right-click on the slide you will see the context
menu in English.
Problem confirmed with Portuguese build
Thanks for checking. And actually, as I wrote, I wouldn't consider this
a problem. Code refactoring caused some strings to be
uld be:
1. Run the same process (2 and 3) on AOO415 and see if the match is
perfect there (no warnings)
2. Build both AOO415 and trunk with the new SDF file and see if
translations from Pootle are picked up properly.
Regards,
Andrea.
Il 28/12/2017 00:39, Andrea Pescetti ha scritto:
Just a f
Just a few notes on what I've found so far about the 4.2.0 localization,
in case others (like Keith, who wrote he is interested) want to follow
and/or proceed.
Of course, you will need:
1. A full checkout of trunk; I believe some of the tools are built
during the build process, but I'm using
As the focus is switching back to trunk, I expect other people to find
simple issues that they would be able to do themselves but that are
suitable for newcomers too.
In that case we can involve people from the recruitment mailing list:
just create an issue in Bugzilla and send a mail to
See https://bz.apache.org/ooo/show_bug.cgi?id=127637 for context.
In short: when we bundle a dictionary in OpenOffice, it is downloaded
during bootstrap and then bundled using the filename we use at bootstrap
phase. This filename does not follow any conventions at the moment, and
a change
As usual, the "holiday version" of the OpenOffice logo is now online at
http://www.openoffice.org/
I've applied it to English and Italian; I didn't apply it to all
languages since it may make more sense in some context than others.
Still, applying it is trivial: just do the equivalent of
On 24/12/2017 CobaltCactus wrote:
Many downloads go the full
gammet to 95% and then CRASH. Sourceforge does not carry a good
reputation for download sites anymore.
The SourceForge downloads worked well (and still work for me, just
tested) for us so far. If you have troubles, you can download
On 21/12/2017 Jim Jagielski wrote:
So with more than the sufficient 3 +1 (binding) votes
and no vetos, I call the VOTE has PASSED.
Just for the record, I've run the usual release checks in the last
couple days with no issues. The vote is now closed but mine would have
been a +1.
What I
Carl Marcum wrote:
"Set the attribute "Latest Version" to all full installation files for
every platform."
I believe this should be done once files have been "unstaged", which in
turn should be done just a few hours before uploading the download pages.
The process is at
Carl Marcum wrote:
My upload to SF has been going all day.
Looks to be about 1/2 way done.
Strange, normally I do it from a good connection but I think the entire
4.1.4 upload took about 3 hours. On the other hand, uploading to the ASF
servers (especially now that everything must be done
Carl Marcum wrote:
Can someone with admin rights to the SourceForge account grant me
permissions so I can upload the release?
Done. Thank you and enjoy!
We now have 6 PMC members as administrators of that area, so we should
be well covered.
Regards,
Andrea.
FR web forum wrote:
I see that you are come back here.
I read all lists. I'm a volunteer like everybody else, so I answer when
I can, and I do what I can do. Other Pootle admins apparently are even
less responsive than me, since I'm the only one who shows signs of life.
Could you have a
Carl Marcum wrote:
On 12/21/2017 11:36 AM, Jim Jagielski wrote:
Who wants to do the Upload to SF?
That's usually me but if the Release Express has to leave then...
I'm willing if I'm able.
...then go ahead, please.
Are there instructions somewhere
Sure. The "Upload" section of
Marcus wrote:
Please give a warm welcome to Keith.
Fixing last name spelling for the records: Keith N. McKenna (here and in
subject).
Welcome back Keith!
Andrea
-
To unsubscribe, e-mail:
Pedro Lino wrote:
(the same as clicking on the Dictionaries button on the Extensions website)
However searching for the words spelling or dictionaries returns many
more results than the Dictionaries button (for instance none of the
Portuguese tools show up when clicking Dictionaries)
This means
Marcus wrote:
Luckily we have 2 volunteers: Carl and Peter. Therefore please vote by
replying to this thread.
[ ] Carl Marcum (cmarcum)
[ ] Peter Kovacs (petko)
[ ] Abstain (I cannot/won't choose between them)
I vote for Carl Marcum (cmarcum), purely due to the nature of the job. I
would
Jim Jagielski wrote:
So our options are:
1. We stick w/ CentOS5 as our ref build system for 4.2.0 but force
Gnome VFS.
2. We move to CentOS6, accept the default of GIO but understand that
this moves CentOS5 as a non-supported OS for our community builds.
3. Just as we offer
On 04/12/2017 Jim Jagielski wrote:
Say we release 4.1.5 and that build number is 9799. We then
release start doing betas and RCs for 4.2.0 and use 9800,
9801 and 9802. We then find out we need to release a 4.1.6.
Is that BUILD number now 9803?
This is an interesting scenario. The way it has
On 04/12/2017 toki wrote:
English dictionaries has an updated release every month, but extensions
for AOo [...] are only released every two months, unless there has
been a recent release, in which case the update extension release is
skipped.
This would be nice in theory. In practice,
On 04/12/2017 Jim Jagielski wrote:
On Dec 3, 2017, at 3:57 PM, Andrea Pescetti wrote:
We don't have a 4.1.5 blocker flag in Bugzilla ...
How does one add one in Bugz?
Marcus knows the magic for it. I believe only Bugzilla admins can create
a new flag.
Regards,
Andrea
Jim Jagielski wrote:
Who has write access to that?
The main OpenOffice site is in our source repository, so all committers
have access to it. But for some reason we don't post news there, even
though we have an (outdated) news archive there.
The OpenOffice blog
if you retry now you may be able to submit a proposal.
Regards,
Andrea.
Il 02/12/2017 15:54, Andrea Pescetti ha scritto:
Reminder: 3 days left (Saturday, Sunday, Monday) for submitting your
FOSDEM proposal. You just need a title and a short abstract for the
moment. Submission instructions below
Jim Jagielski wrote:
I propose that we, "officially", start the ball
rolling in the process of releasing AOO 4.1.5.
Are you accepting blockers? My only blocker would be the English
dictionary update https://bz.apache.org/ooo/show_bug.cgi?id=127621 (a
new version is available and we don't
Keith N. McKenna wrote:
That begs the Question should we add a section to the overall build
guide for CentOS6? If yes I can add the section as a clone of the
CentOS5 Guide with all the proper warnings and notes about it needing
updating for the CentOS6 specifics.
No, this wouldn't be helpful
FR web forum wrote:
No news about 4.1.4 build.
Anybody to tweet this annoucement?
https://twitter.com/ openofficeorg
This is not the official OpenOffice Twitter account. The official account is
https://twitter.com/apacheoo
that is managed, as far as I know, by Roberto on behalf of the PMC.
On 02/12/2017 Jim Jagielski wrote:
What I don't want is some hybrid monstrosity like we
have now. Nor do I want work on the build system to hold
off release of 4.2.0.
This is surely a good point. Actually, the wide delay between 4.1.0 and
the future 4.2.0 is due in big part to build changes.
Jim Jagielski wrote:
On Dec 2, 2017, at 5:56 PM, Andrea Pescetti wrote:
On 30/11/2017 Jim Jagielski wrote:
I think for 4.2.x and later, we have deprecated CentOS5 as a supported
build system... I ran into a LOT of issues.
Such as, for example?
for starters:
o zip 3.0.
o GIO
OK, I now
Jim Jagielski wrote:
I went ahead and copied the 4.1.4 page and created:
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.5
Of course, it needs to be further cleaned up. I can RM if that's OK
with everyone.
Fine with me, let's keep unchanged everything that worked well for
On 01/12/2017 Jim Jagielski wrote:
I see that Pat has committed the security patches to trunk, which is fantastic!
Maybe we should take the next few business days and go thru Bugz
and see what, if anything, would be low-risk patches to trunk and
pencil in, say, Dec 7th as a "code freeze" date
Peter Kovacs wrote:
https://bz.apache.org/ooo/show_bug.cgi?id=20819 ...
The best way imho is to let the users vote. How about follwing flow:
1) check if we can include the extention by license or find an
agreement with the maintainers.
2) Put a call to Vote if the package should be included or
On 30/11/2017 Jim Jagielski wrote:
I think for 4.2.x and later, we have deprecated CentOS5 as a supported
build system... I ran into a LOT of issues.
Such as, for example? I think that the guide we have at
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#CentOS_5
Reminder: 3 days left (Saturday, Sunday, Monday) for submitting your
FOSDEM proposal. You just need a title and a short abstract for the
moment. Submission instructions below.
Regards,
Andrea.
Il 27/11/2017 08:42, Andrea Pescetti ha scritto:
Reminder: submission deadline for proposal
Reminder: submission deadline for proposal is in 7 days (next Monday).
Anyone attending FOSDEM is welcome to prepare a short presentation.
The call is now published at
https://blogs.apache.org/OOo/entry/open-document-editors-devroom-at
Regards,
Andrea.
On 19/11/2017 Andrea Pescetti wrote
On 24/11/2017 Patricia Shanahan wrote:
To answer Damjan's question "when are these 4.1.x releases going to
stop?", we need to continue with 4.1.x builds, and releases as needed,
at least until 4.2.0 development is complete.
This is correct but it misses a (probably taken for granted) detail:
On 24/11/2017 Jim Jagielski wrote:
Question: Is CentOS 5 still our preferred version, or should we deprecate
CentOS5 for CentOS 6?
We should move to CentOS 6. I've explained it in detail at
https://bz.apache.org/ooo/show_bug.cgi?id=127513 more than 3 months ago
and I'll happily discuss this
Matthias Seidel wrote:
Am 26.11.2017 um 18:42 schrieb Dick Groskamp:
http://www.openoffice.org/ui/accessibility/index.html
with the suggestions Karla made:
1. remove the link to bobby ( I checked: bobby isn't available
anymore, at least not from that link)
or replace it by the one Karla
Patricia Shanahan wrote:
This is a slightly complicated issue, and I am not sure how to handle
the related Bugzilla issues.
Kay is right. Issues like
https://bz.apache.org/ooo/show_bug.cgi?id=127600 are RESOLVED (i.e., we
have committed code that fixes the issue) but not CLOSED (since we
Matthias Seidel wrote:
It seems that "openssl-0.9.8zg.tar.gz" is missing on Sourceforge (OOO
Extras):
https://sourceforge.net/projects/oooextras.mirror/files/
Added earlier today, should be visible now.
More admins can always be added to our SourceForge area, just provide
the SourceForge
Andrea Pescetti wrote:
Important dates:
- Submission deadline: 4 Dec 2017
- FOSDEM: [3-]4 Feb 2018, Brussels, Belgium.
Just to avoid confusion about dates: FOSDEM is 3-4 February 2018 and
runs for the full day both days. The Open Document Editors (including
OpenOffice) devroom is on Saturday
The Call for talks for the Open Document Editors (such as OpenOffice) is
open. I'll republish the full call on the OpenOffice blog later today to
have a reference URL.
Important dates:
- Submission deadline: 4 Dec 2017
- FOSDEM: 4 Feb 2018, Brussels, Belgium.
I encourage everybody who plans
Dave Fisher wrote:
I’ve 4.1.3 works. I’ve confirmed that 4.1.2 GA has the Base problem.
Read "Base 4.1.2 does not open Tables and Queries in Mac OSX":
http://openoffice.2283327.n4.nabble.com/Status-of-quot-Base-4-1-2-does-not-open-Tables-and-Queries-in-Mac-OSX-quot-td4683000.html
(this is
Peter Kovacs wrote:
But maybe we should simply consider to write this part of the code
again, with the goal that it works with the old and new ones.
So I think I will try this. It does not make any differences if I can
compile anyhow.
Opinions?
Did you ever get a successful build, on any
Marcus wrote:
Am 07.11.2017 um 09:57 schrieb Peter Kovacs:
I am a bit confused about the 2 pull request. They both seem to try to
merge changes via git into the Git Repo.
So this would be https://github.com/apache/openoffice/pulls - both of
them are not useful. One is badly written, the
Jim Jagielski wrote:
I am wondering if this means/requires that the build machine
MUST be running 10.12 (Sierra).
The original report https://bz.apache.org/ooo/show_bug.cgi?id=127580
says that the Base bug happens with the new (20171101) builds but not
with the 4.1.4 builds released in
Matthias Seidel wrote:
Am 31.10.2017 um 23:39 schrieb Andrea Pescetti:
Andrea Pescetti wrote:
In terms of the update feed, we can keep on hold the update feeds for
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
is out, we will push the update as usual.
I could
Andrea Pescetti wrote:
In terms of the update feed, we can keep on hold the update feeds for
the 4.1.3 (and earlier) to 4.1.4 upgrade for Mac users; and once 4.1.5
is out, we will push the update as usual.
Another obvious thing we can do (if we are really sure that 4.1.4 for
Mac contains
Dave Fisher wrote:
I would like to know what Andrea and Matthias think since they have been
working with the upgrade system.
This is just a bug. A bad bug, that teaches us that (let alone the
source code) we should document not only the configure switches but also
key details of the
Matthias Seidel wrote:
But knowing that now one thing comes to my mind:
If we *would* enable permanent redirection to HTTPS for the website, we
may have to exclude http://installation.openoffice.org/description
otherwise it would break the update feed?
No, this is not a problem. It is not a
Dave Fisher wrote:
BTW - Damjan’s changes are javadoc related and absolutely needed on modern Macs
where getting JDK7 is not easy. We cannot be so conservative that we are afraid
of upgrades.
Yes we can. And not only we can, but we should (a personal opinion of
course).
It must be clear
Matthias Seidel wrote:
Am 28.10.2017 um 20:07 schrieb Andrea Pescetti:
You didn't only look around, you committed stuff and I'll now try to
review it. But yes, I confirm that one is the tool we use.
Only small changes for https... I couldn't resist! ;-)
OK, no problem! But as you will see
Dave Fisher wrote:
We ought to factor out the build tooling by comparing a build based on 4.1.3
with the bug to rule out a tooling regression.
Very good suggestion. Building 4.1.3 on exactly the same system and with
exactly the same config used for 4.1.4 will tell us whether this is
related
Matthias Seidel wrote:
Am 26.10.2017 um 22:58 schrieb Andrea Pescetti:
- Enable feeds for 4.1.3 in French, German, Italian (three random
"medium-size" languages) within the next 24 hours.
I was a bit curious and looked around. ;-)
https://svn.apache.org/repos/asf/openoffic
Patricia Shanahan wrote:
Unless the changes are also in 4.1.4 or are super-urgent, I do not think
they belong in 4.1.5. 4.1.5, which we hope will never be released, is
for fixes to 4.1.4 that are too urgent to wait for 4.2.
Confirmed. 4.2 should get all the focus. Nothing gets in AOO415 (which
Peter Kovacs wrote:
Am Samstag, den 28.10.2017, 00:40 +0200 schrieb Andrea Pescetti:
this thread was actually to address the problem with actually
changing release numbers in code, nothing else.
It does not adress the problem with release models. It works only
around them. Is there a bug
Peter Kovacs wrote:
I hope I did not scare anyone with this lengthy explanation now.
No, but it is just off-topic. This is partially my fault since "Managing
branches" in the subject could be read as a proposal for a branching
model. But this is totally not the topic here.
The issue here
Dave Fisher wrote:
I just created a BZ id - dave2w...@comcast.net - would someone grant me PMC
rights.
Use your @apache.org e-mail for the Bugzilla account and you will get
them automatically (of course they can be granted manually too, by a
Bugzilla admin, if you prefer to use a non-ASF
Marcus wrote:
Am 26.10.2017 um 22:23 schrieb Andrea Pescetti:
If we see users confused by the "double update" process we will have
to add an item to the Release Notes.
I don't understand what you want to write to the release notes.
I mean: if we start getting e-mails from people
A short summary of the post-release steps for 4.1.4 I'm going to take
care of, since we are now at the "7 days after release" mark:
1) Security reports for 4.1.4 are now published at
https://www.openoffice.org/security/bulletin.html
Nothing special, the usual handful of fixes we do at every
On 26/10/2017 Marcus wrote:
Am 26.10.2017 um 12:09 schrieb Marco A.G.Pinto:
Now I get an access error in the official page:
http://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice
maybe a temporary outage in the second where you have looked.
I've test now and it's
These two pages
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.4+Announcement
(CWiki Announcement)
and
https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces19
(Press Release)
have some minor differences in text.
The former, probably an intermediate
Kay Schenk wrote:
Would it be more clear to just remove the AOO415 branch and only
re-instate it if needed (hopefully not).
No, it wouldn't. See https://bz.apache.org/ooo/show_bug.cgi?id=127552 -
there is a series of changes that need to be done for the release number
bump. It's better to
I'm starting a short series of occasional posts to capture the current
collective state of mind on the next release. I'll float them here for
refinement or lazy consensus, and then we may want to reuse this text in
wiki or blog posts to avoid repeating the same concepts over and over.
Let's
Odil Soliev wrote:
We are prepare a Tajik hunspell dictionary for OpenOffice. How can we add our
dictionary to OpenOffice distribution?
After you are done with the dictionary (.dic and .aff files), package
them into an extension and upload it to http://extensions.openoffice.org/
You can
Peter kovacs wrote:
How about creating a project plan, estimates for a budget and then start a
campaign?
I think that getting money would not be the hardest part. The hardest
part would be to find people who are trusted and competent enough. The
code is complex and different people have
dennisroczek wrote:
the following page needs an update:
https://www.openoffice.org/security/bulletin.html
We've usually released bulletins about 7 days later than the release
announcement. We are going to do the same for 4.1.4.
Regards,
Andrea.
Gavin McDonald wrote:
On 20 Oct 2017, at 9:40 am, Andrea Pescetti wrote:
There are no build instructions on the CWiki and there shouldn't be a copy
there.
https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds
Bad. I haven't removed that section of the page since I
Marcus wrote:
Am 19.10.2017 um 23:20 schrieb Matthias Seidel:
Unfortunately just today the SSL certificate expired for:
https://extensions.openoffice.org/
and
https://templates.openoffice.org/
People will see an error message when trying to search for updates via
Extension Manager.
Yes, and
On 19/10/2017 Keith N. McKenna wrote:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
To the best of my knowledge the step by step link that I gave you is the
latest revisions.
This is correct. The Building Giude and its specialized versions are
actively
Matthias Seidel wrote:
The main download page, as well as German and Netherlands are updated...
But we still have a bunch of pages to do.
I'll take care of the Italian pages and I'll also put online the
translations I received from our volunteers.
Regards,
Andrea.
Carl Marcum wrote:
If a PMC member cast a vote should it always be counted as binding
whether stated explicitly or not?
Yes, it should. People add "binding" as a shorthand to mean "I am from
the PMC" since a release cannot be approved without reaching 3 votes
from the PMC, and it must be
Pedro Lino wrote:
I agree that it is good that some users replicate the building procedure
and confirm that it works. ...
In any case I couldn't find that particular requirement for a PMC member
in the voting page (https://www.apache.org/foundation/voting.html).
Maybe that is being too strict?
Keith N. McKenna wrote:
Even though he is a PMC member his vote cannot be counted as binding as
he did not build from source as is required by Apache Policy.
This is OK as long as the Apache Policy doesn't get in the way too
much... I mean, I highly appreciate when people provide a list of
Patricia Shanahan wrote:
I am currently considering FOSDEM 2018, but is there a better choice?
No better choice. It is confirmed there will be a Devroom for Open
Document Editors (like OpenOffice) and the call for talks will be sent
very soon.
There will also be a quite crowded ASF booth
On 13/10/2017 Andrea Pescetti wrote:
Our SourceForge area is now updated with files from revision 22458 from
the dev area (this revision includes the rebuilt Linux-64 binaries).
Now updated again to revision 22553 (this one includes the rebuilt OS X
binaries).
As expected, the only modified
Matthias Seidel wrote:
(Later) I would be interested if your changes in the build process would
also apply to the Linux64 builds from trunk.
I'm also very happy to learn this is reported by Jim and Dave to be
fixed in the rebuilt RC5!
And indeed I would be uncomfortable in confirming my +1
On 16/10/2017 Dave Fisher wrote:
with RC5 I see:
(1) I get the little general error dialog.
Can we get an issue in Bugzilla please, so that we can try and make it
reproducible?
What I understood so far is:
1. For some reason this (in RC5) only affects Mac OS X
2. It is NOT specific to
On 16/10/2017 Patricia Shanahan wrote:
I may change my vote based on future information.
Sure, we'll have to keep the vote open until at least we have determined
whether this is an issue with that particular set of binaries or not.
The full rebuild Jim is doing will give the answer. All
Guy Waterval wrote:
I do not know if such a collaboration is allowed
by Apache
No problem. Apache won't pay developers directly, but it doesn't forbid
that developers are paid of course! So whoever is the sponsor, there is
no problem as long as the code is under the Apache License version 2
301 - 400 of 2585 matches
Mail list logo
