Mailing List Archive

0.23 Bug Squashing Party
Hi All,


We've decided this time around we'd like the development cycle of
0.23 to be far shorter than the time 0.22 took to come out of the
woodwork.

With a view to making this happen sooner rather than later we've
decided to borrow a tradition from Debian, and hold a bug squashing
party!

This will be held over the last weekend in January (30th & 31st).

We are also planning to do the feature freeze for 0.23 at around
the same time.

How can you help?
- Reproducing problems: sometimes we can't reproduce the problems
ourselves, and we need help from those users who do see the
problems, to help us to help them get issues fixed.
- Writing Patches: if you fancy trying your hand at coding, pick
one of the many open tickets and see if you can reproduce and
fix the problem.
- Testing! The more people who test, the more thoroughly we can
test mythtv!


Any comments?


Regards,
Stuart Auchterlonie

_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
> Hi All,
>
[...]
>
> How can you help?
> - Reproducing problems: sometimes we can't reproduce the problems
> ourselves, and we need help from those users who do see the
> problems, to help us to help them get issues fixed.
> - Writing Patches: if you fancy trying your hand at coding, pick
> one of the many open tickets and see if you can reproduce and
> fix the problem.
> - Testing! The more people who test, the more thoroughly we can
> test mythtv!
>
>
> Any comments?
>
Awesome, I'll help out as much as I can with patches and testing.
What about testing patches that already exist in trac?

Perhaps this email should go to the users list as well. There may be
some folk there that would be interested in helping out.

>
> Regards,
> Stuart Auchterlonie
>
Cheers,
Paul
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
On 13-1-2010 4:56, Paul Kendall wrote:
>> Any comments?
>>
> Awesome, I'll help out as much as I can with patches and testing.
> What about testing patches that already exist in trac?

I wonder on that as well as I have submitted some patches which also
have not been applied (previously for .22 and now for trunk), most of
them regarding windows compilation.

Groetjes,

Jonathan
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
'Twas brillig, and Jonathan Martens at 13/01/10 08:07 did gyre and gimble:
> On 13-1-2010 4:56, Paul Kendall wrote:
>>> Any comments?
>>>
>> Awesome, I'll help out as much as I can with patches and testing.
>> What about testing patches that already exist in trac?
>
> I wonder on that as well as I have submitted some patches which also
> have not been applied (previously for .22 and now for trunk), most of
> them regarding windows compilation.

Something that xorg uses is a "nominations" wiki page. It's slightly
different in that case as it asks for nominations of patches from git
master to the stable branch.

But in this case would a wiki page with trac ticket numbers and some
minor (i.e. short) comments on the patch in question help to organise
things? It could be a bit "manual" but it seems to work quite well for
xorg (although project sizes and release process is different so may not
apply here).

Col


--

