[Zope] Python products - Versions in Zope

[Edward Muller]

On Monday 11 June 2001 11:10, Andy wrote:
> We separate dev staging and production totally by having totally different
> Zopes, only putting new versions live once tested (in theory :).
>
> --
>   Andy McKay
>


Good, But how do you upgrade the old stable version of product A to the new 
stable version of product A? What needs to be done in Python to upgrade it 
properly? When (in what method) should this code be placed? What needs to be 
done to upgrade instances of the previous version? etc... etc...

> ----- Original Message -----
> From: "Max M" <maxmcorp@worldonline.dk>
> To: "Zope@Zope. Org" <zope@zope.org>
> Sent: Monday, June 11, 2001 2:47 PM
> Subject: [Zope] Python products - Versions in Zope
>
> > How do you guys manage versions in Python products on running sites?
> >
> > Do you have several versions of products running at the same time, or do
>
> you
>
> > build in some kind of upgrade path that upgrades instanciated objects?
> >
> > Just looking for clues.
> >
> > regards Max M
> >
> > Max M. W. Rasmussen,    Denmark.   New Media Director
> > private: maxmcorp@worldonline.dk work: maxm@normik.dk
> > -----------------------------------------------------
> > Shipping software is an unnatural act
> >
> >
> > _______________________________________________
> > Zope maillist  -  Zope@zope.org
> > http://lists.zope.org/mailman/listinfo/zope
> > **   No cross posts or HTML encoding!  **
> > (Related lists -
> >  http://lists.zope.org/mailman/listinfo/zope-announce
> >  http://lists.zope.org/mailman/listinfo/zope-dev )
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )

-- 
Edward Muller - edwardam@home.com - edwardam@handhelds.org
If ignorance is bliss, 'tis folly to be wise.