On 6 August 2013 15:05, Andrea Pescetti <pesce...@apache.org> wrote: > Rob Weir wrote: > >> a 4.0.1 release in the next few weeks to address the specific >> high-urgency issues? [...] >> > > Good plan. I'm adding some remarks below, to see the release not only from > the users point of view, but from the community perspective too. > > 3) Use the "release blocker" flag to propose defects for inclusion in >> the 4.0.1 release. >> > > OK, but by default the "proposed 4.0.1 release blocker" flag (when it > exists) should be set for: > 1) All the issues with keyword "regression" found after 4.0 was released > 2) All the issues nominated as release blockers for 4.0 and unresolved. > > It is important that we don't fall in the "release and forget" trap, i.e., > "this bug was already known when 4.0 was released, so it doesn't need to be > evaluated again for 4.0.1". At least, we should re-evaluate the old > proposed blockers: some of them might have become more relevant. > > 4) New translations are rolled in, since a new translation cannot >> break core code. [...] >> > > Here (and, by the way, the infamous problem for Italian was a broken > translation of style names a few years ago; indeed, this kind of problems > does not affect other translations) it is really important that we are able > to clearly communicate to volunteers that they can target 4.0.1. > > This is not the case at the moment: we have volunteers who are ready to > work and Pootle is not ready yet for their language, or it only offers > 3.4.1. See > http://markmail.org/message/**4oxacrviktdbmbcv<http://markmail.org/message/4oxacrviktdbmbcv>for > more. >
We need to differentiate here, Pootle is just one tool of many. When you start on a major editing process like a new language, it not fast and convinient enough, you can edit a lot faster offline, and then upload the results. It is another matter if the PO files are not ready, that would prohibit work. However we have a high volume of langauges that are both available as PO files and in Pootle, so I think this is a real showstopper, apart from a single language (which problaly takes more than a couple of weeks to translate) > > The opportunity is now and we should definitely make it a priority for > 4.0.1, so we can tell volunteers that 4.0.1 can be released in their > language and that they can start contributing immediately. This has the > potential to motivate contributors. > I agree to this...lets get those languages that are nearly there completed, and once we have volunteers working on that for 4.01, and those languages who are no near complete or miss totally be planned for 4.1 rgds jan I. > > 5) The one "feature" that I'd consider rolling in would be changes to >> work with Mac OS 10.9. It is not a regression in our code per se, but >> it is a new issue, and a critical one. [...] >> > > A minor and low-risk "feature" is updating bundled dictionaries. As I > explained in a mail to this list, the update behavior is not optimal from a > usability point of view so it's best to update dictionaries just before the > new release. Needless to say, I'd volunteer for that. > > Regards, > Andrea. > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@openoffice.**apache.org<dev-unsubscr...@openoffice.apache.org> > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
