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
