RE: [DISCUSS] Release 4.2: General Topics

2016-08-23 Thread Ivajlo Angelov 
PLEASE UNSUBSCRIBE ME FOR ALL APACHE.ORG EMAILS!

-Original Message-
From: Kay sch...@apache.org [mailto:ksch...@apache.org]
Sent: Tuesday, August 23, 2016 10:14 PM
To: AOO Dev Apache
Cc: q...@openoffice.apache.org; l10n@openoffice.apache.org
Subject: [DISCUSS] Release 4.2: General Topics

Hello all--
I think it would be valuable to discuss some general issues/ideas with the 
upcoming 4.2 release. My plan is to keep this general discussion "in play" 
until Sat, Sept 3, then do a summary with what was agreed to.

WARNING: This is quite long!

*PRIORITIES*

1. Update the localization.

We've had quite a bit of work by the localization folks since the 4.1.1 
release. This was the last release, in 2014-08-21 to import localization 
updates. Currently, it seems we might also add 3 new languages: Uyghur, 
Sinhala, and Icelandic with the 4.2 release. This would include both UI 
translations and Help translations.

We need volunteers to lead this endeavor. I, personally, don't know anything 
about this process. This is a very high priority and it would be good to port 
translations over to our main repository as soon as possible for testing.

2. Update Java requirement from Java 1.5 to *at least* Java 1.7

I am rather adamant that we change our building requirement to Java 1.7 for all 
platforms. I will be changing that in our Building Guide today.
Java 1.5 went out of support by Oracle in November, 2009. We use OpenJDK but 
I'm sure updates for Java 1.5 through that channel are also no longer available.
Even Java 1.7 has reached end of life by Oracle for public support as of April, 
2015. To avoid undue issues for some of our current users on older platforms, I 
am "OK" with java 1.7. I am fairly confident ALL users can obtain this for 
whatever platform they are using.

3. Issues for inclusion

We need to include submitted/tested patches since 4.0.x. This should not 
include UI changes which would need to undergo a much longer test period.

The ones I've identified are:


https://bz.apache.org/ooo/buglist.cgi?bug_status=CONFIRMED_status=ACCEPTED_status=REOPENED_status=RESOLVED=product=component=attachments.ispatch=attachments.description=notsubstring=notsubstring=substring=Importance_format=advanced=---=ui=ui=patch=4.0.0=4.0.0-dev=4.0.1=4.0.1-dev=4.1.0=4.1.0-beta=4.1.0-dev=4.1.1=4.1.2=4.1.2-dev=4.2.0-dev

Due to the fact that I actually have trouble identifying patches in BZ, this 
query may not be inclusive, so please feel free to do your own investigation.

Additionally, issue 127068, involving analytics on our source code would surely 
be worth investigating.

https://bz.apache.org/ooo/show_bug.cgi?id=127068

You might also see commits involving code that are related to other issues that 
are not on the above query.

*BUILDBOTS AND CONFIGURATION*

1. Move to different buildbots?

I will be forwarding a communication I had this morning from infrastructure 
concerning our current issues with our buildbots and a possible solution. You 
will see that the Linux32 and Linux64 buildbots are not even the same version 
of Ubuntu. We could move to Ubuntu 14 for both these Linux buildbots where we 
would also have more control over what's installed on them.
We need a volunteer to lead this effort.

2. Configuration Issues
Add, at least the ant version we're checking for in our configuration is not 
the version recommended in our Building Guide.

*PRODUCTION ENVIRONMENT*

For all our past distributions, we've had our own production environment if you 
will. This means the end user binaries were produced on AOO developer 
equipment, and these developers took responsibility for signing the binaries 
and getting them uploaded to SourceForge.  It has been suggested that we use 
the ASF buildbots to produce our binaries with this release. My feeling is that 
unless we can "move" to a new buildbot environment that is more consistent with 
our two Linux distributions, we can'd to this.

The issues with using an AOO production environment vs ASF is this:
* it is much easier to script signing of binaries and move them to SourceForge 
on AOO supplied production equipment.
* if we use ASF buildbot output, the binaries need to be downloaded to some 
other location by developers for signing, computing checksums, etc.
There is no direct shell access to the buildbot machine that I am aware of for 
transfer purposes.

Andrea has volunteered to set up a production environment for us. SEE:
http://markmail.org/message/b4dbjdeu4llczqwt

We need PMC members to volunteer with this effort if we decide to continue with 
the AOO production environment.


--- the end for now --

This is probably enough for now. More coming over the next few days.
--

Kay Schenk
Apache OpenOffice

"Things work out best for those who make  the best of the way things work out."
 -- John Wooden

-
To unsubscribe, e-mail:

