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/13 18:18:35 UTC

Bugzilla needs version 4.1.3 added

With the announcement of the Release of version 4.1.3 that revision
should be added to Bugzilla so that bugs can be reported against it.
Currently only 4.1.3-dev is active and for latest confirmation on the
latest available is 4.1.2

Regards
Keith


Re: Bugzilla needs version 4.1.3 added

Posted by Damjan Jovanovic <da...@apache.org>.
On Thu, Oct 20, 2016 at 8:05 PM, Marcus <ma...@wtnet.de> wrote:

> Am 10/20/2016 02:48 AM, schrieb Damjan Jovanovic:
>
>> Also what happened to 4.2.0-dev in the "Latest confirmation in:"  field?
>>
>
> do we want to have dev-builds in this field? These builds are changing day
> for day when using the install files from the build bots.
>
> IMHO it doesn't make sense to be able to choose them as we then need to
> ask everytime: Which x.y.z-dev version has been used?
>
> My 2 ct.
>
>
>
Then I guess we should release more often - and release from closer to
trunk :-)

Re: Bugzilla needs version 4.1.3 added

Posted by Marcus <ma...@wtnet.de>.
Am 10/21/2016 12:26 AM, schrieb Pedro:
> On 20/10/2016 19:05, Marcus wrote:
>> Am 10/20/2016 02:48 AM, schrieb Damjan Jovanovic:
>>> Also what happened to 4.2.0-dev in the "Latest confirmation in:" field?
>>
>> do we want to have dev-builds in this field? These builds are changing
>> day for day when using the install files from the build bots.
>
> So if someone does use a master build (currently 4.2.0) and finds a bug
> which version should be reported?
> If people are not supposed to report bugs for daily builds what is the
> point of having them uploaded to a public server?
> If the goal of the buildbots is only to test if it is buildable, then
> they only need to report success/failure.
>
> Actually they are not changing daily... There hasn't been a successful
> daily build (at least for Windows) for over a month (master or 4.1.x)
>
>> IMHO it doesn't make sense to be able to choose them as we then need
>> to ask everytime: Which x.y.z-dev version has been used?
>
> People using daily builds are wise enough to report the Rev number (that
> is why it is a selectable text in the About dialog). Day-to-day users
> don't care about unstable daily builds and wouldn't install them anyway.

all corect. For this we have the "4.2.0-dev" item in the "Version" 
field. However, I think it doesn't make sense to offer "...-dev" items 
in the "Latest confirmation in" field.

Marcus


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


Re: Bugzilla needs version 4.1.3 added

Posted by Pedro <pe...@openmailbox.org>.
On 20/10/2016 19:05, Marcus wrote:
> Am 10/20/2016 02:48 AM, schrieb Damjan Jovanovic:
>> Also what happened to 4.2.0-dev in the "Latest confirmation in:"  field?
>
> do we want to have dev-builds in this field? These builds are changing 
> day for day when using the install files from the build bots.

So if someone does use a master build (currently 4.2.0) and finds a bug 
which version should be reported?
If people are not supposed to report bugs for daily builds what is the 
point of having them uploaded to a public server?
If the goal of the buildbots is only to test if it is buildable, then 
they only need to report success/failure.

Actually they are not changing daily... There hasn't been a successful 
daily build (at least for Windows) for over a month (master or 4.1.x)

> IMHO it doesn't make sense to be able to choose them as we then need 
> to ask everytime: Which x.y.z-dev version has been used?

People using daily builds are wise enough to report the Rev number (that 
is why it is a selectable text in the About dialog). Day-to-day users 
don't care about unstable daily builds and wouldn't install them anyway.

Just my 2 cents.

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


Re: Bugzilla needs version 4.1.3 added

Posted by Marcus <ma...@wtnet.de>.
Am 10/20/2016 02:48 AM, schrieb Damjan Jovanovic:
> Also what happened to 4.2.0-dev in the "Latest confirmation in:"  field?

do we want to have dev-builds in this field? These builds are changing 
day for day when using the install files from the build bots.

IMHO it doesn't make sense to be able to choose them as we then need to 
ask everytime: Which x.y.z-dev version has been used?

My 2 ct.

Marcus



> On Thu, Oct 13, 2016 at 8:18 PM, Keith N. McKenna<keith.mckenna@comcast.net
>> wrote:
>
>> With the announcement of the Release of version 4.1.3 that revision
>> should be added to Bugzilla so that bugs can be reported against it.
>> Currently only 4.1.3-dev is active and for latest confirmation on the
>> latest available is 4.1.2

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


