On 24/10/14 20:15, 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.
Well I think we added all languages on Pootle where we see activities or interest in working on the translation. Why should we add languages where nobody is working on? I don't get it. Juergen > > 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. > >> 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. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
