Am 04/09/2016 11:36 PM, schrieb Kay Schenk:
On Sat, Apr 9, 2016 at 3:01 AM, Marcus wrote:
Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
[...]
A warning -- unless you can see an SVN commit clearly
stating that the fix has been ported to one of our existing
releases, it may take a bit of invest
On Sat, Apr 9, 2016 at 3:01 AM, Marcus wrote:
> Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
>
>> [...]
>>
>> A warning -- unless you can see an SVN commit clearly
>> stating that the fix has been ported to one of our existing
>> releases, it may take a bit of investigation into the
>> release bra
> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Saturday, April 9, 2016 00:01
> To: dev@openoffice.apache.org
> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>
> Am 04/08/2016 12:58 AM, schrieb Kay Schenk:
> > On
Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
[...]
A warning -- unless you can see an SVN commit clearly
stating that the fix has been ported to one of our existing
releases, it may take a bit of investigation into the
release branch area to determine this.
release branch area--
http://svn.apach
eady happened.
Marcus
-Original Message-
From: Marcus [mailto:marcus.m...@wtnet.de]
Sent: Thursday, April 7, 2016 02:10
To: dev@openoffice.apache.org
Cc: q...@openoffice.apache.org
Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
[ ... ]
I've closed all listed issues
On 08/04/2016 Kay Schenk wrote:
Ok, perhaps some misunderstanding here. What I'm asking for is assistance
is finding the RESOLVED-FIXED issues that actually were incorporated in a
release, and CLOSE them.
Well, RESOLVED-FIXED issues are:
- either non-code fixes as discussed, and in this case t
sy without fixes for any OpenOffice code.
I'll answer your other mail later. And try to close more issues in the
next days.
Marcus
-Original Message-
From: Marcus [mailto:marcus.m...@wtnet.de]
Sent: Thursday, April 7, 2016 02:10
To: dev@openoffice.apache.org
Cc: q...@openoffice
, it's a bit of an
> annoyance to get the emails, but I think it's worth it to keep better
> records.
>
>
>>
>> Marcus
>
>
A great big THANK YOU for the work done on this cleanup business so far.
SUPER!
>
>>
>>
>>
>> -Origi
category.
Of these, some percentage should be CLOSEd. And yes, it's a bit of an
annoyance to get the emails, but I think it's worth it to keep better
records.
>
> Marcus
>
>
>
>
> -Original Message-----
>>> From: Marcus [mailto:marcus.m...
April 7, 2016 02:10
To: dev@openoffice.apache.org
Cc: q...@openoffice.apache.org
Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
[ ... ]
I've closed all listed issues regarding our infrastructure (Website,
Bugzilla, etc.). As you can see every single change results in a mail
and
gt; From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Thursday, April 7, 2016 02:10
> To: dev@openoffice.apache.org
> Cc: q...@openoffice.apache.org
> Subject: Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues
>
[ ... ]
> I've closed all listed issues regarding our i
Am 04/07/2016 12:43 AM, schrieb Kay Schenk:
I think typically the process for RESOLVED-FIXED (those
issues that were fixed by some kind of code change to
/trunk) issues is to:
* commit the change to a release build
* once the release build is out for testing, check that the
bug is fixed, and use
12 matches
Mail list logo