Re: Bugzilla needs version 4.1.3 added

Posted by Damjan Jovanovic <da...@apache.org>.
Also what happened to 4.2.0-dev in the "Latest confirmation in:"  field?


On Thu, Oct 13, 2016 at 8:18 PM, Keith N. McKenna <keith.mckenna@comcast.net
> wrote:

> With the announcement of the Release of version 4.1.3 that revision
> should be added to Bugzilla so that bugs can be reported against it.
> Currently only 4.1.3-dev is active and for latest confirmation on the
> latest available is 4.1.2
>
> Regards
> Keith
>
>

Re: Bugzilla needs version 4.1.3 added

Posted by Marcus <ma...@wtnet.de>.
Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
> With the announcement of the Release of version 4.1.3 that revision
> should be added to Bugzilla so that bugs can be reported against it.
> Currently only 4.1.3-dev is active and for latest confirmation on the
> latest available is 4.1.2

right, I'll do this as next task. However, this needs definetely added 
as important task to the cookbook. Will you do this?

https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release

You just need to add some text. Don't care about formatting or order. We 
will do this later when everything (hopefully ;-) ) is there.

Hey, it's a great idea when you would coordinate the creation of this 
cookbook. Then you learn more about the whole process, can add opinions 
from your point of view, etc.

What do you think?

Thanks

Marcus


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


Re: Bugzilla needs version 4.1.3 added

Posted by Marcus <ma...@wtnet.de>.
Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
> Marcus wrote:
>> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
>>> With the announcement of the Release of version 4.1.3 that revision
>>> should be added to Bugzilla so that bugs can be reported against it.
>>> Currently only 4.1.3-dev is active and for latest confirmation on the
>>> latest available is 4.1.2
>>
>> right, I'll do this as next task. However, this needs definetely added
>> as important task to the cookbook. Will you do this?
>>
> Done

and BZ is also updated. :-)

Marcus



>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>
>> You just need to add some text. Don't care about formatting or order. We
>> will do this later when everything (hopefully ;-) ) is there.
>>
>> Hey, it's a great idea when you would coordinate the creation of this
>> cookbook. Then you learn more about the whole process, can add opinions
>> from your point of view, etc.
>>
>> What do you think?

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


Re: Bugzilla needs version 4.1.3 added

Posted by Matthias Seidel <ma...@hamburg.de>.
+1 ;-)


Am 14.10.2016 um 01:19 schrieb Keith N. McKenna:
> Marcus wrote:
>> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>>> Marcus wrote:
>>>> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
>>>>> With the announcement of the Release of version 4.1.3 that revision
>>>>> should be added to Bugzilla so that bugs can be reported against it.
>>>>> Currently only 4.1.3-dev is active and for latest confirmation on the
>>>>> latest available is 4.1.2
>>>> right, I'll do this as next task. However, this needs definetely added
>>>> as important task to the cookbook. Will you do this?
>>>>
>>> Done
>> and BZ is also updated. :-)
>>
> The version drop down list for the Latest Confirmation In field also
> needs to be updated with 4.1.3.
>
> Keith
>
>> Marcus
>>
>>
>>
>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>>
>>>>
>>>> You just need to add some text. Don't care about formatting or order. We
>>>> will do this later when everything (hopefully ;-) ) is there.
>>>>
>>>> Hey, it's a great idea when you would coordinate the creation of this
>>>> cookbook. Then you learn more about the whole process, can add opinions
>>>> from your point of view, etc.
>>>>
>>>> What do you think?
>



Re: Bugzilla needs version 4.1.3 added

Posted by Marcus <ma...@wtnet.de>.
Am 10/14/2016 01:19 AM, schrieb Keith N. McKenna:
> Marcus wrote:
>> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>>> Marcus wrote:
>>>> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
>>>>> With the announcement of the Release of version 4.1.3 that revision
>>>>> should be added to Bugzilla so that bugs can be reported against it.
>>>>> Currently only 4.1.3-dev is active and for latest confirmation on the
>>>>> latest available is 4.1.2
>>>>
>>>> right, I'll do this as next task. However, this needs definetely added
>>>> as important task to the cookbook. Will you do this?
>>>>
>>> Done
>>
>> and BZ is also updated. :-)
>>
>
> The version drop down list for the Latest Confirmation In field also
> needs to be updated with 4.1.3.

ACK, done.

Marcus



