On Mon, 2008-06-23 at 10:36 -0400, Martin Langhoff wrote:
> On Sun, Jun 22, 2008 at 11:29 PM, David Farning <[EMAIL PROTECTED]> wrote:
> > Two releases per year make sense. Particularly when add in the fact that
> > we have two hemispheres with opposing springs and falls.
>
> Only if you assume w
On Mon, Jun 23, 2008 at 11:18 AM, David Farning <[EMAIL PROTECTED]> wrote:
> As Kim stated earlier, in the end this becomes a cost of effort issue.
> >From a developer point of view the more releases the better. From a
> support perspective maintaining several long releases can quickly suck
> the
On Sun, Jun 22, 2008 at 11:29 PM, David Farning <[EMAIL PROTECTED]> wrote:
> Two releases per year make sense. Particularly when add in the fact that
> we have two hemispheres with opposing springs and falls.
Only if you assume we can get countries in lockstep with us. Any
number of things can di
Hi Kim -
On Sun, Jun 22, 2008 at 3:02 PM, Kim Quirk <[EMAIL PROTECTED]> wrote:
> Secondly, I am proposing that our Support team can only support one
> major release along with the current one. With school systems being
> run on yearly basis, this would suggest that we plan for 2 major
> releases p
On Sun, 2008-06-22 at 15:02 -0400, Kim Quirk wrote:
> Deepak (and others interested in support),
>
> This is a good question and we've talked about it from time to time.
>
> The OLPC Support planning is really just now underway. We've made some
> good progress on the Hardware side of support (spa
2 releases per year is the right way to go. I can't imagine using more
than two XO releases per year, barring an important security or bug fix.
It is just too time consuming to test out a new release and more
importantly, train the teachers about any new features or anomalies.
I hope to update our
Deepak (and others interested in support),
This is a good question and we've talked about it from time to time.
The OLPC Support planning is really just now underway. We've made some
good progress on the Hardware side of support (spare parts, repair
centers, warranty, etc); and now we need some f
> I've been thikning about update issues a bit and was wondering
> if we have plans/processes in place to handle maintaince of multiple
> releases?
My perception of our "basic purpose" is that we're in the business of
creating reference OSes which can be modified "with OLPC support" at
fixed poi
On Jun 21 2008, at 20:10, Kim Quirk was caught saying:
> Sounds great! We've discussed a similar thing here, but I don't
> believe there has been any time for that.
>
> For g1g1 people there could possibly be 2 options - 1. Upgrade from
> 656 to 8.1.1, with the automatic second step of adding acti
Sounds great! We've discussed a similar thing here, but I don't
believe there has been any time for that.
For g1g1 people there could possibly be 2 options - 1. Upgrade from
656 to 8.1.1, with the automatic second step of adding activities; or
2. Cleanstall to the 8.1.1 build that already includes
Hello all,
one of the things that repeatedly came up during a greet meetup at
Friends Community School near DC which we had earlier today was that
updating the software on the XOs was still too painful for many people.
So especially with G1G1 2008 looming on the horizon I'm thinking that it
mi
11 matches
Mail list logo
