I also like that we announce 4.1.5-GA at the same time we announce 4.2.0-B1.
Should we clone the 4.1.4 release Wiki page (to create a 4.1.5) and start keeping track there? > On Dec 1, 2017, at 8:18 AM, Patricia Shanahan <p...@acm.org> wrote: > > Remember we also have the 4.1.5 branch, which is a lower risk solution to > some 4.1.4 regressions. > > I think it is time to decide whether to release it, and if so, what the > timing should be relative to the start of the 4.2 beta test. There is > something to be said for a single announcement so that we can explain the > relationship. > > On 12/1/2017 5:13 AM, Jim Jagielski wrote: >> I see that Pat has committed the security patches to trunk, which is >> fantastic! >> Maybe we should take the next few business days and go thru Bugz >> and see what, if anything, would be low-risk patches to trunk and >> pencil in, say, Dec 7th as a "code freeze" date for builds... >> I can provide builds for all 4 platforms. >>> On Dec 1, 2017, at 1:34 AM, Mechtilde <o...@mechtilde.de> wrote: >>> >>> Hello >>> >>> I like this idea, too. it makes it visible that we aren't dead. >>> >>> Regards >>> >>> Mechtilde >>> >>> Am 01.12.2017 um 03:41 schrieb Jim Jagielski: >>>> I like it. I already have Linux, Windows and macOS 4.2.0-dev builds >>>> available >>>> (http://home.apache.org/~jim/AOO-builds/ >>>> <http://home.apache.org/~jim/AOO-builds/>) for some langs >>>> >>>> >>>>> On Nov 30, 2017, at 5:15 PM, Marcus <marcus.m...@wtnet.de> wrote: >>>>> >>>>> Am 30.11.2017 um 21:26 schrieb Dave Fisher: >>>>>> In light of our current situation with getting builds together but not >>>>>> having a lot of people doing more than simple QA what does the team >>>>>> think about releasing a Public Beta for 4.2.0? I think that this would >>>>>> be an advantage for the project and might serve to bring in more of the >>>>>> community as QA volunteers. >>>>> >>>>> I thought it's without discussion that we need a (long) beta test phase >>>>> for 4.2.0. So, yes for your proposal. >>>>> >>>>> We can create a new entry on the download webpage, some advertising areas >>>>> on the other webpages, and other fine things to make it visible. >>>>> >>>>> And - also this should be clear already - we need several builds of 4.2.0 >>>>> with further included bugfixes; to show an increasing quality towards the >>>>> final release build. >>>>> >>>>> For me the real question is " *When* do we start the beta? ". ;-) I would >>>>> like to have a specific level of quality that we give to our users. >>>>> Otherwise we will get spammed by bug reports which nobody wants to handle. >>>>> >>>>> Marcus >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>>> >>>> >>>> >>> >>> -- >>> Mechtilde Stehmann >>> ## Apache OpenOffice.org >>> ## Freie Office Suite für Linux, MacOSX, Windows >>> ## Debian Developer >>> ## Loook, calender-exchange-provider, libreoffice-canzeley-client >>> ## PGP encryption welcome >>> ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