>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>>
>>>>
>>>> You just need to add some text. Don't care about formatting or order. We
>>>> will do this later when everything (hopefully ;-) ) is there.
>>>>
>>>> Hey, it's a great idea when you would coordinate the creation of this
>>>> cookbook. Then you learn more about the whole process, can add opinions
>>>> from your point of view, etc.
>>>>
>>>> What do you think?

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


Re: Bugzilla needs version 4.1.3 added

Posted by "Keith N. McKenna" <ke...@comcast.net>.
Marcus wrote:
> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>> Marcus wrote:
>>> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
>>>> With the announcement of the Release of version 4.1.3 that revision
>>>> should be added to Bugzilla so that bugs can be reported against it.
>>>> Currently only 4.1.3-dev is active and for latest confirmation on the
>>>> latest available is 4.1.2
>>>
>>> right, I'll do this as next task. However, this needs definetely added
>>> as important task to the cookbook. Will you do this?
>>>
>> Done
> 
> and BZ is also updated. :-)
> 

The version drop down list for the Latest Confirmation In field also
needs to be updated with 4.1.3.

Keith

> Marcus
> 
> 
> 
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>
>>>
>>> You just need to add some text. Don't care about formatting or order. We
>>> will do this later when everything (hopefully ;-) ) is there.
>>>
>>> Hey, it's a great idea when you would coordinate the creation of this
>>> cookbook. Then you learn more about the whole process, can add opinions
>>> from your point of view, etc.
>>>
>>> What do you think?



Re: [RELEASE COOKBOOK] Adding and structuring the content

Posted by Marcus <ma...@wtnet.de>.
Am 10/15/2016 10:44 AM, schrieb Patricia Shanahan:
>
> On 10/15/2016 1:43 AM, Marcus wrote:
>> Am 10/14/2016 12:11 AM, schrieb Keith N. McKenna:
>>> Marcus wrote:
>>>> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>>>>
>>>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>>>>
>>>>>>
>>>>>>
>>>>>> You just need to add some text. Don't care about formatting or
>>>>>> order. We
>>>>>> will do this later when everything (hopefully ;-) ) is there.
>>>>>>
>>>>>> Hey, it's a great idea when you would coordinate the creation of this
>>>>>> cookbook. Then you learn more about the whole process, can add
>>>>>> opinions
>>>>>> from your point of view, etc.
>>>>>>
>>>>>> What do you think?
>>> Great. Thanks Marcus.
>>
>> just to let you know:
>> I've added a lot of stuff and added also some structure and formatting.
>> But just to not loose the overview. ;-)
>>
>> Of course this doesn't mean that this structure has to be used. We are
>> still free to change where it is necessary or looks better.
>
> I'm doing a little editing right now, and it looks good to me at least
> as an interim structure.

great, for the moment I'm done.

Marcus

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


Re: [RELEASE COOKBOOK] Adding and structuring the content

Posted by Patricia Shanahan <pa...@acm.org>.
On 10/15/2016 1:43 AM, Marcus wrote:
> Am 10/14/2016 12:11 AM, schrieb Keith N. McKenna:
>> Marcus wrote:
>>> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>>>
>>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>>>
>>>>>
>>>>> You just need to add some text. Don't care about formatting or
>>>>> order. We
>>>>> will do this later when everything (hopefully ;-) ) is there.
>>>>>
>>>>> Hey, it's a great idea when you would coordinate the creation of this
>>>>> cookbook. Then you learn more about the whole process, can add
>>>>> opinions
>>>>> from your point of view, etc.
>>>>>
>>>>> What do you think?
>> Great. Thanks Marcus.
>
> just to let you know:
> I've added a lot of stuff and added also some structure and formatting.
> But just to not loose the overview. ;-)
>
> Of course this doesn't mean that this structure has to be used. We are
> still free to change where it is necessary or looks better.

I'm doing a little editing right now, and it looks good to me at least 
as an interim structure.


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


Re: [RELEASE COOKBOOK] Adding and structuring the content

Posted by Marcus <ma...@wtnet.de>.
Am 10/15/2016 11:18 AM, schrieb J�rg Schmidt:
>
> I can see that the English press release is to be published in the blog.
>
> questions:
> ----------
> 1. Is it really only published there? Is there no press distributor(*) at the ASF?
>
> (*) in german: "Presseverteiler"

I pretty sure it was not only a blog post but also a mail to several 
press agencies and similar recipients.

This is managed by Sally as current ASF press representative. To be sure 
you can ask her to get the answer you want. AFAIK we don't know these 
details.

