Re: [VOTE]: Release Apache OpenOffice 4.0.1 (RC3)
+1 Bonnie On Mon, Sep 23, 2013 at 11:26 PM, Oliver-Rainer Wittmann < orwittm...@googlemail.com> wrote: > +1 > > Best regards, Oliver. > > > On 22.09.2013 10:06, Jürgen Schmidt wrote: > >> Hi all, >> >> this is a call for vote on releasing the RC3 release candidate as >> Apache OpenOffice 4.0.1. This will be an important update release for >> Apache OpenOffice 4.0 to fix some serious regressions and to introduce >> some new languages (Basque, Khmer, Lithuaian, Polish, Serbian Cyrillic, >> Swedish, Turkish, Vietnamese and Chinese Traditional). It is a further >> key milestone to continue the success of OpenOffice. >> >> This release candidate contains mainly fixes serious problems and >> regressions and new languages. An over view can be found under: >> >> http://people.apache.org/~jsc/**developer-snapshots/snapshot/** >> RC3_fixes_1513395_1524958.html<http://people.apache.org/~jsc/developer-snapshots/snapshot/RC3_fixes_1513395_1524958.html> >> >> The release candidate artifacts (source release, as well as binary >> releases for 32 languages) and further information how to verify and >> review Apache OpenOffice 4.0.1 can be found on the following wiki page: >> >> https://cwiki.apache.org/**confluence/display/OOOUSERS/** >> Development+Snapshot+Builds#**DevelopmentSnapshotBuilds-**AOOSnapshot<https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOOSnapshot> >> >> The RC is based on the release branch AOO401, revision 1524958! >> >> Please vote on releasing this package as Apache OpenOffice 4.0.1. >> >> The vote starts now and will be open until: >> >> UTC at noon on Wednesday, 25 September: 2013-09-25 12:00 UTC. >> >> But we invite all people to vote (non binding) on this RC. We would like >> to provide a release that is supported by the majority of our project >> members. >> >> [ ] +1 Release this package as Apache OpenOffice 4.0.1 >> [ ] 0 Don't care >> [ ] -1 Do not release this package because... >> >> --**--**- >> To unsubscribe, e-mail: >> dev-unsubscribe@openoffice.**apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@openoffice.**apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Bonnie Kim University of California, Berkeley English, B. A. bonnie...@berkeley.edu (510) 908-0479
CMS diff: Decision Making
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openoffice.apache.org/orientation%2Fdecision-making.mdtext Bonnie Kim Index: trunk/content/orientation/decision-making.mdtext === --- trunk/content/orientation/decision-making.mdtext(revision 1525182) +++ trunk/content/orientation/decision-making.mdtext(working copy) @@ -31,13 +31,13 @@ unnecessary and unproductive. We have a "time machine" called Subversion that allows us to undo any changes to the product or website. So if a Committer believes that a change would be uncontroversial, and the change is reversible, then the default approach is to go ahead make the change. -1. Terms that you might related to the above are: [JFDI](http://www.urbandictionary.com/define.php?term=JFDI) and "assuming lazy consensus". +1. Terms that you might need to know related to the above are: [JFDI](http://www.urbandictionary.com/define.php?term=JFDI) and "assuming lazy consensus". 1. However, there are times where CTR is not appropriate and RTC is used. This happens, for example, at the end of a release cycle, when we want to carefully review changes made to the product, in order to control the final quality before the release. When we're in RTC mode, no changes are made to the code unless first discussed and approved on the mailing list. -1. A Committer can also voluntarily invocate a RTC on their own changes. For example the Committer might be considering a change that of greater significance. Maybe he would +1. A Committer can also voluntarily invocate a RTC on their own changes. For example the Committer might be considering a change that is of greater significance. Maybe he would value additional input, or technical review. Maybe the change is controversial or require coordination. If CTR is not appropriate then one can make a proposal and send it to the dev mailing list. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Module 3 Corrections
Hello, I noticed a number of corrections that needed to be made on Module 3 of the Orientation Modules, as well as the Lazy Consensus article. I could list these corrections, but I wouldn't mind entering them myself; where can I go to make them? Bonnie -- Bonnie Kim University of California, Berkeley English, B. A. bonnie...@berkeley.edu (510) 908-0479
New Volunteer! Bonnie Kim
Hello! My name is Bonnie and I'm a recent graduate from UC Berkeley. I'm new to Apache OpenOffice, so I wanted to give a little introduction of myself before we begin. I studied English as an undergrad, and completed an honors thesis devoted to sci-fi author Isaac Asimov. My primary interest was in the literary figure of the robot, and why it continues to grip us today, as a legend if not as a reality. I'm interested in OpenOffice because I'm excited to begin my career as a technical writer, and I wanted to gain some experience before I began as a professional. Having come from a strong academic background, I still want to challenge myself by continuing to learn new things, although to be honest I'm a bit overwhelmed by the sheer variety of technological fields that are out there. Anyways, I hope we'll get along very well! And I'll shoot along a couple of questions here and there if that's alright. Thanks, everyone! Bonnie -- Bonnie Kim University of California, Berkeley English, B. A. bonnie...@berkeley.edu (510) 908-0479
