[Systers-dev] Mailman bug #590155 + #495331

[Robin Jeffries]

We would need test cases to add to the testing matrix.  Erica, have you
created test cases for this?

Do we want to add the fix that went to mailman directly to systers?  My
memory is that it doesn't impact behavior, so maybe it's better to have it
come down with the next mailman update.  Might be less confusion when we try
to upgrade.

For the footer message, it's possible that this bug got fixed and not
updated.  I haven't had time to track that down yet.  Will do this weekend
if events don't overwhelm me.

I was also thinking of contributing some testing this weekend, but it will
be sunday before I can get to it.

Jason, there were several people who said they could help with the testing.
 You might reach out to them individually and see what is keeping them from
contributing.  Maybe it's because the instructions aren't detailed enough
for a first timer, and you could help them through that.

Robin

On Fri, Jun 18, 2010 at 12:13 PM, Jason Cox <jasonwilburcox at gmail.com>wrote:

> Honestly, testing is not very far along, and integrating these bugs into
> the
> system would be fine. Jen, what do you think? Can the system be updated
> with
> these fixes and testing get started soon after that?
>
> Thanks,
>
> Jason
>
> On Fri, Jun 18, 2010 at 2:56 PM, Anne Gunn <ompeag at wyoming.com> wrote:
>
> > This particular change of Erica's is definitely ready for prime time
> since
> > it has already been accepted by Mailman.
> >
> > She has also proposed a patch to change a line of logging in order to
> help
> > diagnose a defect (missing footer message in syslog) that is happening on
> > the production system but no one has been able to help her reproduce in
> > test.  Details are up on launchpad for Bug Report 495331.
> >
> > I'd love to see both of these merged into the production code and rolled
> > out.  Can we do that?
> >
> > ag
> >
> > --- jenred at gmail.com wrote:
> >
> > From: Jennifer Redman <jenred at gmail.com>
> > To: erica <erica at wobblingcat.com>
> > Cc: systers-dev+mailman11 at systers.org<systers-dev%2Bmailman11 at systers.org>
> <systers-dev%2Bmailman11 at systers.org<systers-dev%252Bmailman11 at systers.org>
> >
> > Subject: Re: [Systers-dev] Mailman bug #590155
> > Date: Fri, 18 Jun 2010 11:33:31 -0700
> >
> > On Sun, Jun 6, 2010 at 8:49 AM, erica <erica at wobblingcat.com> wrote:
> >
> > > Thanks, Robin!
> > >
> > > I added a link on the Systers Development Resources page (
> > >
> >
> http://systers.org/systers-dev/doku.php/systers_open-source_development_projects
> ).
> >  This is the page itself:
> > >
> >
> http://systers.org/systers-dev/doku.php/how_to_submit_a_bug_to_the_mailman_project
> > .
> > >
> > >
> > Erica this is Wonderful!!  - Sorry for being a little late on the
> congrats
> > ;>.
> >
> > I'm thinking depending on where we are in the current test cycle -- maybe
> > we
> > should merge your code into dev and include in the next production
> rollout.
> >
> > Thoughts?
> >
> > Jen
> >
> >
> > To unsubscribe from this conversation, send email to <
> > systers-dev+mailman11+unsubscribe at systers.org<systers-dev%2Bmailman11%2Bunsubscribe at systers.org>
> <systers-dev%2Bmailman11%2Bunsubscribe at systers.org<systers-dev%252Bmailman11%252Bunsubscribe at systers.org>
> >>
> > or visit <
> > http://systers.org/mailman/options/systers-dev?override=125&preference=0
> >
> > To contribute to this conversation, use your mailer's reply-all or
> > reply-group command or send your message to
> > systers-dev+mailman11 at systers.org <systers-dev%2Bmailman11 at systers.org><
> systers-dev%2Bmailman11 at systers.org<systers-dev%252Bmailman11 at systers.org>
> >
> > To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> <systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>>
> > >
> > To unsubscribe entirely from systers-dev, send email to <
> > systers-dev-request at systers.org> with subject unsubscribe.
> >
> >
> >
> >
> > To unsubscribe from this conversation, send email to <
> > systers-dev+mailman11+unsubscribe at systers.org<systers-dev%2Bmailman11%2Bunsubscribe at systers.org>
> <systers-dev%2Bmailman11%2Bunsubscribe at systers.org<systers-dev%252Bmailman11%252Bunsubscribe at systers.org>
> >>
> > or visit <
> > http://systers.org/mailman/options/systers-dev?override=125&preference=0
> >
> > To contribute to this conversation, use your mailer's reply-all or
> > reply-group command or send your message to
> > systers-dev+mailman11 at systers.org <systers-dev%2Bmailman11 at systers.org><
> systers-dev%2Bmailman11 at systers.org<systers-dev%252Bmailman11 at systers.org>
> >
> > To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> <systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>>
> > >
> > To unsubscribe entirely from systers-dev, send email to <
> > systers-dev-request at systers.org> with subject unsubscribe.
> >
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+mailman11+unsubscribe at systers.org<systers-dev%2Bmailman11%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=125&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+mailman11 at systers.org <systers-dev%2Bmailman11 at systers.org>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> >
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>