> 2. Where will the translated press releases be published?
> Imho:
> in the wiki and they should be linked to the local pages (for example http://www.openoffice.org/en/)

It depends on what we want. But the work done for the 4.1.3 
announcements seems to me a good step forward to a solution.

Marcus


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


Re: [RELEASE COOKBOOK] Adding and structuring the content

Posted by Jörg Schmidt <jo...@j-m-schmidt.de>.
I can see that the English press release is to be published in the blog.

questions:
----------
1. Is it really only published there? Is there no press distributor(*) at the ASF?

(*) in german: "Presseverteiler" 


2. Where will the translated press releases be published?
Imho: 
in the wiki and they should be linked to the local pages (for example http://www.openoffice.org/en/)


Jörg



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


[RELEASE COOKBOOK] Adding and structuring the content

Posted by Marcus <ma...@wtnet.de>.
Am 10/14/2016 12:11 AM, schrieb Keith N. McKenna:
> Marcus wrote:
>> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>>
>>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>>
>>>> You just need to add some text. Don't care about formatting or order. We
>>>> will do this later when everything (hopefully ;-) ) is there.
>>>>
>>>> Hey, it's a great idea when you would coordinate the creation of this
>>>> cookbook. Then you learn more about the whole process, can add opinions
>>>> from your point of view, etc.
>>>>
>>>> What do you think?
> Great. Thanks Marcus.

just to let you know:
I've added a lot of stuff and added also some structure and formatting. 
But just to not loose the overview. ;-)

Of course this doesn't mean that this structure has to be used. We are 
still free to change where it is necessary or looks better.

Marcus

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


Re: Bugzilla needs version 4.1.3 added

Posted by "Keith N. McKenna" <ke...@comcast.net>.
Marcus wrote:
> Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna:
>> Marcus wrote:
>>> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
>>>> With the announcement of the Release of version 4.1.3 that revision
>>>> should be added to Bugzilla so that bugs can be reported against it.
>>>> Currently only 4.1.3-dev is active and for latest confirmation on the
>>>> latest available is 4.1.2
>>>
>>> right, I'll do this as next task. However, this needs definetely added
>>> as important task to the cookbook. Will you do this?
>>>
>> Done
> 
> and BZ is also updated. :-)
> 
> Marcus
> 
> 
> 
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>
>>>
>>> You just need to add some text. Don't care about formatting or order. We
>>> will do this later when everything (hopefully ;-) ) is there.
>>>
>>> Hey, it's a great idea when you would coordinate the creation of this
>>> cookbook. Then you learn more about the whole process, can add opinions
>>> from your point of view, etc.
>>>
>>> What do you think?
Great. Thanks Marcus.


Re: Bugzilla needs version 4.1.3 added

Posted by "Keith N. McKenna" <ke...@comcast.net>.
Marcus wrote:
> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
>> With the announcement of the Release of version 4.1.3 that revision
>> should be added to Bugzilla so that bugs can be reported against it.
>> Currently only 4.1.3-dev is active and for latest confirmation on the
>> latest available is 4.1.2
> 
> right, I'll do this as next task. However, this needs definetely added
> as important task to the cookbook. Will you do this?
> 
Done

> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
> 
> You just need to add some text. Don't care about formatting or order. We
> will do this later when everything (hopefully ;-) ) is there.
> 
> Hey, it's a great idea when you would coordinate the creation of this
> cookbook. Then you learn more about the whole process, can add opinions
> from your point of view, etc.
> 
> What do you think?
> 
> Thanks
> 
> Marcus



Re: Bugzilla needs version 4.1.3 added

Posted by "Keith N. McKenna" <ke...@comcast.net>.
Marcus wrote:
> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna:
>> With the announcement of the Release of version 4.1.3 that revision
>> should be added to Bugzilla so that bugs can be reported against it.
>> Currently only 4.1.3-dev is active and for latest confirmation on the
>> latest available is 4.1.2
> 
> right, I'll do this as next task. However, this needs definetely added
> as important task to the cookbook. Will you do this?
> 
> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
> 
> You just need to add some text. Don't care about formatting or order. We
> will do this later when everything (hopefully ;-) ) is there.
> 
> Hey, it's a great idea when you would coordinate the creation of this
> cookbook. Then you learn more about the whole process, can add opinions
> from your point of view, etc.
> 
> What do you think?
> 
> Thanks
> 
> Marcus
Can do for both.

Keith