[DISCUSS] Release 4.2: General Topics

2016-08-23 Thread Kay sch...@apache.org 
Hello all--
I think it would be valuable to discuss some general issues/ideas with
the upcoming 4.2 release. My plan is to keep this general discussion "in
play" until Sat, Sept 3, then do a summary with what was agreed to.

WARNING: This is quite long!

*PRIORITIES*

1. Update the localization.

We've had quite a bit of work by the localization folks since the 4.1.1
release. This was the last release, in 2014-08-21 to import localization
updates. Currently, it seems we might also add 3 new languages: Uyghur,
Sinhala, and Icelandic with the 4.2 release. This would include both UI
translations and Help translations.

We need volunteers to lead this endeavor. I, personally, don't know
anything about this process. This is a very high priority and it would
be good to port translations over to our main repository as soon as
possible for testing.

2. Update Java requirement from Java 1.5 to *at least* Java 1.7

I am rather adamant that we change our building requirement to Java 1.7
for all platforms. I will be changing that in our Building Guide today.
Java 1.5 went out of support by Oracle in November, 2009. We use OpenJDK
but I'm sure updates for Java 1.5 through that channel are also no
longer available.
Even Java 1.7 has reached end of life by Oracle for public support as of
April, 2015. To avoid undue issues for some of our current users on
older platforms, I am "OK" with java 1.7. I am fairly confident ALL
users can obtain this for whatever platform they are using.

3. Issues for inclusion

We need to include submitted/tested patches since 4.0.x. This should not
include UI changes which would need to undergo a much longer test period.

The ones I've identified are:


https://bz.apache.org/ooo/buglist.cgi?bug_status=CONFIRMED_status=ACCEPTED_status=REOPENED_status=RESOLVED=product=component=attachments.ispatch=attachments.description=notsubstring=notsubstring=substring=Importance_format=advanced=---=ui=ui=patch=4.0.0=4.0.0-dev=4.0.1=4.0.1-dev=4.1.0=4.1.0-beta=4.1.0-dev=4.1.1=4.1.2=4.1.2-dev=4.2.0-dev

Due to the fact that I actually have trouble identifying patches in BZ,
this query may not be inclusive, so please feel free to do your own
investigation.

Additionally, issue 127068, involving analytics on our source code would
surely be worth investigating.

https://bz.apache.org/ooo/show_bug.cgi?id=127068

You might also see commits involving code that are related to other
issues that are not on the above query.

*BUILDBOTS AND CONFIGURATION*

1. Move to different buildbots?

I will be forwarding a communication I had this morning from
infrastructure concerning our current issues with our buildbots and a
possible solution. You will see that the Linux32 and Linux64 buildbots
are not even the same version of Ubuntu. We could move to Ubuntu 14 for
both these Linux buildbots where we would also have more control over
what's installed on them.
We need a volunteer to lead this effort.

2. Configuration Issues
Add, at least the ant version we're checking for in our configuration is
not the version recommended in our Building Guide.

*PRODUCTION ENVIRONMENT*

For all our past distributions, we've had our own production environment
if you will. This means the end user binaries were produced on AOO
developer equipment, and these developers took responsibility for
signing the binaries and getting them uploaded to SourceForge.  It has
been suggested that we use the ASF buildbots to produce our binaries
with this release. My feeling is that unless we can "move" to a new
buildbot environment that is more consistent with our two Linux
distributions, we can'd to this.

The issues with using an AOO production environment vs ASF is this:
* it is much easier to script signing of binaries and move them to
SourceForge on AOO supplied production equipment.
* if we use ASF buildbot output, the binaries need to be downloaded to
some other location by developers for signing, computing checksums, etc.
There is no direct shell access to the buildbot machine that I am aware
of for transfer purposes.

Andrea has volunteered to set up a production environment for us. SEE:
http://markmail.org/message/b4dbjdeu4llczqwt

We need PMC members to volunteer with this effort if we decide to
continue with the AOO production environment.


--- the end for now --

This is probably enough for now. More coming over the next few days.
-- 

Kay Schenk
Apache OpenOffice

"Things work out best for those who make
 the best of the way things work out."
 -- John Wooden

-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org

Re: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-patch1 Hotfixes

2016-08-23 Thread Marcus 

Am 08/23/2016 08:08 PM, schrieb Dennis E. Hamilton:

[BCC PMC, FYI QA and L10N]

There have been no comments concerning the placement of the current materials 
into general distribution.

In addition, there is a set of Dutch (Nederland) language that also passes all 
tests and has been carefully proof-read.  These have been added to the 
directory folder.  (They are not reflected in the hotfix.html so far.)


I would prefer to have an own webpage for all languages. Otherwise we 
will have a hugh webpage for a little patch which isn't looking smart IMHO.



