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:Kay Schenk (kay.@gmail.com)
Date:Feb 28, 2012 4:08:41 pm
List:org.apache.incubator.ooo-dev

2012/2/24 Jürgen Schmidt <jogi@googlemail.com>

Hi,

we move closer forward to our first release.

I would like to suggest that we focus on the following areas next week. 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)

- increase QA work - focus on stabilization, means focus on showstopper issues - finalize the About dialog information, input for future bug reports - online update service

well...a tiny little breakthrough on the update service...

I did the following today--

* reassigned the old update service ( update36.services.openoffice.org) to the current web server IP via my /etc/host file

* created a ProductUpdateService directory on www.openoffice.org and dumped Ariel's atom feed file into the directory with the name check.Update

Now, on my exisiting OOo3.3, when I click "Check for updates", it *gets* somewhere but of course, my system is expecting an ".rpm" package and not a tar ball as spec'd in the DL url, so nothing happens. Really I didn't try to find something reasonable, I just wanted to see if the ideas I had about re-routing the connection would work.

Bottom line. I think we should have infra also make this DNS change. At least folks with current "auto upgrades" will not continue to suffer from NO conenctions AND we now have an place to test/implement the feed, assuming we can get it in the right format for what we will be releasing with 3.4.

Thoughts?

ps. I will copy all this to the previous thread/post on the update service as well.

- updating building guides in the wiki

- documentation update can be run in parallel and are independent of the binary release - translation update, we have made minimal UI changes only and we will use the 3.4 beta translation that were in place.

Anything else that comes into your minds?

I have started to work on the MacOS building guide and have simplified some things (work ongoing).

We need some volunteers who take a look on the other platforms. Especially reference to the hg repo should be removed/replaced to our svn repo. Information about childworkspaces can be removed because it is not longer relevant for us. I would say the focus should be on simplification.

What do others think about it?

--

---------------------------------------------------------------------------------------- MzK

"Follow your bliss." -- attributed to Joseph Campbell