Colin Guthrie
myth(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
On 13/01/2010 08:07, Jonathan Martens wrote:
> On 13-1-2010 4:56, Paul Kendall wrote:
>>> Any comments?
>>>
>> Awesome, I'll help out as much as I can with patches and testing.
>> What about testing patches that already exist in trac?
>
> I wonder on that as well as I have submitted some patches which also
> have not been applied (previously for .22 and now for trunk), most of
> them regarding windows compilation.
>

The plan of attack is as follows:

Firstly work our way through any tickets which have a milestone
of 0.22, 0.22.1 or 0.23. This will hopefully catch a lot of
of issues people have with 0.22 and quite a number of these already
have fairly simple patches to fix issues.

The second piece of work of triaging of tickets that currently have
an unknown milestone. These tickets need to be reviewed, problems
reproduced and patches produced as applicable. They also need assigning
to a milestone. Those which we can produce a fix for will be for 0.23,
others that are too invasive, require longer term testing or are
feature additions will get pushed to 0.24

Testing patches that are already in trac falls into both of these
streams of work, and most of them will actually been from the unknown
milestone list.

We will be co-ordinating all of this via IRC in #mythtv on freenode.


Stuart
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
> I wonder on that as well as I have submitted some patches which also have
> not been applied (previously for .22 and now for trunk), most of them
> regarding windows compilation.

Jonathan

I've been keeping an eye on all of the windows related patches in trac
with a view to getting most/all of them in to 0.23 - assuming I have
the time and someone else doesn't get there first. It would help if
there was some consensus on some of the compilation fixes - with the
amount of mail I'm getting at the moment, I just can't keep up and
don't have the time to work back through the discussion.

rgds

Mark
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
Op woensdag 13 januari 2010 00:27:02 schreef Stuart Auchterlonie:
> How can you help?
> - Reproducing problems: sometimes we can't reproduce the problems
> ourselves, and we need help from those users who do see the
> problems, to help us to help them get issues fixed.
> - Writing Patches: if you fancy trying your hand at coding, pick
> one of the many open tickets and see if you can reproduce and
> fix the problem.
> - Testing! The more people who test, the more thoroughly we can
> test mythtv!
>

Great idea.
I'll try to keep this weekend free.

What is the best way to see if someone is working on a specific ticket or
problem?

Joep
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
On 16/01/2010 15:32, joep admiraal wrote:
> Op woensdag 13 januari 2010 00:27:02 schreef Stuart Auchterlonie:
>> How can you help?
>> - Reproducing problems: sometimes we can't reproduce the problems
>> ourselves, and we need help from those users who do see the
>> problems, to help us to help them get issues fixed.
>> - Writing Patches: if you fancy trying your hand at coding, pick
>> one of the many open tickets and see if you can reproduce and
>> fix the problem.
>> - Testing! The more people who test, the more thoroughly we can
>> test mythtv!
>>
>
> Great idea.
> I'll try to keep this weekend free.
>
> What is the best way to see if someone is working on a specific ticket or
> problem?
>

All co-ordination will be done via IRC in #mythtv on freenode.


Stuart
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
* On Wed Jan 13, 2010 at 10:02:45AM +0000, Colin Guthrie wrote:
> Something that xorg uses is a "nominations" wiki page. It's slightly
> different in that case as it asks for nominations of patches from git
> master to the stable branch.
>
> But in this case would a wiki page with trac ticket numbers and some
> minor (i.e. short) comments on the patch in question help to organise
> things? It could be a bit "manual" but it seems to work quite well for
> xorg (although project sizes and release process is different so may not
> apply here).

I think that something as simple as an update to a 0.23 milestone bugfix
ticket saying that the applied patch corrects the issue will help us in
getting fixes into svn. The more people that test a patch, the more
confidence we have in that patch. Also, it helps keep the patches up to
date if they need to be tweaked because of changes in trunk since the patch
was uploaded.

--
Chris
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
On Friday 29 Jan 2010 14:21:41 Chris Pinkham wrote:
> * On Wed Jan 13, 2010 at 10:02:45AM +0000, Colin Guthrie wrote:
> > Something that xorg uses is a "nominations" wiki page. It's slightly
> > different in that case as it asks for nominations of patches from git
> > master to the stable branch.
> >
> > But in this case would a wiki page with trac ticket numbers and some
> > minor (i.e. short) comments on the patch in question help to organise
> > things? It could be a bit "manual" but it seems to work quite well for
> > xorg (although project sizes and release process is different so may not
> > apply here).
>
> I think that something as simple as an update to a 0.23 milestone bugfix
> ticket saying that the applied patch corrects the issue will help us in
> getting fixes into svn. The more people that test a patch, the more
> confidence we have in that patch.

Cue an avalanche of trac comments ... "Works for me too, please commit to
0.23". I've a feeling that the wiki might be more manageable, otherwise we'll
spend the entire weekend just trying to catch up with the email generated by
trac.

Reports of regressions caused by a patch are maybe more important. Testing of
patches is normally biased to those who stand to benefit from the fix, e.g. a
fix for Italian DVB will be written by, tested by and work for Italian users,
but no-one tests it with Spanish DVB and we only discover that it breaks
things for those users after the commit.

--
Stuart Morgan
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
* On Fri Jan 29, 2010 at 02:44:17PM +0000, Stuart Morgan wrote:
> Cue an avalanche of trac comments ... "Works for me too, please commit to
> 0.23". I've a feeling that the wiki might be more manageable, otherwise we'll
> spend the entire weekend just trying to catch up with the email generated by
> trac.

OK, maybe I should have added a phrase that I thought, saying "if there are
more than 3 comments saying it works then we'll purposefully _not_ put the patch
into trunk." :)

I agree on this. So it sounds like a 0.23-BSP wiki page where people can add
something like this:

Ticket #1024: Fixes issue of all green aliens appearing red

* This patch worked for me, but also had the side-effect of making Kirk's
shirt appear purple. User XYZ

* This patch works for me with Qt, but with OpenGL makes Kirk's hair yellow.
User ABC

Ticket #1052: Fixes tribbles stuttering movements

* This patch works, but now Kirk talks ... ev ... en ... slow ... er.
User XYZ

Ticket #1200: Phasers stuck on stun

* This patch works, tested against trunk r12385. I was able to successfully
switch back and forth between stun and nuke-em on my phaser via both the
OSD menu and the settings menu and the setting change was preserved
successfully each time. User ABC

--
Chris
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
On 29/01/2010 15:55, Chris Pinkham wrote:
> * On Fri Jan 29, 2010 at 02:44:17PM +0000, Stuart Morgan wrote:
>> Cue an avalanche of trac comments ... "Works for me too, please commit to
>> 0.23". I've a feeling that the wiki might be more manageable, otherwise we'll
>> spend the entire weekend just trying to catch up with the email generated by
>> trac.
>
> OK, maybe I should have added a phrase that I thought, saying "if there are
> more than 3 comments saying it works then we'll purposefully _not_ put the patch
> into trunk." :)
>
> I agree on this. So it sounds like a 0.23-BSP wiki page where people can add
> something like this:
>

IRC!!!!! That's what it was invented for!

We will be (as always) on freenode.
We've even got a channel specifically for the occasion #mythtv-bsp

Join us in there and we can co-ordinate there.


Stuart
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: 0.23 Bug Squashing Party [ In reply to ]
On Fri, Jan 29, 2010 at 10:20 AM, Stuart Auchterlonie
<stuarta@squashedfrog.net> wrote:
> On 29/01/2010 15:55, Chris Pinkham wrote:
>>
>> * On Fri Jan 29, 2010 at 02:44:17PM +0000, Stuart Morgan wrote:
>>>
>>> Cue an avalanche of trac comments ... "Works for me too, please commit to
>>> 0.23". I've a feeling that the wiki might be more manageable, otherwise
>>> we'll
>>> spend the entire weekend just trying to catch up with the email generated
>>> by
>>> trac.
>>
>> OK, maybe I should have added a phrase that I thought, saying "if there
>> are
>> more than 3 comments saying it works then we'll purposefully _not_ put the
>> patch
>> into trunk." :)
>>
>> I agree on this.  So it sounds like a 0.23-BSP wiki page where people can
>> add
>> something like this:
>>
>
> IRC!!!!! That's what it was invented for!
>
> We will be (as always) on freenode.
> We've even got a channel specifically for the occasion #mythtv-bsp
>
> Join us in there and we can co-ordinate there.

For those experienced Mythbuntu users interested in helping the MythTV
developers with the trunk (pre-0.23) bug squash:

0. Activate the 0.23 PPA within auto-builds [only available on 9.10 or
alpha 10.04]: http://www.mythbuntu.org/auto-builds

1. Attempt to reproduce bugs for which there are already tickets. If
it is still reproducible, they want to know (possibly with what steps
you used). If it isn't reproducible on similar hardware, they want to
know that too.

2. Verify patches (steps here: http://mythbuntu.org/wiki/recipes)

IMPORTANT NOTE: if you aren't comfortable with running possibly
unstable trunk software (and not comfortable with backing up your 0.22
database and restoring it later), it might be better to pass on this.

BTW, it would probably be a help to enable the -dbg packages so that
if you get a core dump, it will be of use:
http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages

Marc
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev