Blog post: update on OpenOffice 4.1.2 status

[Andrea Pescetti]

A long overdue blog post on the 4.1.2 status is now online:
https://blogs.apache.org/OOo/entry/coming_soon_apache_openoffice_4

I regret that our tools do not really allow to review a post before 
publishing it, but if there is anything to be fixed/modify just note it 
here and I will fix it.


The Wiki page
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2
has also been updated accordingly (Kay, do you have a simple way to 
produce updated Bugzilla searches to list in that wiki page? There are 
still the 4.1.1 ones, but they should be replaced).


In short:
- Most of the code changes are already in the AOO410 branch.
- I will update the SNAPSHOT tag in a few hours
- It is time to focus on QA and final preparations

By final preparations I mean press release, release notes and website.

Do you think we should update the site headline to point to that blog 
post? At least we would give visibility to what we have been doing recently.


Regards,
  Andrea.

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

4.1.2_release_blocker requested: [Issue 124158] Update CoinMP

[bugzilla]

Andrea Pescetti  has asked  for 4.1.2_release_blocker:
Issue 124158: Update CoinMP
https://bz.apache.org/ooo/show_bug.cgi?id=124158



--- Comment #8 from Andrea Pescetti  ---
For tracking: pfg has now committed this patch to the AOO410 branch.

Based on the above discussion, this actually seems a good thing to do, but
still we want to preserve information on release blockers. This will require
some specific testing in the QA phase.

For reference, the merge commit is
http://svn.apache.org/r1705549
which also contains other portions that will have to be quickly validated on
the dev list.

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

Re: Blog post: update on OpenOffice 4.1.2 status

[Kay Schenk]

On 09/27/2015 07:35 AM, Andrea Pescetti wrote:
> A long overdue blog post on the 4.1.2 status is now online:
> https://blogs.apache.org/OOo/entry/coming_soon_apache_openoffice_4
> 

A nice blog.

> 
> I regret that our tools do not really allow to review a post
> before publishing it, but if there is anything to be
> fixed/modify just note it here and I will fix it.
> 
> The Wiki page
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2
> has also been updated accordingly (Kay, do you have a simple
> way to produce updated Bugzilla searches to list in that
> wiki page? There are still the 4.1.1 ones, but they should
> be replaced).

re BZ: I will work on this today. I was trying to do that a
week or so ago, but couldn't find a way to deal with
tracking by "Flag".

> 
> In short:
> - Most of the code changes are already in the AOO410 branch.
> - I will update the SNAPSHOT tag in a few hours
> - It is time to focus on QA and final preparations
> 
> By final preparations I mean press release, release notes
> and website.

When can we get actual RCs/test builds to use? Since the
"win" buildbot is still having issues, even you reset
SNAPSHOT, we will only have a few Linux builds to use for
testing.

> 
> Do you think we should update the site headline to point to
> that blog post? At least we would give visibility to what we
> have been doing recently.

We could do that. But I would feel better if we had test
build available first.

> 
> Regards,
>   Andrea.
> 



-- 

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

Re: Merging some FreeBSD changes to AOO410 (was Re: AOO build system upgrades)

[Andrea Pescetti]

On 25/09/2015 Pedro Giffuni wrote:

I think it may be desireable to upgrade coinmp in AOO410 and with that
we would solve the issues for people(/buildbots) doing complete builds.


I see you have just committed this to AOO410, but remember: we are not 
freely committing to AOO410 at the moment (even though it seems indeed 
desirable to upgrade CoinMP, so it was correct that you did so).


Can you please provide explanations of the different merges from
http://svn.apache.org/viewvc?view=revision=1705549 ?

Especially I don't find any background for this one:
http://svn.apache.org/viewvc?view=revision=1647713
Make sure system LAPACK/BLAS are never used
(the rest seems OK).


OTOH, my instinct tells me we could just avoid risks and leave things
as they are right now.


Yes, that's also my instinct and my preference. We got a large number of 
fixes in during the last few days, and now let's take the time to check 
that things work, and be careful before committing to AOO410.



Andrea, is the FreeBSD buildbot going to be
re-targeting AOO410 too?


It depends on its configuration. I assume it follows trunk. What I will 
do (when ready) is to move the SNAPSHOT tag to track a recent AOO410 
commit. Buildbots that track SNAPSHOT will thus immediately switch to 
AOO410.


Regards,
  Andrea.

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

Re: Blog post: update on OpenOffice 4.1.2 status

[Andrea Pescetti]

On 27/09/2015 Kay Schenk wrote:

re BZ: I will work on this today. I was trying to do that a
week or so ago, but couldn't find a way to deal with
tracking by "Flag".


In Bugzilla's Advanced search (this answers the question from Marcus 
too) one can do a "Custom Search" for "Flags" - "contains the string" - 
"4.1.2_release_blocker" and the system will show a list of bugs fixed or 
proposed for 4.1.2.



When can we get actual RCs/test builds to use? Since the
"win" buildbot is still having issues, even you reset
SNAPSHOT, we will only have a few Linux builds to use for
testing.


This is true for the buildbots. But probably our best option is NOT to 
use the buildbots for 4.1.2; if we manage to get snapshots from the same 
hardware used to build 4.1.1 it would be perfect. Let's see.


Note: while the current snapshot is probably not the final 4.1.2 
release, it is quite close. Most of the code changes are already in and 
are ready for testing. I expect that the next snapshot (no estimated 
date) will be our Release Candidate.



Do you think we should update the site headline to point to
that blog post? At least we would give visibility to what we
have been doing recently.

We could do that. But I would feel better if we had test
build available first.


Maybe we can wait a couple days, but I'd rather get volunteers first and 
builds later. Users will also appreciate to know that 4.1.2 is coming 
soon: we didn't give it any visibility except for this mailing list and 
the CWiki so far, and it was a mistake.


Regards,
  Andrea.

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

SNAPSHOT tag updated

[Andrea Pescetti]

The SNAPSHOT tag has now been updated to the latest (for the time being) 
revision of the AOO410 branch:

https://svn.apache.org/viewvc/openoffice/tags/

The buildbots that are configured to track SNAPSHOT will thus build 
OpenOffice 4.1.2 starting from now (actually if anybody knows how to 
force a build it would be good to do so, and document it).


As Kay noted, Widnows buildbots may not be ready yet to ship development 
versions due to https://issues.apache.org/jira/browse/INFRA-10481 but we 
are getting on track.


Regards,
  Andrea.

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

Release Notes work -- AOO 4.1.2 issues/other inclusions

[Kay Schenk]

For those wishing to help with the Release Notes for 4.1.2,
here is what I have identified as issues that got approved
for 4.1.2. It is likely that not all approved issues have
actually been committed to the AOO410 trunk. But I think
there are less than 5 of these to be sure.

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=run=4.1.2_approved_and_fixed_id=7

There have been other commits to the 4.1.2 release which are
not tracked in BZ. We will try to identify those soon, and
update THIS thread so everything is in one place.

Thanks for all your help on this.

-- 

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

Re: Blog post: update on OpenOffice 4.1.2 status

[Kay Schenk]

On 09/27/2015 03:19 PM, Andrea Pescetti wrote:
> On 27/09/2015 Kay Schenk wrote:
>> re BZ: I will work on this today. I was trying to do that a
>> week or so ago, but couldn't find a way to deal with
>> tracking by "Flag".
> 
> In Bugzilla's Advanced search (this answers the question
> from Marcus too) one can do a "Custom Search" for "Flags" -
> "contains the string" - "4.1.2_release_blocker" and the
> system will show a list of bugs fixed or proposed for 4.1.2.

Ok, I finally got on with this. There was one little
additional trick.

> 
>> When can we get actual RCs/test builds to use? Since the
>> "win" buildbot is still having issues, even you reset
>> SNAPSHOT, we will only have a few Linux builds to use for
>> testing.
> 
> This is true for the buildbots. But probably our best option
> is NOT to use the buildbots for 4.1.2; if we manage to get
> snapshots from the same hardware used to build 4.1.1 it
> would be perfect. Let's see.

Sure. This makes sense. Hopefully the SNAPSHOTS will emerge
soon. :)

> 
> Note: while the current snapshot is probably not the final
> 4.1.2 release, it is quite close. Most of the code changes
> are already in and are ready for testing. I expect that the
> next snapshot (no estimated date) will be our Release
> Candidate.
> 
>>> Do you think we should update the site headline to point to
>>> that blog post? At least we would give visibility to what we
>>> have been doing recently.
>> We could do that. But I would feel better if we had test
>> build available first.
> 
> Maybe we can wait a couple days, but I'd rather get
> volunteers first and builds later. Users will also
> appreciate to know that 4.1.2 is coming soon: we didn't give
> it any visibility except for this mailing list and the CWiki
> so far, and it was a mistake.

Well this is certainly a good point.

> 
> Regards,
>   Andrea.
> 
> -
> 
> 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



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

Re: [CWiki] Account Whitelisting

[Andrea Pescetti]

Lalith Ramesh wrote:

Please try again.  I just created an account on the Confluence Wiki.


Thanks! Your account lalithramesh312 is now whitelisted.

Andrea

-
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

[Andrea Pescetti]

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=run=4.1.2_approved_and_fixed_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

Re: Blog post: update on OpenOffice 4.1.2 status

[Marcus]

Am 09/27/2015 04:35 PM, schrieb Andrea Pescetti:

A long overdue blog post on the 4.1.2 status is now online:
https://blogs.apache.org/OOo/entry/coming_soon_apache_openoffice_4


thanks


I regret that our tools do not really allow to review a post before
publishing it, but if there is anything to be fixed/modify just note it
here and I will fix it.

The Wiki page
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2
has also been updated accordingly (Kay, do you have a simple way to
produce updated Bugzilla searches to list in that wiki page? There are
still the 4.1.1 ones, but they should be replaced).

In short:
- Most of the code changes are already in the AOO410 branch.
- I will update the SNAPSHOT tag in a few hours
- It is time to focus on QA and final preparations

By final preparations I mean press release, release notes and website.


Is there a rough list of bugfixes that can be formed into complete 
sentences in the release notes?



Do you think we should update the site headline to point to that blog
post? At least we would give visibility to what we have been doing
recently.


Sure, it would help to get more attention. But - as Kay mentioned it 
already - the downloading the builds need to the ready and for that the 
Win buildbot.


Marcus


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

Re: 4.1.2_release_blocker granted: [Issue 125613] Insert Picture from file do not work

[Andrea Pescetti]

Regina Henschel wrote:

it would be nice, if you will merge it. I have not committed to branches
and fell uneasy.


Done. All you need to do, for the record, is to be in an AOO410 checkout 
and run


$ svn merge -c 1650314 
https://svn.apache.org/repos/asf/openoffice/trunk/main main


This merges commit 1650314 into AOO410; svn commit takes care of doing 
all the right things, including the merge information.


Regards,
  Andrea.

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