Re: Om2009 release plan
On Tue, 2009-04-07 at 22:53 +0200, Ed Kapitein wrote: Hi, With the remainder of march being behind us, can you give an update on the release plan? Kind regards, Ed Hi Ed, We are going to put a testing image together for the end of this week. Because of OM reduced staffing levels some other dates mentioned in the Release Plan will probably slide a bit. Most of the features mentioned in the release plan have been implemented. A few still need some work and hopefully we can get those finished in short order. Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 release plan
On Wed, 2009-04-08 at 13:48 -0400, Mark Shewmaker wrote: Great to hear that. I'm sending this question privately only because I don't want it to sound negative in any sense by sending it publicly, but..do you know if there is a release goal for this release for opkg update and upgrades to be able to complete without the infamous Signature check failed errors? As it's not really negative and other people might have the same question, I'm bouncing it back to the list. (The claim in http://docs.openmoko.org/trac/ticket/1870 that this is fixed notwithstanding, that's not the case now.) If you try either the unstable or experimental images you will see that it is already fixed for Om2009. Since the fundamental problem has to do with how the repository is set up, and you are your coworkers are setting that up for this testing image this week, I figure this is probably the best time to ask. Asking questions anytime should provoke thought. Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Om2009 release plan
Spring a time for new beginnings and we have a plan. An Om2009 release plan that is. For the remainder of March we are going to be integrating. We're going put FSO milestone 5.5, the stable kernel, paroli and the new xorg-glamo drivers together and make our most stable distro ever. Any incomplete features need to be finished and integrated before the end of March. The builds in March will be called Alpha builds, and will receive only partial testing. The following features already have an owner and will be taken care of before the end of March: phone calls incoming and outgoing sms incoming and outgoing simple phone book (no images) call log charging suspend and resume alarm clock resume speed 2 seconds boot time 2 minutes screen lock battery indicator (gta01 and gta02 battery) gsm indicator Then there are still features looking for someone to help bring them in before the end of March: Settings application gprs edge user changeable ring tones bluetooth wifi led indication for missed calls or sms sliding in UI In April we start with Beta builds and full testing. From then on only critical features and bug fixes will be backported into the branch. If you're brave and test with us please use the bug filing procedure below. During the Beta phase in April and May, the phone will become fully functional. Full testing will be weekly at this point to try and nail the stability. Any remaining bugs will need closing. This is when we need to nail all the showstopper bugs and we're going to need your ( the communities help ). Your responsibility will be to find bugs and make sure they get into trac.openmoko.org. When filing a bug : 1) Don't request new features or enhancements during this period. They will slow us down. 2) search 3 different ways to make sure it's not a duplicate. Duplicates will slow us down. The couple of extra minutes you try to search will save us a lot of time and may even find you a solution. During your search if you find bugs that might depend on one another add it to the comments. 3) attach your log files ( anything in /tmp or /var/log that ends in log ). 4) include as much of a description as you can. 5) include patches. They make fixing the bugs easier. At the end of May we'll start generating release candidates (RC builds). If we all pull together we should be able to get it out in the second week of June. If it's not quite right yet we'll keep doing release candidates until it is. I don't want to jinx it by saying the release is going to be Om2009.x ,we'll leave off the x and aim for June. Who's in? And about the enhancements and feature requests I'm serious they kill schedules so if you want us to make it don't ask for anything that's not in the UI spec ( to be released at http://www.paroli-project.org/, shortly I hope ). Angus Ainslie Openmoko Distribution Maintainer ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 release plan
On Mon, Mar 2, 2009 at 6:14 PM, Angus Ainslie nyt...@openmoko.org wrote: Spring a time for new beginnings and we have a plan. An Om2009 release plan that is. Thanks for your update great news, really appreciate it!! It'll be interesting to see what'll the result be like :) r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 release plan
On Mon, 2009-03-02 at 09:14 -0700, Angus Ainslie wrote: During the Beta phase in April and May, the phone will become fully functional. Full testing will be weekly at this point to try and nail the stability. Any remaining bugs will need closing. This is when we need to nail all the showstopper bugs and we're going to need your ( the communities help ). Your responsibility will be to find bugs and make sure they get into trac.openmoko.org. Well there's the first oops in the plan. The correct url for bug filing would be : http://docs.openmoko.org/trac/ Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 release plan
On Mon, 02 Mar 2009 09:14:56 -0700 Angus Ainslie nyt...@openmoko.org wrote: The following features already have an owner and will be taken care of before the end of March: phone calls incoming and outgoing sms incoming and outgoing simple phone book (no images) call log charging suspend and resume alarm clock resume speed 2 seconds boot time 2 minutes screen lock battery indicator (gta01 and gta02 battery) gsm indicator Then there are still features looking for someone to help bring them in before the end of March: Settings application gprs edge user changeable ring tones bluetooth wifi led indication for missed calls or sms sliding in UI Two questions. What about package management GUI - is one planned to be included? Can you clarify sliding in UI? j ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 release plan
Hej, Can you clarify sliding in UI? Sliding here means any form of scrolling and dragging. Scrolling of lists such as contacts, messages etc and sliding of items in that list t have secondary functions connected to those. Our problem here is, that the py bindings for etk are broken (and the scrolling would be slow), in elm it seems to be slow using py as well and implementing it in edje/embryo directly is a lot of tricky coding. /mirko ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
