Re: [RELEASE]: proposed schedule for AOO 4.0
Am Donnerstag, 4. April 2013 um 19:40 schrieb Kay Schenk: > On Thu, Apr 4, 2013 at 4:07 AM, Jürgen Schmidt wrote: > > > On 4/4/13 11:27 AM, mengualjean...@free.fr wrote: > > > Hi, > > > > > > Does some cycle exist about releasing of OOo? Because since the > > schedule, it seems that OOo 4.0 will not include current work about > > accessibility. It is a pitty as I think it is a major contribution and it > > would be a pitty if we should wait for end of 2014 to see it. It seems > > things could be ready for novembre. Do you think we can hope progress > > during 1st six months 2014? In a 4.1 release I get? > > > > > > > > > we had 2 releases last year and I don't see any reason why we should not > > have 2 releases this year. It really depends on what we have for a new > > release. We don't want release something only to have a new release. > > > > The accessibility work is a big and major task and takes some time. It > > can't be finished in time for 4.0 but we will see how the development > > moves forward. It can be a good candidate for a 4.1. > > > > Juergen > > I think the last update we got on the accessibility work indicated end of > June for completion... > > http://markmail.org/message/ipdmx3scax4umc2s > > so, do we think we shouldn't wait on this for 4.0? I believe this is a misunderstanding but I am open to learn something else... ;-) Juergen > > > > > > > Regards, > > > > > > - Mail d'origine - > > > De: Jürgen Schmidt > > > À: dev@openoffice.apache.org > > > Envoyé: Thu, 04 Apr 2013 10:46:16 +0200 (CEST) > > > Objet: Re: [RELEASE]: proposed schedule for AOO 4.0 > > > > > > On 2/20/13 11:32 AM, Jürgen Schmidt wrote: > > > > On 2/20/13 10:46 AM, Jürgen Schmidt wrote: > > > > > Hi, > > > > > > > > > > we make good progress with the sidebar work which is done on the > > branch. > > > > > The sidebar will be the most visible and important change for 4.0 (by > > > > > the way I like what I have seen so far). We come closer to the point > > > > > where we should talk about a more detailed schedule. > > > > > > > > > > I would like to start with the following proposal and still many steps > > > > > have to be defined in more detail. > > > > > > > > > > 03/01 function verification test will start, define test case, prepare > > > > > tests etc. > > > > > 04/04 integrate sidebar branch in trunk, other new features should be > > > > > finished by this date as well. > > > > > > > > > > > > > > > > > I missed to add that the art work (logo, icons, etc. should be finished > > > > at this date as well) > > > > > > > > > 04/05 - 05/15 regression testing will be start on trunk > > > > > 04/05 - 05/15 bugfix and stabilization, no feature development > > > > > 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > > > > > strings. This can change when we know exactly how many new strings we > > > > > will have. But translation for new languages can already work on the > > > > > existing po files for 3.4.1. > > > > > 05/21 RC1 > > > > > 06/04 RC2 > > > > > 06/18 RC3 (optional), can be GA already > > > > > 06/25 GA -> this should be our final target > > > > > > > > > > > > > > > This is a proposal based on the ongoing work that I no. Please let me > > > > > know if I missed something important. > > > > > > > > > > Regular developer builds 1/week + nightly builds > > > > > > > > > > Based on feedback and potential changes I will put this in the wiki > > later. > > > > > > > > > > Important is from my pov that we start talking about the improvements > > > > > that we make in public. It should be very clear for anybody where the > > > > > real important features and improvement for OpenOffice or derivatives > > > > > are coming from ;-) > > > > > > > > > > > > > > > > > > I will try to give n update on the current plan. > > > > > > The
Re: [RELEASE]: proposed schedule for AOO 4.0
Guy Waterval schrieb: Hi Jürgen, Hi all, Is there an official terminology to describe the sidebar and its different parts ? A+ Yes, look at http://wiki.openoffice.org/wiki/Sidebar section "Glossary" and the picture on the right side there. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Re : Re: [RELEASE]: proposed schedule for AOO 4.0
On Thu, Apr 4, 2013 at 4:07 AM, Jürgen Schmidt wrote: > On 4/4/13 11:27 AM, mengualjean...@free.fr wrote: > > Hi, > > > > Does some cycle exist about releasing of OOo? Because since the > schedule, it seems that OOo 4.0 will not include current work about > accessibility. It is a pitty as I think it is a major contribution and it > would be a pitty if we should wait for end of 2014 to see it. It seems > things could be ready for novembre. Do you think we can hope progress > during 1st six months 2014? In a 4.1 release I get? > > > > we had 2 releases last year and I don't see any reason why we should not > have 2 releases this year. It really depends on what we have for a new > release. We don't want release something only to have a new release. > > The accessibility work is a big and major task and takes some time. It > can't be finished in time for 4.0 but we will see how the development > moves forward. It can be a good candidate for a 4.1. > > Juergen > I think the last update we got on the accessibility work indicated end of June for completion... http://markmail.org/message/ipdmx3scax4umc2s so, do we think we shouldn't wait on this for 4.0? > > > Regards, > > > > - Mail d'origine - > > De: Jürgen Schmidt > > À: dev@openoffice.apache.org > > Envoyé: Thu, 04 Apr 2013 10:46:16 +0200 (CEST) > > Objet: Re: [RELEASE]: proposed schedule for AOO 4.0 > > > > On 2/20/13 11:32 AM, Jürgen Schmidt wrote: > >> On 2/20/13 10:46 AM, Jürgen Schmidt wrote: > >>> Hi, > >>> > >>> we make good progress with the sidebar work which is done on the > branch. > >>> The sidebar will be the most visible and important change for 4.0 (by > >>> the way I like what I have seen so far). We come closer to the point > >>> where we should talk about a more detailed schedule. > >>> > >>> I would like to start with the following proposal and still many steps > >>> have to be defined in more detail. > >>> > >>> 03/01 function verification test will start, define test case, prepare > >>> tests etc. > >>> 04/04 integrate sidebar branch in trunk, other new features should be > >>> finished by this date as well. > >> > >> I missed to add that the art work (logo, icons, etc. should be finished > >> at this date as well) > >> > >>> 04/05 - 05/15 regression testing will be start on trunk > >>> 04/05 - 05/15 bugfix and stabilization, no feature development > >>> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > >>> strings. This can change when we know exactly how many new strings we > >>> will have. But translation for new languages can already work on the > >>> existing po files for 3.4.1. > >>> 05/21 RC1 > >>> 06/04 RC2 > >>> 06/18 RC3 (optional), can be GA already > >>> 06/25 GA -> this should be our final target > >>> > >>> > >>> This is a proposal based on the ongoing work that I no. Please let me > >>> know if I missed something important. > >>> > >>> Regular developer builds 1/week + nightly builds > >>> > >>> Based on feedback and potential changes I will put this in the wiki > later. > >>> > >>> Important is from my pov that we start talking about the improvements > >>> that we make in public. It should be very clear for anybody where the > >>> real important features and improvement for OpenOffice or derivatives > >>> are coming from ;-) > > > > I will try to give n update on the current plan. > > > > The sidebar branch is not yet integrated but I expect that it will be > > finished next week latest. That means we will have a delay of some days > > here. As soon as I have concrete dates I will update the plan in the > wiki. > > > > Some further things are ongoing and we should try to finish this work > > soon (2 weeks) to have the stuff in place and can start or concentrate > > on bug fixing and stabilization. > > > > Juergen > > > > > > > > > > > >>> > >>> > >>> Juergen > >>> > >> > > > > > > - > > 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 > > -- MzK "Achieving happiness requires the right combination of Zen and Zin."
Re: [RELEASE]: proposed schedule for AOO 4.0
Hi Jürgen, Hi all, Is there an official terminology to describe the sidebar and its different parts ? A+ -- gw 2013/4/4 Jürgen Schmidt > On 2/20/13 11:32 AM, Jürgen Schmidt wrote: > > On 2/20/13 10:46 AM, Jürgen Schmidt wrote: > >> Hi, > >> > >> we make good progress with the sidebar work which is done on the branch. > >> The sidebar will be the most visible and important change for 4.0 (by > >> the way I like what I have seen so far). We come closer to the point > >> where we should talk about a more detailed schedule. > >> > >> I would like to start with the following proposal and still many steps > >> have to be defined in more detail. > >> > >> 03/01 function verification test will start, define test case, prepare > >> tests etc. > >> 04/04 integrate sidebar branch in trunk, other new features should be > >> finished by this date as well. > > > > I missed to add that the art work (logo, icons, etc. should be finished > > at this date as well) > > > >> 04/05 - 05/15 regression testing will be start on trunk > >> 04/05 - 05/15 bugfix and stabilization, no feature development > >> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > >> strings. This can change when we know exactly how many new strings we > >> will have. But translation for new languages can already work on the > >> existing po files for 3.4.1. > >> 05/21 RC1 > >> 06/04 RC2 > >> 06/18 RC3 (optional), can be GA already > >> 06/25 GA -> this should be our final target > >> > >> > >> This is a proposal based on the ongoing work that I no. Please let me > >> know if I missed something important. > >> > >> Regular developer builds 1/week + nightly builds > >> > >> Based on feedback and potential changes I will put this in the wiki > later. > >> > >> Important is from my pov that we start talking about the improvements > >> that we make in public. It should be very clear for anybody where the > >> real important features and improvement for OpenOffice or derivatives > >> are coming from ;-) > > I will try to give n update on the current plan. > > The sidebar branch is not yet integrated but I expect that it will be > finished next week latest. That means we will have a delay of some days > here. As soon as I have concrete dates I will update the plan in the wiki. > > Some further things are ongoing and we should try to finish this work > soon (2 weeks) to have the stuff in place and can start or concentrate > on bug fixing and stabilization. > > Juergen > > > > > > >> > >> > >> Juergen > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Re : Re: [RELEASE]: proposed schedule for AOO 4.0
On 4/4/13 11:27 AM, mengualjean...@free.fr wrote: > Hi, > > Does some cycle exist about releasing of OOo? Because since the schedule, it > seems that OOo 4.0 will not include current work about accessibility. It is a > pitty as I think it is a major contribution and it would be a pitty if we > should wait for end of 2014 to see it. It seems things could be ready for > novembre. Do you think we can hope progress during 1st six months 2014? In a > 4.1 release I get? > we had 2 releases last year and I don't see any reason why we should not have 2 releases this year. It really depends on what we have for a new release. We don't want release something only to have a new release. The accessibility work is a big and major task and takes some time. It can't be finished in time for 4.0 but we will see how the development moves forward. It can be a good candidate for a 4.1. Juergen > Regards, > > - Mail d'origine - > De: Jürgen Schmidt > À: dev@openoffice.apache.org > Envoyé: Thu, 04 Apr 2013 10:46:16 +0200 (CEST) > Objet: Re: [RELEASE]: proposed schedule for AOO 4.0 > > On 2/20/13 11:32 AM, Jürgen Schmidt wrote: >> On 2/20/13 10:46 AM, Jürgen Schmidt wrote: >>> Hi, >>> >>> we make good progress with the sidebar work which is done on the branch. >>> The sidebar will be the most visible and important change for 4.0 (by >>> the way I like what I have seen so far). We come closer to the point >>> where we should talk about a more detailed schedule. >>> >>> I would like to start with the following proposal and still many steps >>> have to be defined in more detail. >>> >>> 03/01 function verification test will start, define test case, prepare >>> tests etc. >>> 04/04 integrate sidebar branch in trunk, other new features should be >>> finished by this date as well. >> >> I missed to add that the art work (logo, icons, etc. should be finished >> at this date as well) >> >>> 04/05 - 05/15 regression testing will be start on trunk >>> 04/05 - 05/15 bugfix and stabilization, no feature development >>> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new >>> strings. This can change when we know exactly how many new strings we >>> will have. But translation for new languages can already work on the >>> existing po files for 3.4.1. >>> 05/21 RC1 >>> 06/04 RC2 >>> 06/18 RC3 (optional), can be GA already >>> 06/25 GA -> this should be our final target >>> >>> >>> This is a proposal based on the ongoing work that I no. Please let me >>> know if I missed something important. >>> >>> Regular developer builds 1/week + nightly builds >>> >>> Based on feedback and potential changes I will put this in the wiki later. >>> >>> Important is from my pov that we start talking about the improvements >>> that we make in public. It should be very clear for anybody where the >>> real important features and improvement for OpenOffice or derivatives >>> are coming from ;-) > > I will try to give n update on the current plan. > > The sidebar branch is not yet integrated but I expect that it will be > finished next week latest. That means we will have a delay of some days > here. As soon as I have concrete dates I will update the plan in the wiki. > > Some further things are ongoing and we should try to finish this work > soon (2 weeks) to have the stuff in place and can start or concentrate > on bug fixing and stabilization. > > Juergen > > > > > >>> >>> >>> Juergen >>> >> > > > - > 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
Re : Re: [RELEASE]: proposed schedule for AOO 4.0
Hi, Does some cycle exist about releasing of OOo? Because since the schedule, it seems that OOo 4.0 will not include current work about accessibility. It is a pitty as I think it is a major contribution and it would be a pitty if we should wait for end of 2014 to see it. It seems things could be ready for novembre. Do you think we can hope progress during 1st six months 2014? In a 4.1 release I get? Regards, - Mail d'origine - De: Jürgen Schmidt À: dev@openoffice.apache.org Envoyé: Thu, 04 Apr 2013 10:46:16 +0200 (CEST) Objet: Re: [RELEASE]: proposed schedule for AOO 4.0 On 2/20/13 11:32 AM, Jürgen Schmidt wrote: > On 2/20/13 10:46 AM, Jürgen Schmidt wrote: >> Hi, >> >> we make good progress with the sidebar work which is done on the branch. >> The sidebar will be the most visible and important change for 4.0 (by >> the way I like what I have seen so far). We come closer to the point >> where we should talk about a more detailed schedule. >> >> I would like to start with the following proposal and still many steps >> have to be defined in more detail. >> >> 03/01 function verification test will start, define test case, prepare >> tests etc. >> 04/04 integrate sidebar branch in trunk, other new features should be >> finished by this date as well. > > I missed to add that the art work (logo, icons, etc. should be finished > at this date as well) > >> 04/05 - 05/15 regression testing will be start on trunk >> 04/05 - 05/15 bugfix and stabilization, no feature development >> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new >> strings. This can change when we know exactly how many new strings we >> will have. But translation for new languages can already work on the >> existing po files for 3.4.1. >> 05/21 RC1 >> 06/04 RC2 >> 06/18 RC3 (optional), can be GA already >> 06/25 GA -> this should be our final target >> >> >> This is a proposal based on the ongoing work that I no. Please let me >> know if I missed something important. >> >> Regular developer builds 1/week + nightly builds >> >> Based on feedback and potential changes I will put this in the wiki later. >> >> Important is from my pov that we start talking about the improvements >> that we make in public. It should be very clear for anybody where the >> real important features and improvement for OpenOffice or derivatives >> are coming from ;-) I will try to give n update on the current plan. The sidebar branch is not yet integrated but I expect that it will be finished next week latest. That means we will have a delay of some days here. As soon as I have concrete dates I will update the plan in the wiki. Some further things are ongoing and we should try to finish this work soon (2 weeks) to have the stuff in place and can start or concentrate on bug fixing and stabilization. Juergen >> >> >> Juergen >> > - 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
Re: [RELEASE]: proposed schedule for AOO 4.0
On 2/20/13 11:32 AM, Jürgen Schmidt wrote: > On 2/20/13 10:46 AM, Jürgen Schmidt wrote: >> Hi, >> >> we make good progress with the sidebar work which is done on the branch. >> The sidebar will be the most visible and important change for 4.0 (by >> the way I like what I have seen so far). We come closer to the point >> where we should talk about a more detailed schedule. >> >> I would like to start with the following proposal and still many steps >> have to be defined in more detail. >> >> 03/01 function verification test will start, define test case, prepare >> tests etc. >> 04/04 integrate sidebar branch in trunk, other new features should be >> finished by this date as well. > > I missed to add that the art work (logo, icons, etc. should be finished > at this date as well) > >> 04/05 - 05/15 regression testing will be start on trunk >> 04/05 - 05/15 bugfix and stabilization, no feature development >> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new >> strings. This can change when we know exactly how many new strings we >> will have. But translation for new languages can already work on the >> existing po files for 3.4.1. >> 05/21 RC1 >> 06/04 RC2 >> 06/18 RC3 (optional), can be GA already >> 06/25 GA -> this should be our final target >> >> >> This is a proposal based on the ongoing work that I no. Please let me >> know if I missed something important. >> >> Regular developer builds 1/week + nightly builds >> >> Based on feedback and potential changes I will put this in the wiki later. >> >> Important is from my pov that we start talking about the improvements >> that we make in public. It should be very clear for anybody where the >> real important features and improvement for OpenOffice or derivatives >> are coming from ;-) I will try to give n update on the current plan. The sidebar branch is not yet integrated but I expect that it will be finished next week latest. That means we will have a delay of some days here. As soon as I have concrete dates I will update the plan in the wiki. Some further things are ongoing and we should try to finish this work soon (2 weeks) to have the stuff in place and can start or concentrate on bug fixing and stabilization. Juergen >> >> >> Juergen >> > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE]: proposed schedule for AOO 4.0
Hi, all, I just posted the proposed release schedule to 4.0 planning wiki: https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning - Shenfeng (Simon) 2013/2/22 janI > On 21 February 2013 18:27, Andrea Pescetti wrote: > > > On 20/02/2013 Jürgen Schmidt wrote: > > > >> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > >> strings. This can change when we know exactly how many new strings we > >> will have. But translation for new languages can already work on the > >> existing po files for 3.4.1. > >> > > > > Looks good, but if the new infrastructure allows it by that moment we > > should aim at either having a usable Pootle instance (I mean, one where > new > > volunteers can work) or all the PO files ready, so that we can point > > volunteers to PO files with no need to prepare them explicitly. > > > Status on l10tools is that I am testing generation of po files at the > moment. > > It is a very timeconsuming work, because I need to be 100% sure that > genLang extract at least the same information as the current tools. genLang > extracts a bit more information in some cases e.g.: > - there a a number of messages marked [en-US] that are currently not > extracted > - some keyparts are not extracted correctly, typically missing root part of > key > - Itemlist, is only extracted with itemnumber, but often the items have > names > > For these cases I modify the sdf file (manually correcting the error if you > will), but that has to be done for all languages, so that I can later match > keys. > > Once this part is finished, genLang can generate po files directly. > > genLang can already read po files, but need to be able to merge (extract > from source, merge with existing po files) and write updated po files for > all languages. The part is only rudimentary programmed > > and finally genLang will write new source files, containing the selected > languages, this part is more or less programmed, but totally untested. > > Once the community has accepted genLang, we (I cannot do that alone) need > to integrate it into the build process. > > so as you can see, I have a full schedule ahead of me, but I am still > confident that I will finish in time for 4.0. > > Please remember that as soon as the extract works, we have po files > directly available in svn...and if everything fails, we can use the current > method to convert them back to source files. > > have a nice day. > Jan I. > > Ps. the l10n commits at the moment is NOT the full picture, but parts I > need tested on different platforms, once l10n is ready for others I will > announce it on the list. > > > > I've see some l10n-related commits (good!), but I don't know where we are > > precisely. > > > > > > Important is from my pov that we start talking about the improvements > >> that we make in public. > >> > > > > I agree. A couple of screenshot and a brief description are often enough, > > and I would use the posts to recruit some new development volunteers too. > > > > Regards, > > Andrea. > > >
Re: [RELEASE]: proposed schedule for AOO 4.0
On 21 February 2013 18:27, Andrea Pescetti wrote: > On 20/02/2013 Jürgen Schmidt wrote: > >> 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new >> strings. This can change when we know exactly how many new strings we >> will have. But translation for new languages can already work on the >> existing po files for 3.4.1. >> > > Looks good, but if the new infrastructure allows it by that moment we > should aim at either having a usable Pootle instance (I mean, one where new > volunteers can work) or all the PO files ready, so that we can point > volunteers to PO files with no need to prepare them explicitly. > Status on l10tools is that I am testing generation of po files at the moment. It is a very timeconsuming work, because I need to be 100% sure that genLang extract at least the same information as the current tools. genLang extracts a bit more information in some cases e.g.: - there a a number of messages marked [en-US] that are currently not extracted - some keyparts are not extracted correctly, typically missing root part of key - Itemlist, is only extracted with itemnumber, but often the items have names For these cases I modify the sdf file (manually correcting the error if you will), but that has to be done for all languages, so that I can later match keys. Once this part is finished, genLang can generate po files directly. genLang can already read po files, but need to be able to merge (extract from source, merge with existing po files) and write updated po files for all languages. The part is only rudimentary programmed and finally genLang will write new source files, containing the selected languages, this part is more or less programmed, but totally untested. Once the community has accepted genLang, we (I cannot do that alone) need to integrate it into the build process. so as you can see, I have a full schedule ahead of me, but I am still confident that I will finish in time for 4.0. Please remember that as soon as the extract works, we have po files directly available in svn...and if everything fails, we can use the current method to convert them back to source files. have a nice day. Jan I. Ps. the l10n commits at the moment is NOT the full picture, but parts I need tested on different platforms, once l10n is ready for others I will announce it on the list. I've see some l10n-related commits (good!), but I don't know where we are > precisely. > > > Important is from my pov that we start talking about the improvements >> that we make in public. >> > > I agree. A couple of screenshot and a brief description are often enough, > and I would use the posts to recruit some new development volunteers too. > > Regards, > Andrea. >
Re: [RELEASE]: proposed schedule for AOO 4.0
On 20/02/2013 Jürgen Schmidt wrote: 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new strings. This can change when we know exactly how many new strings we will have. But translation for new languages can already work on the existing po files for 3.4.1. Looks good, but if the new infrastructure allows it by that moment we should aim at either having a usable Pootle instance (I mean, one where new volunteers can work) or all the PO files ready, so that we can point volunteers to PO files with no need to prepare them explicitly. I've see some l10n-related commits (good!), but I don't know where we are precisely. Important is from my pov that we start talking about the improvements that we make in public. I agree. A couple of screenshot and a brief description are often enough, and I would use the posts to recruit some new development volunteers too. Regards, Andrea.
Re: [RELEASE]: proposed schedule for AOO 4.0
On Wed, Feb 20, 2013 at 1:46 AM, Jürgen Schmidt wrote: > Hi, > > we make good progress with the sidebar work which is done on the branch. > The sidebar will be the most visible and important change for 4.0 (by > the way I like what I have seen so far). We come closer to the point > where we should talk about a more detailed schedule. > > I would like to start with the following proposal and still many steps > have to be defined in more detail. > > 03/01 function verification test will start, define test case, prepare > tests etc. > 04/04 integrate sidebar branch in trunk, other new features should be > finished by this date as well. > 04/05 - 05/15 regression testing will be start on trunk > 04/05 - 05/15 bugfix and stabilization, no feature development > 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > strings. This can change when we know exactly how many new strings we > will have. But translation for new languages can already work on the > existing po files for 3.4.1. > 05/21 RC1 > 06/04 RC2 > 06/18 RC3 (optional), can be GA already > 06/25 GA -> this should be our final target > > > This is a proposal based on the ongoing work that I no. Please let me > know if I missed something important. > > Regular developer builds 1/week + nightly builds > > Based on feedback and potential changes I will put this in the wiki later. > > Important is from my pov that we start talking about the improvements > that we make in public. It should be very clear for anybody where the > real important features and improvement for OpenOffice or derivatives > are coming from ;-) > > > Juergen > I would hope that somewhere in this mix we make the current Base issues vis a vis HSQLDB version (performance issues) and java version issues (we REALLY need to get off 6 and onto 7 with whatever we know about future versions) high priorities. Maybe in the next week or so, we can get an update on the progress of this area (several folks are working on this I think). Generally though, I think this time frame looks workable. Thanks for this posting. -- MzK "Achieving happiness requires the right combination of Zen and Zin."
Re: [RELEASE]: proposed schedule for AOO 4.0
On Wed, Feb 20, 2013 at 4:46 AM, Jürgen Schmidt wrote: > Hi, > > we make good progress with the sidebar work which is done on the branch. > The sidebar will be the most visible and important change for 4.0 (by > the way I like what I have seen so far). We come closer to the point > where we should talk about a more detailed schedule. > > I would like to start with the following proposal and still many steps > have to be defined in more detail. > > 03/01 function verification test will start, define test case, prepare > tests etc. > 04/04 integrate sidebar branch in trunk, other new features should be > finished by this date as well. > 04/05 - 05/15 regression testing will be start on trunk > 04/05 - 05/15 bugfix and stabilization, no feature development > 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > strings. This can change when we know exactly how many new strings we > will have. But translation for new languages can already work on the > existing po files for 3.4.1. > 05/21 RC1 > 06/04 RC2 > 06/18 RC3 (optional), can be GA already > 06/25 GA -> this should be our final target > > > This is a proposal based on the ongoing work that I no. Please let me > know if I missed something important. > Have we resolved the question of whether the extensions API is changing? If so we probably need an "API freeze" date (maybe the same as feature freeze), so there is time for extension authors to prepare. So probably a set of things to aim for by that date: 1) API freeze, 2) a good build of AOO 4.0 and SDK, 3) Blog post for extension developers letting them know what will be changing. -Rob > Regular developer builds 1/week + nightly builds > > Based on feedback and potential changes I will put this in the wiki later. > > Important is from my pov that we start talking about the improvements > that we make in public. It should be very clear for anybody where the > real important features and improvement for OpenOffice or derivatives > are coming from ;-) > > > Juergen
Re: [RELEASE]: proposed schedule for AOO 4.0
I will be driving the branding effort from the marketing team. I agree design work needs to be done early. 04/04 is a good target. On Wed, Feb 20, 2013 at 5:32 AM, Jürgen Schmidt wrote: > On 2/20/13 10:46 AM, Jürgen Schmidt wrote: > > Hi, > > > > we make good progress with the sidebar work which is done on the branch. > > The sidebar will be the most visible and important change for 4.0 (by > > the way I like what I have seen so far). We come closer to the point > > where we should talk about a more detailed schedule. > > > > I would like to start with the following proposal and still many steps > > have to be defined in more detail. > > > > 03/01 function verification test will start, define test case, prepare > > tests etc. > > 04/04 integrate sidebar branch in trunk, other new features should be > > finished by this date as well. > > I missed to add that the art work (logo, icons, etc. should be finished > at this date as well) > > > 04/05 - 05/15 regression testing will be start on trunk > > 04/05 - 05/15 bugfix and stabilization, no feature development > > 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > > strings. This can change when we know exactly how many new strings we > > will have. But translation for new languages can already work on the > > existing po files for 3.4.1. > > 05/21 RC1 > > 06/04 RC2 > > 06/18 RC3 (optional), can be GA already > > 06/25 GA -> this should be our final target > > > > > > This is a proposal based on the ongoing work that I no. Please let me > > know if I missed something important. > > > > Regular developer builds 1/week + nightly builds > > > > Based on feedback and potential changes I will put this in the wiki > later. > > > > Important is from my pov that we start talking about the improvements > > that we make in public. It should be very clear for anybody where the > > real important features and improvement for OpenOffice or derivatives > > are coming from ;-) > > > > > > Juergen > > > >
Re: [RELEASE]: proposed schedule for AOO 4.0
On 2/20/13 10:46 AM, Jürgen Schmidt wrote: > Hi, > > we make good progress with the sidebar work which is done on the branch. > The sidebar will be the most visible and important change for 4.0 (by > the way I like what I have seen so far). We come closer to the point > where we should talk about a more detailed schedule. > > I would like to start with the following proposal and still many steps > have to be defined in more detail. > > 03/01 function verification test will start, define test case, prepare > tests etc. > 04/04 integrate sidebar branch in trunk, other new features should be > finished by this date as well. I missed to add that the art work (logo, icons, etc. should be finished at this date as well) > 04/05 - 05/15 regression testing will be start on trunk > 04/05 - 05/15 bugfix and stabilization, no feature development > 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new > strings. This can change when we know exactly how many new strings we > will have. But translation for new languages can already work on the > existing po files for 3.4.1. > 05/21 RC1 > 06/04 RC2 > 06/18 RC3 (optional), can be GA already > 06/25 GA -> this should be our final target > > > This is a proposal based on the ongoing work that I no. Please let me > know if I missed something important. > > Regular developer builds 1/week + nightly builds > > Based on feedback and potential changes I will put this in the wiki later. > > Important is from my pov that we start talking about the improvements > that we make in public. It should be very clear for anybody where the > real important features and improvement for OpenOffice or derivatives > are coming from ;-) > > > Juergen >
[RELEASE]: proposed schedule for AOO 4.0
Hi, we make good progress with the sidebar work which is done on the branch. The sidebar will be the most visible and important change for 4.0 (by the way I like what I have seen so far). We come closer to the point where we should talk about a more detailed schedule. I would like to start with the following proposal and still many steps have to be defined in more detail. 03/01 function verification test will start, define test case, prepare tests etc. 04/04 integrate sidebar branch in trunk, other new features should be finished by this date as well. 04/05 - 05/15 regression testing will be start on trunk 04/05 - 05/15 bugfix and stabilization, no feature development 04/08 - 05/15 translation -> I guessed ~5 weeks for updating the new strings. This can change when we know exactly how many new strings we will have. But translation for new languages can already work on the existing po files for 3.4.1. 05/21 RC1 06/04 RC2 06/18 RC3 (optional), can be GA already 06/25 GA -> this should be our final target This is a proposal based on the ongoing work that I no. Please let me know if I missed something important. Regular developer builds 1/week + nightly builds Based on feedback and potential changes I will put this in the wiki later. Important is from my pov that we start talking about the improvements that we make in public. It should be very clear for anybody where the real important features and improvement for OpenOffice or derivatives are coming from ;-) Juergen
