Thanks a lot Jerry and Gonzalo,
2013/9/2 Gonzalo Odiard gonz...@laptop.org:
Yes, you are right about the schedule.
My comment was based in my perception (can be wrong)
of the work in the last weeks. Following the pull requests,
most of the work is related to web, only a few were related to
Hello,
0.99.3 is due tomorrow and with it the code freeze. We need to decide what
to do.
I propose we don't freeze and instead we keep releasing 0.99.x every four
weeks, until we feel we have done enough testing and bug fixing. This is
not what you are supposed to do with time based releases but
Release 0.99.3 as is is good, because we will have rpms and that
should facilitate testing.
I prefer we try hard to follow the schedule, remember usually is aligned
with Fedora and other projects.
Gonzalo
On Mon, Sep 2, 2013 at 3:21 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
Hello,
0.99.3
To be clear, are you saying we should code freeze tomorrow? I couldn't find
a definition of the freeze in the wiki but the GNOME one seems accurate.
Hard Code Freeze
This is a late freeze to avoids sudden last-minute accidents which could
risk the stability that should have been reached at this
Yes. Only fixes allowed, we can discuss if double review is needed or not.
Gonzalo
On Mon, Sep 2, 2013 at 3:38 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
To be clear, are you saying we should code freeze tomorrow? I couldn't find
a definition of the freeze in the wiki but the GNOME one
Hi,
hard code freeze is way more strict than bug fixes only, that's more a
feature freeze.
In code freeze only very critical stuff is supposed to land. The double
approval is in addition to the review, to ensure only essential fixes lands.
Just want to be clear what we would be buying into :)
I think we didn't had a bug fixes only stage yet on 0.100 cycle,
then does not have too much sense jump to regressions only, right?
Gonzalo
On Mon, Sep 2, 2013 at 3:48 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
Hi,
hard code freeze is way more strict than bug fixes only, that's more a
On 2 September 2013 20:52, Jerry Vonau je...@laptop.org.au wrote:
On 2 September 2013 13:38, Daniel Narvaez dwnarv...@gmail.com wrote:
To be clear, are you saying we should code freeze tomorrow? I couldn't
find a definition of the freeze in the wiki but the GNOME one seems
accurate.
Hard
On Mon, Sep 2, 2013 at 12:21 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
I propose we don't freeze and instead we keep releasing 0.99.x every four
weeks, until we feel we have done enough testing and bug fixing. This is not
what you are supposed to do with time based releases but I'd rather
We have been in feature freeze, which seems the closest to what you call
bug fixes only, since 31 July. (I would not define hard code freeze as
regressions only, even though being a regression is of course part of
what needs to be considered when deciding if landing a change or not).
On 2
On 2 September 2013 21:00, Daniel Drake d...@laptop.org wrote:
On Mon, Sep 2, 2013 at 12:21 PM, Daniel Narvaez dwnarv...@gmail.com
wrote:
I propose we don't freeze and instead we keep releasing 0.99.x every four
weeks, until we feel we have done enough testing and bug fixing. This is
not
On Mon, Sep 2, 2013 at 2:38 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
To be clear, are you saying we should code freeze tomorrow? I couldn't find
a definition of the freeze in the wiki but the GNOME one seems accurate.
Hard Code Freeze
This is a late freeze to avoids sudden last-minute
2013/9/2 Daniel Narvaez dwnarv...@gmail.com:
On 2 September 2013 21:00, Daniel Drake d...@laptop.org wrote:
On Mon, Sep 2, 2013 at 12:21 PM, Daniel Narvaez dwnarv...@gmail.com
wrote:
I propose we don't freeze and instead we keep releasing 0.99.x every
four
weeks, until we feel we have
On Mon, Sep 02, 2013 at 04:36:31PM -0300, Manuel Quiñones wrote:
I agree. We should delay the hard freeze for 4 weeks and hope that by
that time we get some testing and bugfixing.
How can I test on an XO?
--
James Cameron
http://quozl.linux.org.au/
2013/9/2 James Cameron qu...@laptop.org:
On Mon, Sep 02, 2013 at 04:36:31PM -0300, Manuel Quiñones wrote:
I agree. We should delay the hard freeze for 4 weeks and hope that by
that time we get some testing and bugfixing.
How can I test on an XO?
That's the question, James. We don't have
On Mon, Sep 02, 2013 at 09:09:09PM -0300, Manuel Quiñones wrote:
2013/9/2 James Cameron qu...@laptop.org:
On Mon, Sep 02, 2013 at 04:36:31PM -0300, Manuel Quiñones wrote:
I agree. We should delay the hard freeze for 4 weeks and hope that by
that time we get some testing and bugfixing.
On 2 September 2013 19:20, James Cameron qu...@laptop.org wrote:
On Mon, Sep 02, 2013 at 09:09:09PM -0300, Manuel Quiñones wrote:
2013/9/2 James Cameron qu...@laptop.org:
On Mon, Sep 02, 2013 at 04:36:31PM -0300, Manuel Quiñones wrote:
I agree. We should delay the hard freeze for 4
On Mon, 2013-09-02 at 19:37 -0500, Jerry Vonau wrote:
On 2 September 2013 19:20, James Cameron qu...@laptop.org wrote:
On Mon, Sep 02, 2013 at 09:09:09PM -0300, Manuel Quiñones
wrote:
2013/9/2 James Cameron qu...@laptop.org:
On Mon, Sep 02, 2013 at
A few notes about the rpms Jerry shared:
* While is based on 0.100, have a few patches needed by AU,
we didn't have time to upstream.
* The patches are applied on the rpms, to make clear the separation of
the changes.
* specs and patches are here: https://github.com/godiard/au1b_rpms
We don't
Yes, you are right about the schedule.
My comment was based in my perception (can be wrong)
of the work in the last weeks. Following the pull requests,
most of the work is related to web, only a few were related to bugs.
Part of the problem, like other said, is actually
we don't have images
On Mon, Sep 02, 2013 at 07:37:17PM -0500, Jerry Vonau wrote:
We have some rpms that are testable: http://dev.laptop.org/~gonzalo/AU1B/
AU1B_4.zip
Thanks, these work fine for me. I've already been able to raise a
bug with journal backup.
http://bugs.sugarlabs.org/ticket/4616
(Background
Thanks!
Gonzalo
On Mon, Sep 2, 2013 at 11:03 PM, James Cameron qu...@laptop.org wrote:
On Mon, Sep 02, 2013 at 07:37:17PM -0500, Jerry Vonau wrote:
We have some rpms that are testable: http://dev.laptop.org/~gonzalo/AU1B/
AU1B_4.zip
Thanks, these work fine for me. I've already been able to
On 08/28/2013 11:03 AM, Gonzalo Odiard wrote:
I agree in the need of testing.
Testing is more difficult this cycle because:
* We have less developers working.
* We don't have the images we usually used to test on our main
hardware platform (XO*) yet.
I don't know if any test is done now on
On 08/29/2013 05:35 AM, Thomas Gilliard wrote:
On 08/28/2013 11:03 AM, Gonzalo Odiard wrote:
I agree in the need of testing.
Testing is more difficult this cycle because:
* We have less developers working.
* We don't have the images we usually used to test on our main
hardware platform (XO*)
On 08/29/2013 06:01 AM, Thomas Gilliard wrote:
On 08/29/2013 05:35 AM, Thomas Gilliard wrote:
On 08/28/2013 11:03 AM, Gonzalo Odiard wrote:
I agree in the need of testing.
Testing is more difficult this cycle because:
* We have less developers working.
* We don't have the images we usually
Hello,
code freeze is due on 4 September. We have seven days left and I don't
think we are going to be ready, there are still 250 bugs to triage, 11
must fix already tagged, very little testing done judging from the number
of incoming bug reports and a not ready feeling when running master.
The
On Wed, Aug 28, 2013 at 1:25 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
Hello,
code freeze is due on 4 September. We have seven days left and I don't think
we are going to be ready, there are still 250 bugs to triage, 11 must fix
already tagged, very little testing done judging from the
On Wednesday, 28 August 2013, Gonzalo Odiard wrote:
From my part, I am building rpms for Australia, to use sugar 0.100 on a
F18 image.
We will do testing on that, but not in the web part, at least not now, due
to missing dependencies.
I wonder if anyone is planning a F19/F20 image for the
On Wed, Aug 28, 2013 at 6:05 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
On Wednesday, 28 August 2013, Gonzalo Odiard wrote:
From my part, I am building rpms for Australia, to use sugar 0.100 on a
F18 image.
We will do testing on that, but not in the web part, at least not now, due
to
29 matches
Mail list logo
