[Systers-dev] Testing Request for Bug 583379

[Jason Cox]

Kathy,

Ok, that is how I was thinking it works.

Thanks!

Jason

On Mon, Jun 7, 2010 at 3:48 PM, Kathy Richardson <kjr at casaveracruz.com>wrote:

>
>
> Jason,
>
> I'm answering this because I want to test my understanding, and hope others
> will correct me if I am wrong.
>
> Robin said I was wrong about any old code running.   I now believe that
> this is the deal:
>  MM stopped
>  Apache stopped
>
>  The new code was installed ( python files over writing existing python
> files)
>
>  MM started
>  Apache started
>
> This means that all/any data or messages that existed before the upgrade
> are still there.
> The new code needs to run on the exact same data.  If not then a conversion
> step needs to take place after stopping the services and before restarting
> then.  Of course new code could be smart enough to handle a complicate
> upgrade in functionality seamlessly.
>
> Kathy
> On Jun 7, 2010, at 10:45 AM, Jason Cox <jasonwilburcox at gmail.com> wrote:
>
> Robin,
>
> On Fri, Jun 4, 2010 at 7:28 PM, Robin Jeffries <robin at jeffries.org> wrote:
>
> Jason and company need to create a list for this testing cycle (it needs to
> be created with the code that we are testing) and I need to figure out how
> to create a user with
>
>
> When a list is created, does it use the code from the time of creation
> forever? Or, does updating the code update how the list works as well?
>
> Thanks,
>
> Jason
>
>
> mixed case addresses.  The easiest way to deal with the latter is that I
> will take on testing the test for the bug this is supposed to fix (SBT1 --
> Jason has already dibbed SBT2), as I can't get to creating this user till
> tomorrow.
>
> Jason, can you let us all know when you have the list created?  (Or whoever
> you delegate this to creates it)
>
> Robin
>
> On Fri, Jun 4, 2010 at 3:04 PM, Jennifer Redman <jenred at gmail.com> wrote:
>
> Ok I've merged Kanika Vats changes into systers-dev/systers/development
> and
> pulled the changes to abiwt.org.
>
> Restarted Mailman.  System should now be ready for testing.
>
> Let me know if you have any problems.
>
> Jen
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>
> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
> >>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=121&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 at systers.org> <
> systers-dev%2Btesting7 at systers.org <systers-dev%252Btesting7 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+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=121&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 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.
>
>
>