A set of German (Deutsch) language scripts has been prepared and had to be changed 
from Unicode (UTF8) to ISO 8859-1 (Western European) in order to run properly on 
Windows XP.  The script window does not show extended characters used in German on an 
English Windows XP, but the scripts run correctly.  They should appear correctly in 
Windows XP installs set for Western European languages.  This part remains to be 
confirmed.  See.

If the German version is not complete today, I propose going ahead with the 
general distribution of the English and Dutch ones and adding the German set 
later.


German won't be ready in the next hours but hopefuĺly within this week. 
So, we should go online with the stuff we have.


Marcus




-Original Message-
From: Dennis E. Hamilton [mailto:orc...@apache.org]
Sent: Friday, August 19, 2016 15:02
To: d...@openoffice.apache.org
Subject: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-
patch1 Hotfixes

[BCC PMC, FYI QA]

At this time, the preparation and dev@/qa@ confirmation of the AOO
4.1.2-patch1 Hotfixes has quieted.

I propose that the current binaries be placed into general availability.
I am initiating lazy consensus to end not before Tuesday, 2016-08-
23T22:00Z.

MATERIALS TO BE AVAILABLE

  * The file hotfix.html at

will be made available at


  * The directory folder

will be made available as a subdirectory of
.

ANNOUNCEMENT OF AVAILABILITY

   * The CVE-2016-1513 advisory,
 ,
 will be reissued to include availability of the hotfix and
 refer users to the hotfix.html page in the archive 4.1.2-patch1
 location.

   * There will be an accompanying announcement on dev@, users@,
 and in the two bugzilla issues related to the defect that the
 hotfix applies to.

WHAT TO REVIEW

You can find everything to be made available by starting with the
hotfix.html page at
.

IGNORE the Source column.  The source release has already occurred, and
those links will not be valid until deployment of hotfix.html to the
archive location.

The README files are the next materials to examine.  There you can learn
more about the hotfix for each of the four platforms: Windows, MacOSX,
Linux32, and Linux64.  Follow any of the procedures that you want to
verify.


-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org

RE: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-patch1 Hotfixes

2016-08-23 Thread Dennis E. Hamilton 
[BCC PMC, FYI QA and L10N]

There have been no comments concerning the placement of the current materials 
into general distribution.

In addition, there is a set of Dutch (Nederland) language that also passes all 
tests and has been carefully proof-read.  These have been added to the 
directory folder.  (They are not reflected in the hotfix.html so far.)

A set of German (Deutsch) language scripts has been prepared and had to be 
changed from Unicode (UTF8) to ISO 8859-1 (Western European) in order to run 
properly on Windows XP.  The script window does not show extended characters 
used in German on an English Windows XP, but the scripts run correctly.  They 
should appear correctly in Windows XP installs set for Western European 
languages.  This part remains to be confirmed.  See 
.

If the German version is not complete today, I propose going ahead with the 
general distribution of the English and Dutch ones and adding the German set 
later.

 - Dennis



> -Original Message-
> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> Sent: Friday, August 19, 2016 15:02
> To: d...@openoffice.apache.org
> Subject: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-
> patch1 Hotfixes
> 
> [BCC PMC, FYI QA]
> 
> At this time, the preparation and dev@/qa@ confirmation of the AOO
> 4.1.2-patch1 Hotfixes has quieted.
> 
> I propose that the current binaries be placed into general availability.
> I am initiating lazy consensus to end not before Tuesday, 2016-08-
> 23T22:00Z.
> 
> MATERIALS TO BE AVAILABLE
> 
>  * The file hotfix.html at
>
>will be made available at
>
> 
>  * The directory folder
> patch1/binaries/>
>will be made available as a subdirectory of
>.
> 
> ANNOUNCEMENT OF AVAILABILITY
> 
>   * The CVE-2016-1513 advisory,
> ,
> will be reissued to include availability of the hotfix and
> refer users to the hotfix.html page in the archive 4.1.2-patch1
> location.
> 
>   * There will be an accompanying announcement on dev@, users@,
> and in the two bugzilla issues related to the defect that the
> hotfix applies to.
> 
> WHAT TO REVIEW
> 
> You can find everything to be made available by starting with the
> hotfix.html page at
>  patch1/hotfix.html>.
> 
> IGNORE the Source column.  The source release has already occurred, and
> those links will not be valid until deployment of hotfix.html to the
> archive location.
> 
> The README files are the next materials to examine.  There you can learn
> more about the hotfix for each of the four platforms: Windows, MacOSX,
> Linux32, and Linux64.  Follow any of the procedures that you want to
> verify.
> 
> 
>  - Dennis
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org