If/When there is a need, I can do it.
> On Dec 1, 2018, at 3:24 PM, Matthias Seidel
> wrote:
>
> Hi all,
>
> Am 13.11.18 um 21:38 schrieb Andrea Pescetti:
>> Peter Kovacs wrote:
>>> I am just saying a 4.1.7 release has nothing to do with the efforts we
>>> have to organize for 4.2.0.
>>
>>
Hi all,
Am 13.11.18 um 21:38 schrieb Andrea Pescetti:
> Peter Kovacs wrote:
>> I am just saying a 4.1.7 release has nothing to do with the efforts we
>> have to organize for 4.2.0.
>
> OK, got it! Let's work together on finishing 4.1.6 and then we will
> have plenty of time for discussing about
Hi Marcus,
Am 17.11.18 um 10:10 schrieb Marcus:
> Am 14.11.18 um 00:09 schrieb Marcus:
>> Am 13.11.18 um 08:04 schrieb Peter Kovacs:
>>> Release is now in the svn branch.
>>>
>>> I remove tonight the 4.1.5 release, any objections?
>>>
>>> So how much time do we need? is release date 16th November
Am 14.11.18 um 00:09 schrieb Marcus:
Am 13.11.18 um 08:04 schrieb Peter Kovacs:
Release is now in the svn branch.
I remove tonight the 4.1.5 release, any objections?
So how much time do we need? is release date 16th November feasable?
if there is no good reason against it, I would move this
Hi Marcus,
Am 14.11.18 um 00:09 schrieb Marcus:
> Am 13.11.18 um 00:58 schrieb Matthias Seidel:
>> Am 13.11.18 um 00:48 schrieb Andrea Pescetti:
>>> Peter Kovacs wrote:
I do not see your issue. Our release team works much faster then
the dev
team progresses on 4.2.0.
>>>
>>> There
Am 13.11.18 um 00:58 schrieb Matthias Seidel:
Am 13.11.18 um 00:48 schrieb Andrea Pescetti:
Peter Kovacs wrote:
I do not see your issue. Our release team works much faster then the dev
team progresses on 4.2.0.
There is a major difference between a 4.1.x and a new release like
4.2.0: for
Am 13.11.18 um 08:04 schrieb Peter Kovacs:
Release is now in the svn branch.
I remove tonight the 4.1.5 release, any objections?
So how much time do we need? is release date 16th November feasable?
if there is no good reason against it, I would move this always to the
weekend, as I think
Peter Kovacs wrote:
I am just saying a 4.1.7 release has nothing to do with the efforts we
have to organize for 4.2.0.
OK, got it! Let's work together on finishing 4.1.6 and then we will have
plenty of time for discussing about the next releases.
Regards,
Andrea.
Am 13.11.18 um 08:39 schrieb Matthias Seidel:
Am 13.11.18 um 08:04 schrieb Peter Kovacs:
Release is now in the svn branch.
I remove tonight the 4.1.5 release, any objections?
If you speak of
https://www.apache.org/dist/openoffice/4.1.5/
our project page [1] still points to it, so please
Okay I need to check.
4.1.5 delete as last step, check.
Am 13. November 2018 11:32:20 MEZ schrieb Matthias Seidel
:
>Hi Peter,
>
>Am 13.11.18 um 08:04 schrieb Peter Kovacs:
>> Release is now in the svn branch.
>
>There are a lot of languages missing...
>
Hi Peter,
Am 13.11.18 um 08:04 schrieb Peter Kovacs:
> Release is now in the svn branch.
There are a lot of languages missing...
https://dist.apache.org/repos/dist/release/openoffice/4.1.6/binaries/
https://www.apache.org/dist/openoffice/4.1.6/binaries/
Regards,
Matthias
>
> I remove
Hi Peter,
Am 13.11.18 um 08:04 schrieb Peter Kovacs:
> Release is now in the svn branch.
>
> I remove tonight the 4.1.5 release, any objections?
If you speak of
https://www.apache.org/dist/openoffice/4.1.5/
our project page [1] still points to it, so please wait until the page
is updated after
Release is now in the svn branch.
I remove tonight the 4.1.5 release, any objections?
So how much time do we need? is release date 16th November feasable?
On 13.11.18 01:30, Peter Kovacs wrote:
> Andrea,
>
> I am just saying a 4.1.7 release has nothing to do with the efforts we
> have to
Andrea,
I am just saying a 4.1.7 release has nothing to do with the efforts we
have to organize for 4.2.0.
I hope I upload now into the right place, but I have initiated the task.
All the best
Peter
On 13.11.18 00:48, Andrea Pescetti wrote:
> Peter Kovacs wrote:
>> I do not see your issue.
On 11/12/2018 4:34 PM, Matthias Seidel wrote:
> Hi Marcus,
>
> Am 12.11.18 um 21:05 schrieb Marcus:
>> Am 12.11.18 um 14:59 schrieb Matthias Seidel:
>>> Am 11.11.18 um 17:36 schrieb Peter Kovacs:
I am not available at the moment for release manager. But it would be
good to
Am 13.11.18 um 00:48 schrieb Andrea Pescetti:
> Peter Kovacs wrote:
>> I do not see your issue. Our release team works much faster then the dev
>> team progresses on 4.2.0.
>
> There is a major difference between a 4.1.x and a new release like
> 4.2.0: for 4.2.0 we need the entire community, not
Peter Kovacs wrote:
I do not see your issue. Our release team works much faster then the dev
team progresses on 4.2.0.
There is a major difference between a 4.1.x and a new release like
4.2.0: for 4.2.0 we need the entire community, not only what you call
the "release team" and developers
I do not see your issue. Our release team works much faster then the dev
team progresses on 4.2.0.
And to train releases is vital for us. 4.1.6 did not really bind any
developer, beyond security issues.
A 4.1.7 will keep the routine and knowledge active while we develop 4.2.0.
All the best
On 12/11/2018 Patricia Shanahan wrote:
The way I see it, we should be keeping 4.1.x for security fixes that
cannot wait until 4.2.0. As such, we may need to decide to release 4.1.7
at any time.
Sure, this is obvious. Thanks for pointing it out and of course I agree
with it. I was commenting
On 11/12/2018 2:49 PM, Andrea Pescetti wrote:
On 11/11/2018 Peter Kovacs wrote:
I suggest that we start right away with an Parallel development of 4.1.7
Release branch.
First, we'll have to officially release and announce 4.1.6.
Then energy should really go to 4.2.0. Only if there are any
On 11/11/2018 Peter Kovacs wrote:
I suggest that we start right away with an Parallel development of 4.1.7
Release branch.
First, we'll have to officially release and announce 4.1.6.
Then energy should really go to 4.2.0. Only if there are any outstanding
bugs or regressions we should
Hi Marcus,
Am 12.11.18 um 21:05 schrieb Marcus:
> Am 12.11.18 um 14:59 schrieb Matthias Seidel:
>> Am 11.11.18 um 17:36 schrieb Peter Kovacs:
>>>
>>> I am not available at the moment for release manager. But it would be
>>> good to continue, to be able to have release versions prepared.
>>
>>
Am 12.11.18 um 14:59 schrieb Matthias Seidel:
Am 11.11.18 um 17:36 schrieb Peter Kovacs:
I am not available at the moment for release manager. But it would be
good to continue, to be able to have release versions prepared.
Back to 4.1.6: Is anyone already working on the Release Notes?
Am 12.11.18 um 14:39 schrieb Jim Jagielski:
On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
And I suggest also to branch 4.2.0 from trunk. Jim you still available
to be the release manager on this branch? - Maybe we should branch from
the latest dev build version if we can find out and
On 11/12/2018 05:39 AM, Jim Jagielski wrote:
On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
And I suggest also to branch 4.2.0 from trunk. Jim you still available
to be the release manager on this branch? - Maybe we should branch from
the latest dev build version if we can find out and
Hi Peter,
Am 11.11.18 um 17:36 schrieb Peter Kovacs:
> Hello all,
>
> I suggest that we start right away with an Parallel development of 4.1.7
> Release branch. I nominate Matthias to be release manager. Are you
> willing to go on this?
Yes, after we have 4.1.6 out I will take a deep breath and
Hello,
Am 12.11.18 um 14:39 schrieb Jim Jagielski:
>
>
>> On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
>>
>> And I suggest also to branch 4.2.0 from trunk. Jim you still available
>> to be the release manager on this branch? - Maybe we should branch from
>> the latest dev build version if
> On Nov 11, 2018, at 11:36 AM, Peter Kovacs wrote:
>
> And I suggest also to branch 4.2.0 from trunk. Jim you still available
> to be the release manager on this branch? - Maybe we should branch from
> the latest dev build version if we can find out and then check on the
> commits.
That
Hello
Am 11.11.18 um 17:36 schrieb Peter Kovacs:
> Hello all,
>
> I suggest that we start right away with an Parallel development of 4.1.7
> Release branch. I nominate Matthias to be release manager. Are you
> willing to go on this?
>
> And I suggest also to branch 4.2.0 from trunk. Jim you
Hello all,
I suggest that we start right away with an Parallel development of 4.1.7
Release branch. I nominate Matthias to be release manager. Are you
willing to go on this?
And I suggest also to branch 4.2.0 from trunk. Jim you still available
to be the release manager on this branch? - Maybe
30 matches
Mail list logo
