openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus (OOo)" <marcus.m...@wtnet.de>
Subject Re: [BUGZILLA] proposal for new entry in field Target Milestone
Date Fri, 07 Mar 2014 20:39:43 GMT
Am 03/06/2014 09:20 AM, schrieb Oliver-Rainer Wittmann:
> Hi,
>
> On 05.03.2014 22:46, Marcus (OOo) wrote:
>> Am 03/05/2014 05:23 PM, schrieb Oliver-Rainer Wittmann:
>>> Hi,
>>>
>>> On 05.03.2014 15:35, Rob Weir wrote:
>>>> On Wed, Mar 5, 2014 at 8:38 AM, Oliver-Rainer Wittmann
>>>> <orwittmann@googlemail.com> wrote:
>>>>> Hi,
>>>>>
>>>>> as we have created branch AOO410 for our coming AOO 4.1.0 release I
>>>>> would
>>>>> like to propose a new entry for Bugzilla field 'Target Milestone'.
>>>>> Something
>>>>> like 'AOO.next'. It shall be used for the solved issues which won't
>>>>> be part
>>>>> of the AOO 4.1.0 release, but be part of the next following one. Once
>>>>> we had
>>>>> agreed on the version number for this release this new entry shall be
>>>>> renamed accordingly.
>>>>>
>>>>
>>>> Would it make sense to have two, like:
>>>>
>>>> AOO.next.micro
>>>> AOO.next.minor
>>>>
>>>> That would map to things targeted for 4.1.1 (work done in the branch)
>>>> versus 4.2.0 (work done in the trunk).
>>>>
>>>
>>> It might make sense, but I think in this case we can name
>>> 'AOO.next.micro' directly '4.1.1' (we also know, what the next micro
>>> release will be) and it should be introduced right after our 4.1.0
>>> release, when a corresponding issue comes to life.
>>
>> +1
>>
>> I also think that we can name the things directly.
>>
>> For issues that should be fixed/resolved in the mid-term future, we can
>> use the already existing "AOO Later".
>>
>
> strong -1 from my side for using 'AOO Later'.
> my arguments are:
> - There are already more than 1800 issue having this 'Target Milestone'.
> - 'AOO Later' sounds like 'never' - just my experience from former days
> when we had 'OOo Later' as 'Target Milestone'.

ah, I remember. I'm rejecting my suggestion. ;-)
Indeed better to start with a new name *and* nearly 0 issues.

Sorry for the noise.

Marcus



>> And if there is no idea how and when to fix it, then simply don#t set
>> any target version.
>>
>> Marcus
>>
>>
>>
>>> BTW, is it possible to rename an existing entry of 'Target Milestone' as
>>> I had propose above?
>>>
>>> Just my 2 cents.
>>>
>>> Best regards, Oliver.
>>>
>>>> -Rob
>>>>
>>>>
>>>>
>>>>
>>>>> Any objections?
>>>>>
>>>>>
>>>>> Best regards, Oliver.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
>



-- 

Ciao

Marcus

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


Mime
View raw message