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 always to the weekend, as I think the most people can spend more time for a release than within the week with 1-2 hours in the evening.

So, Saturday (btw, which time?) would fit better - at least for me for the download website.

what about the release now? Is it ready for offering on the download webpage?

Thanks

Marcus



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 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. 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 (read: localization efforts,
organized QA efforts, a possible public beta, a baseline update...).
If you believe that 4.2.0 is only for developers you are
underestimating the task.

A 4.1.7 will keep the routine and knowledge active while we develop
4.2.0.
We have many millions of users. We must provide some value with a
release. This meant waiting 11 months (and counting) between 4.1.5 and
4.1.6; if 4.1.6 has no major regressions, we can surely wait some
months before considering a 4.1.7 (again, in a non-emergency situation).

But I would really like that we stop talking about this virtual 4.1.7
release and actually release 4.1.6 for real.


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

Reply via email to