You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by "Keith N. McKenna" <ke...@comcast.net> on 2016/10/05 21:35:30 UTC
{Dicuss] [Vote]
Just a procedural Question. How can we be calling for a vote when there
are items in Bugzilla marked as release blockers that are not marked as
fixed?
Regards
Keith
Re: {Dicuss] [Vote]
Posted by Patricia Shanahan <pa...@acm.org>.
They are now marked as fixed.
On 10/5/2016 3:28 PM, Patricia Shanahan wrote:
> I believe, based on my tracking and testing, that the release blockers
> are all fixed. I was hoping the people working on the bugs, especially
> those who requested release_blocker, will update them ASAP.
>
> On 10/5/2016 2:35 PM, Keith N. McKenna wrote:
>> Just a procedural Question. How can we be calling for a vote when there
>> are items in Bugzilla marked as release blockers that are not marked as
>> fixed?
>>
>> Regards
>> Keith
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by Patricia Shanahan <pa...@acm.org>.
I believe, based on my tracking and testing, that the release blockers
are all fixed. I was hoping the people working on the bugs, especially
those who requested release_blocker, will update them ASAP.
On 10/5/2016 2:35 PM, Keith N. McKenna wrote:
> Just a procedural Question. How can we be calling for a vote when there
> are items in Bugzilla marked as release blockers that are not marked as
> fixed?
>
> Regards
> Keith
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by Ariel Constenla-Haile <ar...@apache.org>.
On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:
> Patricia Shanahan wrote:
> > I believe, based on my tracking and testing, that the release blockers
> > are all fixed. I was hoping the people working on the bugs, especially
> > those who requested release_blocker, will update them ASAP.
> >
> I have no doubt that they have been fixed, but they need to be updated
> as we link to a query for them from the Release Notes and what message
> does it give to the world if the Release Notes show Release Blockers as
> still open?
Most of these bugs don't make any sense in the release notes, they are
too aoo-build specific.
Regards
--
Ariel Constenla-Haile
Re: {Dicuss] [Vote]
Posted by Marcus <ma...@wtnet.de>.
Am 10/06/2016 02:33 PM, schrieb Patricia Shanahan:
> On 10/6/2016 5:21 AM, Marcus wrote:
>> Am 10/06/2016 01:52 PM, schrieb Marcus:
> ...
>>> I'll take a look into the issue list, update the release notes with
>>> interesting issues for the average user and keep the full details to the
>>> link of BZ issues.
>>
>> done.
>>
>> I've also added a line for the BZ issue 126622 "Base 4.1.2 does not open
>> Tables and Queries in Mac OSX" that it is no longer occurring.
>
> I hate marking things fixed when they mysteriously disappear, because
> anything that mysteriously disappears can reappear, probably at the
> least convenient possible time.
>
> I think, based on Ariel's comment #28 on
> https://bz.apache.org/ooo/show_bug.cgi?id=126622, that we no longer have
> a mysterious disappearance, but an actual fix:
>
> It is fixed by switching from building on Mac OS X El Capitan with Xcode
> 7 to building on 4.1.3 on macOS Sierra with Xcode 8.
>
> I am going to be offline for several hours starting in about an hour.
> Can you update the release notes to show this?
and done :-)
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: {Dicuss] [Vote] Summary
Posted by "Dennis E. Hamilton" <or...@msn.com>.
+1
Great analysis and working things out: pats, arielch, marcus.
> -----Original Message-----
> From: Patricia Shanahan [mailto:pats@acm.org]
> Sent: Thursday, October 6, 2016 06:00
> To: dev@openoffice.apache.org
> Subject: Re: {Dicuss] [Vote] Summary
>
> This thread has morphed a bit, and I think a summary may be useful at
> this time.
>
> It started with Keith pointing out, correctly, that I was taking a short
> cut by starting the vote before all the relevant bugs had been marked
> "Fixed", although after I was sure they were all fixed in reality. That
> aspect was quickly resolved by Ariel updating the bugs in question. All
> 4.1.3 release blocker bugs are now marked as fixed.
>
> It then shifted into a discussion of what should be in the release
> notes. There are three classes of Bugzilla issues involved:
>
> 1. Fixes affecting the behavior of binaries. Listing these in the
> release notes is non-controversial.
>
> 2. Administrative changes, changing the release number in various
> places.
>
> 3. Fixes to the build systems. Because of the year time lapse since
> 4.1.2, there was an accumulation of issues that affect building in
> various environments.
>
> The question was how to handle the second and third classes. They are
> uninteresting, and in some cases incomprehensible, to the vast majority
> of AOO users. The plan is to only mention "interesting" bugs directly in
> the release notes, but include the URL for a Bugzilla query that shows
> all the fixes.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote] Summary
Posted by Patricia Shanahan <pa...@acm.org>.
This thread has morphed a bit, and I think a summary may be useful at
this time.
It started with Keith pointing out, correctly, that I was taking a short
cut by starting the vote before all the relevant bugs had been marked
"Fixed", although after I was sure they were all fixed in reality. That
aspect was quickly resolved by Ariel updating the bugs in question. All
4.1.3 release blocker bugs are now marked as fixed.
It then shifted into a discussion of what should be in the release
notes. There are three classes of Bugzilla issues involved:
1. Fixes affecting the behavior of binaries. Listing these in the
release notes is non-controversial.
2. Administrative changes, changing the release number in various places.
3. Fixes to the build systems. Because of the year time lapse since
4.1.2, there was an accumulation of issues that affect building in
various environments.
The question was how to handle the second and third classes. They are
uninteresting, and in some cases incomprehensible, to the vast majority
of AOO users. The plan is to only mention "interesting" bugs directly in
the release notes, but include the URL for a Bugzilla query that shows
all the fixes.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by Patricia Shanahan <pa...@acm.org>.
On 10/6/2016 5:21 AM, Marcus wrote:
> Am 10/06/2016 01:52 PM, schrieb Marcus:
...
>> I'll take a look into the issue list, update the release notes with
>> interesting issues for the average user and keep the full details to the
>> link of BZ issues.
>
> done.
>
> I've also added a line for the BZ issue 126622 "Base 4.1.2 does not open
> Tables and Queries in Mac OSX" that it is no longer occurring.
I hate marking things fixed when they mysteriously disappear, because
anything that mysteriously disappears can reappear, probably at the
least convenient possible time.
I think, based on Ariel's comment #28 on
https://bz.apache.org/ooo/show_bug.cgi?id=126622, that we no longer have
a mysterious disappearance, but an actual fix:
It is fixed by switching from building on Mac OS X El Capitan with Xcode
7 to building on 4.1.3 on macOS Sierra with Xcode 8.
I am going to be offline for several hours starting in about an hour.
Can you update the release notes to show this?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by Marcus <ma...@wtnet.de>.
Am 10/06/2016 01:52 PM, schrieb Marcus:
> Am 10/06/2016 05:10 AM, schrieb Patricia Shanahan:
>>
>> On 10/5/2016 5:51 PM, Keith N. McKenna wrote:
>>> Ariel Constenla-Haile wrote:
>>>> On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:
>>>>> Patricia Shanahan wrote:
>>>>>> I believe, based on my tracking and testing, that the release
>>>>>> blockers
>>>>>> are all fixed. I was hoping the people working on the bugs,
>>>>>> especially
>>>>>> those who requested release_blocker, will update them ASAP.
>>>>>>
>>>>> I have no doubt that they have been fixed, but they need to be updated
>>>>> as we link to a query for them from the Release Notes and what message
>>>>> does it give to the world if the Release Notes show Release
>>>>> Blockers as
>>>>> still open?
>>>>
>>>> Most of these bugs don't make any sense in the release notes, they are
>>>> too aoo-build specific.
>>>>
>>>>
>>>> Regards
>>>>
>>> Ariel;
>>>
>>> In all the builds that I have been involved in with AOO we have included
>>> a link to a Bugzilla query for all bugs fixed by that release.My concern
>>> was 2 fold. One that it would give a wrong impression to anyone that
>>> followed the link and the second was to try to keep Bugzilla up to date.
>>>
>>> If it is possible we should construct a query that excludes anything in
>>> Product = Build Tools for the Release Notes.
>>
>> I think calling out the important stuff directly in the release notes
>> but providing a Bugzilla link that shows everything, including tools, is
>> a reasonable compromise. However, I am very open to suggestions for
>> improving the release notes.
>
> that was also my idea. I don't like to hide things as we do open source.
> Fixing problems when building is part of that. And it is not a secret
> that we would have more fixes in the build area than in previous releases.
>
> I'll take a look into the issue list, update the release notes with
> interesting issues for the average user and keep the full details to the
> link of BZ issues.
done.
I've also added a line for the BZ issue 126622 "Base 4.1.2 does not open
Tables and Queries in Mac OSX" that it is no longer occurring.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by Marcus <ma...@wtnet.de>.
Am 10/06/2016 05:10 AM, schrieb Patricia Shanahan:
>
> On 10/5/2016 5:51 PM, Keith N. McKenna wrote:
>> Ariel Constenla-Haile wrote:
>>> On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:
>>>> Patricia Shanahan wrote:
>>>>> I believe, based on my tracking and testing, that the release blockers
>>>>> are all fixed. I was hoping the people working on the bugs, especially
>>>>> those who requested release_blocker, will update them ASAP.
>>>>>
>>>> I have no doubt that they have been fixed, but they need to be updated
>>>> as we link to a query for them from the Release Notes and what message
>>>> does it give to the world if the Release Notes show Release Blockers as
>>>> still open?
>>>
>>> Most of these bugs don't make any sense in the release notes, they are
>>> too aoo-build specific.
>>>
>>>
>>> Regards
>>>
>> Ariel;
>>
>> In all the builds that I have been involved in with AOO we have included
>> a link to a Bugzilla query for all bugs fixed by that release.My concern
>> was 2 fold. One that it would give a wrong impression to anyone that
>> followed the link and the second was to try to keep Bugzilla up to date.
>>
>> If it is possible we should construct a query that excludes anything in
>> Product = Build Tools for the Release Notes.
>
> I think calling out the important stuff directly in the release notes
> but providing a Bugzilla link that shows everything, including tools, is
> a reasonable compromise. However, I am very open to suggestions for
> improving the release notes.
that was also my idea. I don't like to hide things as we do open source.
Fixing problems when building is part of that. And it is not a secret
that we would have more fixes in the build area than in previous releases.
I'll take a look into the issue list, update the release notes with
interesting issues for the average user and keep the full details to the
link of BZ issues.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by Ariel Constenla-Haile <ar...@apache.org>.
On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
> >Ariel;
> >
> >In all the builds that I have been involved in with AOO we have included
> >a link to a Bugzilla query for all bugs fixed by that release.My concern
> >was 2 fold. One that it would give a wrong impression to anyone that
> >followed the link and the second was to try to keep Bugzilla up to date.
> >
> >If it is possible we should construct a query that excludes anything in
> >Product = Build Tools for the Release Notes.
>
> I think calling out the important stuff directly in the release notes but
> providing a Bugzilla link that shows everything, including tools, is a
> reasonable compromise. However, I am very open to suggestions for improving
> the release notes.
IMO yes, there should be a link to the bugzilla query, but it does not
make sense to mention those build-related bugs individually.
Regards
--
Ariel Constenla-Haile
Re: {Dicuss] [Vote]
Posted by Peter Kovacs <le...@gmail.com>.
Cool 22h utca is more then enough for me I hope.
Marcus <ma...@wtnet.de> schrieb am Fr., 7. Okt. 2016, 01:08:
> Am 10/06/2016 11:45 PM, schrieb Peter Kovacs:
>
> > I can only make some time for testing on the 8th Okt. Is that okay if I
> > take my vote on this last moment?
>
> of course, that's the advantage of the time frame. Take your time.
>
> Marcus
>
>
>
> > Keith N. McKenna<ke...@comcast.net> schrieb am Do., 6. Okt.
> 2016,
> > 19:48:
> >
> >> Ariel Constenla-Haile wrote:
> >>> On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
> >>>>> Ariel;
> >>>>>
> >>>>> In all the builds that I have been involved in with AOO we have
> >> included
> >>>>> a link to a Bugzilla query for all bugs fixed by that release.My
> >> concern
> >>>>> was 2 fold. One that it would give a wrong impression to anyone that
> >>>>> followed the link and the second was to try to keep Bugzilla up to
> >> date.
> >>>>>
> >>>>> If it is possible we should construct a query that excludes anything
> in
> >>>>> Product = Build Tools for the Release Notes.
> >>>>
> >>>> I think calling out the important stuff directly in the release notes
> >> but
> >>>> providing a Bugzilla link that shows everything, including tools, is a
> >>>> reasonable compromise. However, I am very open to suggestions for
> >> improving
> >>>> the release notes.
> >>>
> >>> IMO yes, there should be a link to the bugzilla query, but it does not
> >>> make sense to mention those build-related bugs individually.
> >>>
> >>>
> >>> Regards
> >>>
> >> I agree there is no need to highlight those types of bugs individually.
> >> I will remove the individual mention of them from the 4.1.3 Release
> Notes.
> >>
> >> Keith
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
> --
Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.
Re: {Dicuss] [Vote]
Posted by Marcus <ma...@wtnet.de>.
Am 10/06/2016 11:45 PM, schrieb Peter Kovacs:
> I can only make some time for testing on the 8th Okt. Is that okay if I
> take my vote on this last moment?
of course, that's the advantage of the time frame. Take your time.
Marcus
> Keith N. McKenna<ke...@comcast.net> schrieb am Do., 6. Okt. 2016,
> 19:48:
>
>> Ariel Constenla-Haile wrote:
>>> On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
>>>>> Ariel;
>>>>>
>>>>> In all the builds that I have been involved in with AOO we have
>> included
>>>>> a link to a Bugzilla query for all bugs fixed by that release.My
>> concern
>>>>> was 2 fold. One that it would give a wrong impression to anyone that
>>>>> followed the link and the second was to try to keep Bugzilla up to
>> date.
>>>>>
>>>>> If it is possible we should construct a query that excludes anything in
>>>>> Product = Build Tools for the Release Notes.
>>>>
>>>> I think calling out the important stuff directly in the release notes
>> but
>>>> providing a Bugzilla link that shows everything, including tools, is a
>>>> reasonable compromise. However, I am very open to suggestions for
>> improving
>>>> the release notes.
>>>
>>> IMO yes, there should be a link to the bugzilla query, but it does not
>>> make sense to mention those build-related bugs individually.
>>>
>>>
>>> Regards
>>>
>> I agree there is no need to highlight those types of bugs individually.
>> I will remove the individual mention of them from the 4.1.3 Release Notes.
>>
>> Keith
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by Patricia Shanahan <pa...@acm.org>.
No problem. I won't close the vote early.
On 10/6/2016 2:45 PM, Peter Kovacs wrote:
> Hi,
>
> I can only make some time for testing on the 8th Okt. Is that okay if I
> take my vote on this last moment?
>
> Keith N. McKenna <ke...@comcast.net> schrieb am Do., 6. Okt. 2016,
> 19:48:
>
>> Ariel Constenla-Haile wrote:
>>> On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
>>>>> Ariel;
>>>>>
>>>>> In all the builds that I have been involved in with AOO we have
>> included
>>>>> a link to a Bugzilla query for all bugs fixed by that release.My
>> concern
>>>>> was 2 fold. One that it would give a wrong impression to anyone that
>>>>> followed the link and the second was to try to keep Bugzilla up to
>> date.
>>>>>
>>>>> If it is possible we should construct a query that excludes anything in
>>>>> Product = Build Tools for the Release Notes.
>>>>
>>>> I think calling out the important stuff directly in the release notes
>> but
>>>> providing a Bugzilla link that shows everything, including tools, is a
>>>> reasonable compromise. However, I am very open to suggestions for
>> improving
>>>> the release notes.
>>>
>>> IMO yes, there should be a link to the bugzilla query, but it does not
>>> make sense to mention those build-related bugs individually.
>>>
>>>
>>> Regards
>>>
>> I agree there is no need to highlight those types of bugs individually.
>> I will remove the individual mention of them from the 4.1.3 Release Notes.
>>
>> Keith
>>
>> --
>
> Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
> wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
> werbeana�ysen gescannt. Es ist derzeit nicht auszuschlie�en das ihre
> Nachricht auch durch einen NSA Mitarbeiter gepr�ft wird. Durch
> kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
> Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
> konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
> w�nschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
> verhandeln.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by "Keith N. McKenna" <ke...@comcast.net>.
Peter Kovacs wrote:
> Hi,
>
> I can only make some time for testing on the 8th Okt. Is that okay if I
> take my vote on this last moment?
>
As long as it is before 22:00 UTC it should be fine. That is the
earliest that the vote can end.
> Keith N. McKenna <ke...@comcast.net> schrieb am Do., 6. Okt. 2016,
> 19:48:
>
>> Ariel Constenla-Haile wrote:
>>> On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
>>>>> Ariel;
>>>>>
>>>>> In all the builds that I have been involved in with AOO we have
>> included
>>>>> a link to a Bugzilla query for all bugs fixed by that release.My
>> concern
>>>>> was 2 fold. One that it would give a wrong impression to anyone that
>>>>> followed the link and the second was to try to keep Bugzilla up to
>> date.
>>>>>
>>>>> If it is possible we should construct a query that excludes anything in
>>>>> Product = Build Tools for the Release Notes.
>>>>
>>>> I think calling out the important stuff directly in the release notes
>> but
>>>> providing a Bugzilla link that shows everything, including tools, is a
>>>> reasonable compromise. However, I am very open to suggestions for
>> improving
>>>> the release notes.
>>>
>>> IMO yes, there should be a link to the bugzilla query, but it does not
>>> make sense to mention those build-related bugs individually.
>>>
>>>
>>> Regards
>>>
>> I agree there is no need to highlight those types of bugs individually.
>> I will remove the individual mention of them from the 4.1.3 Release Notes.
>>
>> Keith
>>
>> --
>
> Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
> wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
> werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
> Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
> kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
> Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
> konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
> wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
> verhandeln.
>
Re: {Dicuss] [Vote]
Posted by Peter Kovacs <le...@gmail.com>.
Hi,
I can only make some time for testing on the 8th Okt. Is that okay if I
take my vote on this last moment?
Keith N. McKenna <ke...@comcast.net> schrieb am Do., 6. Okt. 2016,
19:48:
> Ariel Constenla-Haile wrote:
> > On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
> >>> Ariel;
> >>>
> >>> In all the builds that I have been involved in with AOO we have
> included
> >>> a link to a Bugzilla query for all bugs fixed by that release.My
> concern
> >>> was 2 fold. One that it would give a wrong impression to anyone that
> >>> followed the link and the second was to try to keep Bugzilla up to
> date.
> >>>
> >>> If it is possible we should construct a query that excludes anything in
> >>> Product = Build Tools for the Release Notes.
> >>
> >> I think calling out the important stuff directly in the release notes
> but
> >> providing a Bugzilla link that shows everything, including tools, is a
> >> reasonable compromise. However, I am very open to suggestions for
> improving
> >> the release notes.
> >
> > IMO yes, there should be a link to the bugzilla query, but it does not
> > make sense to mention those build-related bugs individually.
> >
> >
> > Regards
> >
> I agree there is no need to highlight those types of bugs individually.
> I will remove the individual mention of them from the 4.1.3 Release Notes.
>
> Keith
>
> --
Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort
wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks
werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre
Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch
kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre
Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google
konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht
wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu
verhandeln.
Re: {Dicuss] [Vote]
Posted by "Keith N. McKenna" <ke...@comcast.net>.
Ariel Constenla-Haile wrote:
> On Wed, Oct 05, 2016 at 08:10:40PM -0700, Patricia Shanahan wrote:
>>> Ariel;
>>>
>>> In all the builds that I have been involved in with AOO we have included
>>> a link to a Bugzilla query for all bugs fixed by that release.My concern
>>> was 2 fold. One that it would give a wrong impression to anyone that
>>> followed the link and the second was to try to keep Bugzilla up to date.
>>>
>>> If it is possible we should construct a query that excludes anything in
>>> Product = Build Tools for the Release Notes.
>>
>> I think calling out the important stuff directly in the release notes but
>> providing a Bugzilla link that shows everything, including tools, is a
>> reasonable compromise. However, I am very open to suggestions for improving
>> the release notes.
>
> IMO yes, there should be a link to the bugzilla query, but it does not
> make sense to mention those build-related bugs individually.
>
>
> Regards
>
I agree there is no need to highlight those types of bugs individually.
I will remove the individual mention of them from the 4.1.3 Release Notes.
Keith
Re: {Dicuss] [Vote]
Posted by Patricia Shanahan <pa...@acm.org>.
On 10/5/2016 5:51 PM, Keith N. McKenna wrote:
> Ariel Constenla-Haile wrote:
>> On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:
>>> Patricia Shanahan wrote:
>>>> I believe, based on my tracking and testing, that the release blockers
>>>> are all fixed. I was hoping the people working on the bugs, especially
>>>> those who requested release_blocker, will update them ASAP.
>>>>
>>> I have no doubt that they have been fixed, but they need to be updated
>>> as we link to a query for them from the Release Notes and what message
>>> does it give to the world if the Release Notes show Release Blockers as
>>> still open?
>>
>> Most of these bugs don't make any sense in the release notes, they are
>> too aoo-build specific.
>>
>>
>> Regards
>>
> Ariel;
>
> In all the builds that I have been involved in with AOO we have included
> a link to a Bugzilla query for all bugs fixed by that release.My concern
> was 2 fold. One that it would give a wrong impression to anyone that
> followed the link and the second was to try to keep Bugzilla up to date.
>
> If it is possible we should construct a query that excludes anything in
> Product = Build Tools for the Release Notes.
I think calling out the important stuff directly in the release notes
but providing a Bugzilla link that shows everything, including tools, is
a reasonable compromise. However, I am very open to suggestions for
improving the release notes.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: {Dicuss] [Vote]
Posted by "Keith N. McKenna" <ke...@comcast.net>.
Ariel Constenla-Haile wrote:
> On Wed, Oct 05, 2016 at 07:17:27PM -0400, Keith N. McKenna wrote:
>> Patricia Shanahan wrote:
>>> I believe, based on my tracking and testing, that the release blockers
>>> are all fixed. I was hoping the people working on the bugs, especially
>>> those who requested release_blocker, will update them ASAP.
>>>
>> I have no doubt that they have been fixed, but they need to be updated
>> as we link to a query for them from the Release Notes and what message
>> does it give to the world if the Release Notes show Release Blockers as
>> still open?
>
> Most of these bugs don't make any sense in the release notes, they are
> too aoo-build specific.
>
>
> Regards
>
Ariel;
In all the builds that I have been involved in with AOO we have included
a link to a Bugzilla query for all bugs fixed by that release.My concern
was 2 fold. One that it would give a wrong impression to anyone that
followed the link and the second was to try to keep Bugzilla up to date.
If it is possible we should construct a query that excludes anything in
Product = Build Tools for the Release Notes.
Regards
Keith
Re: {Dicuss] [Vote]
Posted by "Keith N. McKenna" <ke...@comcast.net>.
Patricia Shanahan wrote:
> I believe, based on my tracking and testing, that the release blockers
> are all fixed. I was hoping the people working on the bugs, especially
> those who requested release_blocker, will update them ASAP.
>
I have no doubt that they have been fixed, but they need to be updated
as we link to a query for them from the Release Notes and what message
does it give to the world if the Release Notes show Release Blockers as
still open?
Regards
Keith
> On 10/5/2016 2:35 PM, Keith N. McKenna wrote:
>> Just a procedural Question. How can we be calling for a vote when there
>> are items in Bugzilla marked as release blockers that are not marked as
>> fixed?
>>
>> Regards
>> Keith
>>