atom feed37 messages in org.apache.incubator.ooo-devRe: [RELEASE]: preparation for our fi...
FromSent OnAttachments
Jürgen SchmidtFeb 24, 2012 2:23 am 
Andrea PescettiFeb 24, 2012 2:53 am 
Jürgen SchmidtFeb 24, 2012 3:05 am 
Raphael BircherFeb 24, 2012 3:37 am 
Andrea PescettiFeb 24, 2012 3:40 am 
Jürgen SchmidtFeb 24, 2012 4:18 am 
Andre FischerFeb 24, 2012 4:26 am 
Jürgen SchmidtFeb 24, 2012 4:28 am 
Rory O'FarrellFeb 24, 2012 4:33 am 
Rory O'FarrellFeb 24, 2012 4:36 am 
Jürgen SchmidtFeb 24, 2012 4:42 am 
imacatFeb 24, 2012 7:16 am 
Ross GardlerFeb 24, 2012 8:03 am 
Rob WeirFeb 24, 2012 4:05 pm 
Pedro GiffuniFeb 24, 2012 6:24 pm 
Ross GardlerFeb 25, 2012 3:06 am 
Ross GardlerFeb 25, 2012 3:19 am 
O.FelkaFeb 25, 2012 3:26 am 
Ross GardlerFeb 25, 2012 4:15 am 
Kay SchenkFeb 25, 2012 8:53 am 
Jürgen SchmidtFeb 26, 2012 12:52 am 
Jürgen SchmidtFeb 26, 2012 1:05 am 
Michael BauerFeb 26, 2012 3:40 am 
Rob WeirFeb 26, 2012 11:50 am 
Jürgen SchmidtFeb 27, 2012 2:12 am 
Andre FischerFeb 27, 2012 2:30 am 
Michael BauerFeb 27, 2012 5:03 am 
Andre FischerFeb 27, 2012 6:27 am 
Andrea PescettiFeb 27, 2012 6:55 am 
Michael BauerFeb 27, 2012 7:47 am 
Andre FischerFeb 27, 2012 8:04 am 
Michael BauerFeb 27, 2012 8:43 am 
Kay SchenkFeb 28, 2012 4:08 pm 
Andrea PescettiFeb 29, 2012 12:58 pm 
Andre FischerMar 1, 2012 2:48 am 
Paolo PozzanMar 3, 2012 11:28 am 
Andrea PescettiMar 10, 2012 6:13 am 
Subject:Re: [RELEASE]: preparation for our first release
From:Jürgen Schmidt (jogi@googlemail.com)
Date:Feb 24, 2012 3:05:14 am
List:org.apache.incubator.ooo-dev

On 2/24/12 11:53 AM, Andrea Pescetti wrote:

On 24/02/2012 Jürgen Schmidt wrote:

And I would like to propose the following schedule depending on the progress we will make next week. Monday: Feb. 27th new dev snapshots Monday: March 5th first RC candidate (based on the progress next week)

This is (of course) great and exciting news. I would only recommend to avoid the temptation to be marketing-driven... let RC1 be something that we believe we could actually release. There's nothing bad in using the name "dev" or "beta" for something that is not ready yet. This is how I interpret the "depending on progress" above, and it would be very good and show respect for users.

RC should be used indeed only if we think that it can be released, and this depends on the progress ;-)

- translation update, we have made minimal UI changes only and we will use the 3.4 beta translation that were in place.

Note that https://issues.apache.org/ooo/show_bug.cgi?id=118895 is still not solved: it might be that the 3.4 beta translations are not integrated in our current dev builds, or, more likely, that language packs are not being built correctly. I've just set that issue as a release blocker. Using the 3.4-beta translations would be OK, but we need the full set, not what we have now (see issue page).

here we might run into a problem because of not having the translation process in place 100%. We have to figure out which translation data is the latest one, it's still not 100% clear if we really have it :-(

We will also need to: - Decide the URLs for all links in the suite (Extensions, Templates, Suite Updates, Extensions Updates...).

I hope the links wouldn't really change, but it have to be clarified

- Describe the 3.3 -> 3.4 migration path; it would be good to avoid the need to reinstall extensions, but I don't know the current state of the art here.

that can't be avoided because of the removed berkeley DB. Not nice but we can't avoid it.

Juergen