On 10/24/2014 11:15 AM, Andrea Pescetti wrote:
> On 23/10/2014 Rob Weir wrote:
>> Let's try for a 4.1.2 release
> 
> I see another priority. But it is fully compatible with making a release
> and actually the two can work together really well.
> 
> I would like to streamline our processes and remove bottlenecks and
> dependencies on non-Apache systems. In other words, it's two years that
> we are a top-level project and it is time to reach a phase where
> processes just work. It is not acceptable that we produce binary builds
> on non-Apache hardware, it is hardly acceptable that we don't have all
> our languages on Pootle, and it is not acceptable that the l10n list
> sees a reduction in activity just because I suddenly have to use a large
> part of my spare time on unrelated activities.
> 
> A release is probably a perfect way to make sure that everything is
> considered (and an important indicator in the Apache way). So it will
> take even more time, but if we can take care of all these tasks we will
> finally be a project with solid grounds at Apache. Some tasks, like the
> buildbots, are huge; some, like finding someone who can welcome
> volunteers on the l10n list when I can't, are easier. And it's obvious
> that we must work together, we can't expect that a few people do
> everything.
> 
>> 1) Whatever new languages/language updates we have, including of
>> course dictionary updates.
> 
> We are seeing interest in a couple of languages, but we don't have any
> new ones to release at the moment. Of course, when we establish a
> deadline we can communicate it to translators and make a plan.
> 
>> 2) Fixes for any critical bugs, especially any introduced in AOO
>> 4.1.1.  Do we know yet which bugs these are?   Do we have a short list
>> of the most critical ones?
> 
> This one https://issues.apache.org/ooo/show_bug.cgi?id=125519 is worth
> looking at. It's already fixed in trunk anyway.

I just created a saved search -- registered user -- with 4.1.x regressions:

https://issues.apache.org/ooo/buglist.cgi?cmdtype=dorem&list_id=161111&namedcmd=4.1.x%20regressions&remaction=run&sharer_id=7

> 
>> 3) Patches merged in from new dev volunteers.
>> I think #3 is extremely important here.
> 
> Sure, involving new development volunteers has been a priority in the
> last few months, and I'm happy to hear some new voices here. We may even
> manage to get some new features implemented, not only basic fixes.
> 
> But again... If we go for this, then mentoring developers becomes a
> priority and everyone who has the required knowledge should invest time
> on this.
> 
>> What do you think?
> 
> It is surely a good idea (and the version number does not matter that
> much), provided that all of us are ready to be actively involved as much
> as possible.
> 
> Regards,
>   Andrea.

Suggestions 1-3 do involve additional translation from new volunteers.
Juergen's version numbering scheme is now documented on the Planning
wiki: https://cwiki.apache.org/confluence/display/OOOUSERS/Releases)

but we may want to revise this definition for translation of UI strings
and help content and reassign these kinds of changes to "minor" instead
of "major". In this case, we would be looking at 4.2?

I think the suggestion of using Apache hardware for the rollout of the
"new" version is  a good one.

So, two larger tasks must be accomplished before a new release if a new
binary rollout is determined:

* getting a new release manager (complete task list needed)
* configuring additional buildbots and going through a "live" complete
run -- all languages and platforms.

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

-- 
-------------------------------------------------------------------------
MzK

"Success breeds complacency. Complacency breeds failure.
 Only the paranoid survive."
                            -- Andy Grove, Intel Co-founder

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

Reply via email to