Greg Smith's Weekly Report

[rihoward1 at gmail.com]

Greg,

Thanks for fixing http://wiki.laptop.org/go/Activities/Joyride and  
make it reference the correct version of
Develop.  Tested it and software updater now downloads Develop V35.  
Now maybe people can start looking for valid bugs and give the  
developer useful feedback.
Develop launches nicely in 8.2-759.

I went ahead and updated the reference to Colors! to Colors! V4 and  
software updater successfully downloaded that it.

The architecture of the wiki activity group pages is interesting to  
say the list.

Robert H.



On Sep 5, 2008, at 11:23 AM, Greg Smith wrote:

> Hi Robert,
>
> Thanks for the info. We should probably do this on the list so  
> others learn too if you don't mind. If you reply again, just add in  
> devel.
>
> I edited the Joyride page (http://wiki.laptop.org/go/Activities/ 
> Joyride)
>  to point to the new Devel v35
>
> I just updated the activity bundle value by copying and pasting it  
> from the main activities page: http://wiki.laptop.org/go/Activities
>
> and I updated the version value to 35.
>
> Try running the SW updater again and let me know if that fetches  
> the right one. If so, maybe we can close another bug!
>
> The policy on where the SW updater gets stuff is at:
> http://wiki.laptop.org/go/Software_update
>
> Can you try to fix Colors too if you know where the right one is  
> and how to edit its wiki page from those instructions?
>
> Scott,
>
> This could be an ongoing challenge if we have the SW updater coded  
> to use our wiki. Its a little complicated to figure out what  
> version you are using (e.g. Joyride, shipping, peru etc) then to  
> determine where the SW updater is  pulling from and then update the  
> right page.
>
> Its solvable but needs a lot of communication and takes some time.  
> I wonder if there is some semantic wiki solution here to change it  
> once and have it update everywhere....
>
> Also, we still need a way to post older versions of activities when  
> they are not backward compatible (e.g. if develop 35 doesn't run on  
> 656 or 708, we need to say that on the main page and post the one  
> (e.g. v25) that does run on older releases somewhere).
>
> If we edit the main activities page, to include some more fields in  
> the table will that be a problem for SW updater?
>
> Skierpage,
>
> If we can edit activities page safely do you feel up to making some  
> edits there... Maybe propose something on devel then we can approve  
> and execute. Let me know if what we are looking for there is not  
> clear.
>
> BTW don't mean to give you all the hard problems, its just that   
> you do great work so I try you first :-)
>
> Thanks,
>
> Greg S
>
> rihoward1 at gmail.com wrote:
>> Regarding item 1. I came across http://dev.laptop.org/ticket/7716  
>> "Develop doesn't launch" (not a blocker) for which I provided a  
>> diagnoses.
>>  I left the ticket as Diagnose because I did not know were to move  
>> it to next as it did not seem to be a code problem but an  
>> infrastructure problem.   Basically the wrong version of Develop  
>> is being fetched by software upgrade for joyride activities group.  
>> (Also there is a caveat for using it on old builds were a patch  
>> has to be applied to the journal).  This is a low hanging bit of  
>> fruit that could easily be fixed if I knew the correct process for  
>> updating the file that gets fetched by software update.
>> I have also noticed this problem with Colors! for the joyride  
>> activities group were an old version is being fetched instead of  
>> the latest.
>> Late for work so will follow up later if you need more information..
>> Robert H.
>> On Sep 5, 2008, at 8:55 AM, Greg Smith wrote:
>>> Hi All,
>>>
>>> We write a weekly report for the OLPC management and employees.
>>>
>>> In order to keep the community involved, motivated and  
>>> knowledgeable,
>>> Michael suggested we share it with this list.
>>>
>>> Its FYI but I'm open to help, comments or suggestions, as always.
>>>
>>> Thanks,
>>>
>>> Greg S
>>>
>>> **************
>>> Status against last weeks goals:
>>> 1 - Identify, triage and clarify 8.2 blocker bugs.
>>> GS - Done. Triaged all incoming bugs for 8.2. Helped get the 8.2  
>>> release
>>> down to a manageable set of blocking bugs which must be fixed. See:
>>> http://dev.laptop.org/report/28
>>> As of this writing, there are only 9 left with the next action of
>>> Diagnose, Design or Code!
>>>
>>> 2 - Update 8.2 release notes
>>> GS - Made some progress with review of update instructions. Added  
>>> text
>>> to all open bugs in preparation for final review:
>>> http://wiki.laptop.org/go/Release_Notes/ 
>>> 8.2.0#Notable_Open_Bugs_In_This_Release
>>> Also read and commented on the new manual which will be linked from
>>> release notes when ready.
>>>
>>> 3 - Update 9.1 page with more requirements. Re-check that all  
>>> Peru input
>>> is in 9.1 page. Add Uruguay, Haiti, Rwanda, Birmingham and Mongolia
>>> requirements.
>>> GS - Done for Peru. Some Uruguay items in but not all. Not done  
>>> for the
>>> rest. Also started engagement with sugar list re: their 0.84  
>>> which maps
>>> to 9.1.
>>>
>>> 4 - Prune outdated material off OLPC home page:
>>> http://wiki.laptop.org/go/The_OLPC_Wiki
>>> GS - Not done.
>>>
>>> 5 - Follow up on Cmap tools
>>> GS - Done. Proposed X windows wrapper activity. CMap
>>> developers will consider it and are looking in to the feasibility  
>>> now.
>>>
>>> ****************
>>> Goals for next week in priority order:
>>> - Identify, triage and clarify 8.2 blocker bugs. Help get to a well
>>> defined final release schedule.
>>>
>>> - Update 8.2 release notes
>>>
>>> - Write 8.2 marketing launch plan. To include lists, web sites  
>>> and other
>>> ideas for getting the word out. Once done, this will sit on the  
>>> shelf
>>> until the release is final.
>>>
>>> - Update 9.1 page with more requirements. Add Uruguay, Haiti,  
>>> Rwanda,
>>> Birmingham, Mongolia, Ethiopia, others. Start writing strategy  
>>> section
>>> and set schedule.
>>>
>>> - Find engineering lead for 8.2.1. If none is identified, start  
>>> laying
>>> out the parameters anyway (e.g. date, target customers, goals,  
>>> target
>>> bug fixes and featurettes, etc.).
>>>
>>> - Find a volunteer and partner to write Beta/Early Field Trial  
>>> plan. The
>>> plan should get pre-release code in to real classes at target  
>>> deployment
>>> countries for comment and review prior to 8.2.1 release.
>>>
>>> - Update deployments page with latest data, improve timeline and add
>>> timeline to releases page.
>>>
>>> - Prune outdated material off OLPC wiki home page.
>>>
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at lists.laptop.org
>>> http://lists.laptop.org/listinfo/devel