Mailing List Archive: Zope: CMF

GenericSetup 1.5

Index | Next | Previous | View Threaded

tseaver at palladion

Dec 11, 2008, 9:18 AM

Post #1 of 15 (1444 views)
Permalink

GenericSetup 1.5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I would like to get a 1.5 release of GenericSetup out over the holidays.
Here is what I have on the roadmap:

- Clean up the sphinx docs for the package, incorporating / updating
Rob Miller's excellent tutorial on GS (Rob has already blessed the
notion).

- Make *much* clearer the idea that content export / import should
not be treated as part of any "normal" profile, including adding
some extra support for doing that task at the application level.

- Tidy up any deprecations when running under Python 2.5 (and maybe
even 2.6).

Anyone have other stuff they would like to see in the mix (and can help
land)?

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJQUtL+gerLs4ltQ4RAoDIAJ9HV0NtsTLj/HHxJRcmjeaRPuCI7ACfTQCF
9AF0Pk2jMOdmMTpvgb2ejME=
=u2g+
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

y.2008 at wcm-solutions

Dec 11, 2008, 1:44 PM

Post #2 of 15 (1378 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

Hi!

Tres Seaver wrote:
> I would like to get a 1.5 release of GenericSetup out over the holidays.
> Here is what I have on the roadmap:
>
> - Clean up the sphinx docs for the package, incorporating / updating
> Rob Miller's excellent tutorial on GS (Rob has already blessed the
> notion).

Great! But why didn't you remove handlers.txt and profiles.txt in
GenericSetup/doc? AFAICS they are now redundant and outdated.

> - Make *much* clearer the idea that content export / import should
> not be treated as part of any "normal" profile, including adding
> some extra support for doing that task at the application level.
>
> - Tidy up any deprecations when running under Python 2.5 (and maybe
> even 2.6).

+1

> Anyone have other stuff they would like to see in the mix (and can help
> land)?

I recently started using UpgradeSteps and would like to improve the
"Upgrades" tab. Especially I'd like to implement useful behavior for
steps that have source/destination versions *and* a checker specified.

Right now the versions are mostly ignored if a checker exist. I'd like
to evaluate the versions first and use the checker as an additional
restriction. Also, running a step with checker should not update the
current version of the profile.

These changes would allow to split upgrades between versions into
several task centric steps. That gives users more control over the
upgrade process, doing upgrades step by step or skipping specific steps.

If people agree that this doesn't require a proposal and discussion
first, I could try to implement this in time for your release.

Cheers,

Yuppie

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

tseaver at palladion

Dec 11, 2008, 1:57 PM

Post #3 of 15 (1374 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

yuppie wrote:
> Hi!
>
>
> Tres Seaver wrote:
>> I would like to get a 1.5 release of GenericSetup out over the holidays.
>> Here is what I have on the roadmap:
>>
>> - Clean up the sphinx docs for the package, incorporating / updating
>> Rob Miller's excellent tutorial on GS (Rob has already blessed the
>> notion).
>
> Great! But why didn't you remove handlers.txt and profiles.txt in
> GenericSetup/doc? AFAICS they are now redundant and outdated.

I certainly plan to review all the docs: ideally, we would have a
combination of explanatory, tutorial, and reference docs.

>> - Make *much* clearer the idea that content export / import should
>> not be treated as part of any "normal" profile, including adding
>> some extra support for doing that task at the application level.
>>
>> - Tidy up any deprecations when running under Python 2.5 (and maybe
>> even 2.6).
>
> +1
>
>> Anyone have other stuff they would like to see in the mix (and can help
>> land)?
>
> I recently started using UpgradeSteps and would like to improve the
> "Upgrades" tab. Especially I'd like to implement useful behavior for
> steps that have source/destination versions *and* a checker specified.
>
> Right now the versions are mostly ignored if a checker exist. I'd like
> to evaluate the versions first and use the checker as an additional
> restriction. Also, running a step with checker should not update the
> current version of the profile.
>
> These changes would allow to split upgrades between versions into
> several task centric steps. That gives users more control over the
> upgrade process, doing upgrades step by step or skipping specific steps.
>
> If people agree that this doesn't require a proposal and discussion
> first, I could try to implement this in time for your release.

Sounds OK to me: note that I have never yet used UpgradeSteps myself.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJQYyw+gerLs4ltQ4RAmdMAKCHDz3T9GEgmvH50D35ngzXuU5EngCfdjlO
F3weQ5zXtbOnJ8GLjRtCUn4=
=xUzm
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Dec 12, 2008, 1:40 AM

Post #4 of 15 (1379 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

Previously Tres Seaver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I would like to get a 1.5 release of GenericSetup out over the holidays.
> Here is what I have on the roadmap:
>
> - Clean up the sphinx docs for the package, incorporating / updating
> Rob Miller's excellent tutorial on GS (Rob has already blessed the
> notion).
>
> - Make *much* clearer the idea that content export / import should
> not be treated as part of any "normal" profile, including adding
> some extra support for doing that task at the application level.
>
> - Tidy up any deprecations when running under Python 2.5 (and maybe
> even 2.6).
>
> Anyone have other stuff they would like to see in the mix (and can help
> land)?

I want to extend the upgrade step logic a bit to allow you to call
single steps from other profiles. Should be a simple change.

Wichert.

--
Wichert Akkerman <wichert[at]wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

ra at burningman

Dec 12, 2008, 11:31 AM

Post #5 of 15 (1380 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

yuppie wrote:
> Hi!
>
>
> Tres Seaver wrote:
>> I would like to get a 1.5 release of GenericSetup out over the holidays.
>> Here is what I have on the roadmap:
>>
>> - Clean up the sphinx docs for the package, incorporating / updating
>> Rob Miller's excellent tutorial on GS (Rob has already blessed the
>> notion).
>
> Great! But why didn't you remove handlers.txt and profiles.txt in
> GenericSetup/doc? AFAICS they are now redundant and outdated.
>
>> - Make *much* clearer the idea that content export / import should
>> not be treated as part of any "normal" profile, including adding
>> some extra support for doing that task at the application level.
>>
>> - Tidy up any deprecations when running under Python 2.5 (and maybe
>> even 2.6).
>
> +1
>
>> Anyone have other stuff they would like to see in the mix (and can help
>> land)?
>
> I recently started using UpgradeSteps and would like to improve the
> "Upgrades" tab. Especially I'd like to implement useful behavior for
> steps that have source/destination versions *and* a checker specified.
>
> Right now the versions are mostly ignored if a checker exist. I'd like
> to evaluate the versions first and use the checker as an additional
> restriction. Also, running a step with checker should not update the
> current version of the profile.
>
> These changes would allow to split upgrades between versions into
> several task centric steps. That gives users more control over the
> upgrade process, doing upgrades step by step or skipping specific steps.
>
> If people agree that this doesn't require a proposal and discussion
> first, I could try to implement this in time for your release.

+1 from me, as long as it's possible to use checkers w/o any version.

the version updating stuff in particular can be improved. right now it's very
dumb and just assumes that you ran an update so the version should be bumped.
definitely needs more love.

-r

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

charlie at begeistert

Dec 13, 2008, 9:19 AM

Post #6 of 15 (1373 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

Am 11.12.2008 um 22:57 schrieb Tres Seaver:

> I certainly plan to review all the docs: ideally, we would have a
> combination of explanatory, tutorial, and reference docs.

I might be able to help here. I am planning to spend some time between
Christmas and New Year on my own tasks but would like to help improve
documentation as well.

Charlie
--
Charlie Clark
Helmholtzstr. 20
D�sseldorf
D- 40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

jens at dataflake

Dec 18, 2008, 8:30 AM

Post #7 of 15 (1349 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Dec 11, 2008, at 18:18 , Tres Seaver wrote:

> Anyone have other stuff they would like to see in the mix (and can
> help
> land)?

Having just implemented GS handlers for a PAS plugin and the
LDAPUserFolder I came across the fact that two separate handler types
are used "in the wild", the (older?) IFilesystemExporter/Importer and
the (newer?) BodyAdapterBase-derived handlers. There's one unfortunate
incompatibility: If someone has implemented a IFilesystemExporter-
based exporter that walks the content tree, such as the
PluggableAuthService exporter, it will only pick up other
IFilesystemExporter-based export adapters, but not BodyAdapterBase-
type exporters. I'd like to see that ability, unless there's a
specific reason why it isn't there.

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAklKepwACgkQRAx5nvEhZLKDQACgqEtv27nJC+sIXi8sIuCYivCs
AfEAoKIwQZpM6x4+uuMQMJyRCAjY4nZC
=tT2F
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

y.2008 at wcm-solutions

Dec 23, 2008, 1:03 PM

Post #8 of 15 (1306 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

yuppie wrote:
> Right now the versions are mostly ignored if a checker exist. I'd like
> to evaluate the versions first and use the checker as an additional
> restriction. Also, running a step with checker should not update the
> current version of the profile.
>
> These changes would allow to split upgrades between versions into
> several task centric steps. That gives users more control over the
> upgrade process, doing upgrades step by step or skipping specific steps.
>
> If people agree that this doesn't require a proposal and discussion
> first, I could try to implement this in time for your release.

This is now implemented. I hope I didn't break anything. There were no
tests and same behavior didn't look right.

CMFDefault now uses the new features.

Cheers, Yuppie

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Mar 5, 2009, 4:08 AM

Post #9 of 15 (1016 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

Previously Wichert Akkerman wrote:
> Previously Tres Seaver wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I would like to get a 1.5 release of GenericSetup out over the holidays.
> > Here is what I have on the roadmap:
> >
> > - Clean up the sphinx docs for the package, incorporating / updating
> > Rob Miller's excellent tutorial on GS (Rob has already blessed the
> > notion).
> >
> > - Make *much* clearer the idea that content export / import should
> > not be treated as part of any "normal" profile, including adding
> > some extra support for doing that task at the application level.
> >
> > - Tidy up any deprecations when running under Python 2.5 (and maybe
> > even 2.6).
> >
> > Anyone have other stuff they would like to see in the mix (and can help
> > land)?
>
> I want to extend the upgrade step logic a bit to allow you to call
> single steps from other profiles. Should be a simple change.

I have commited this. Once the BBB problems with Zope 2.10 are fixed I
have no objections (and would in fact be in favour) of an 1.5 release.

Wichert.

--
Wichert Akkerman <wichert[at]wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

tseaver at palladion

Mar 5, 2009, 5:26 AM

Post #10 of 15 (1013 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wichert Akkerman wrote:
> Previously Wichert Akkerman wrote:
>> Previously Tres Seaver wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> I would like to get a 1.5 release of GenericSetup out over the holidays.
>>> Here is what I have on the roadmap:
>>>
>>> - Clean up the sphinx docs for the package, incorporating / updating
>>> Rob Miller's excellent tutorial on GS (Rob has already blessed the
>>> notion).
>>>
>>> - Make *much* clearer the idea that content export / import should
>>> not be treated as part of any "normal" profile, including adding
>>> some extra support for doing that task at the application level.
>>>
>>> - Tidy up any deprecations when running under Python 2.5 (and maybe
>>> even 2.6).
>>>
>>> Anyone have other stuff they would like to see in the mix (and can help
>>> land)?
>> I want to extend the upgrade step logic a bit to allow you to call
>> single steps from other profiles. Should be a simple change.
>
> I have commited this. Once the BBB problems with Zope 2.10 are fixed I
> have no objections (and would in fact be in favour) of an 1.5 release.

Are there open bug reports on such problems? Also, we might not even
support running on Zope 2.10.x with this release, if it is too painful
to resolve.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJr9MF+gerLs4ltQ4RAn1YAKDEyjNVBYIauNOPGFXAmNXkW2zISgCfadMO
8JISC2q5vlIwnoGH6Al/Vfc=
=k7XM
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Mar 5, 2009, 5:29 AM

Post #11 of 15 (1013 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

Previously Tres Seaver wrote:
> Are there open bug reports on such problems? Also, we might not even
> support running on Zope 2.10.x with this release, if it is too painful
> to resolve.

I posted to this list earlier today. It is just a matter of changing a
few imports, so not painful at all.

Wichert.

--
Wichert Akkerman <wichert[at]wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Mar 5, 2009, 5:29 AM

Post #12 of 15 (1012 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

tseaver at palladion

Mar 5, 2009, 12:33 PM

Post #13 of 15 (1012 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wichert Akkerman wrote:
> Previously Tres Seaver wrote:
>> Are there open bug reports on such problems? Also, we might not even
>> support running on Zope 2.10.x with this release, if it is too painful
>> to resolve.
>
> I posted to this list earlier today. It is just a matter of changing a
> few imports, so not painful at all.

I'm a little puzzled: you expect to be able to upgrade to a new "major"
release of GenericSetup (1.4.x -> 1.5.0), but not to pick up a "minor"
update to Zope (2.10.x -> 2.10.latest)? Doesn't make much sense to me:
if stability matters that much, then don't figure on upgrading products
to new, possibly incompatible versions.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJsDcW+gerLs4ltQ4RAsTNAJ9hTXSYIu9F94z330knz9nnZ+VJCQCg3QzK
0jC9ZPsf7qXPTErdU4PrTc8=
=USxM
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Mar 5, 2009, 12:37 PM

Post #14 of 15 (1012 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

Previously Tres Seaver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Wichert Akkerman wrote:
> > Previously Tres Seaver wrote:
> >> Are there open bug reports on such problems? Also, we might not even
> >> support running on Zope 2.10.x with this release, if it is too painful
> >> to resolve.
> >
> > I posted to this list earlier today. It is just a matter of changing a
> > few imports, so not painful at all.
>
> I'm a little puzzled: you expect to be able to upgrade to a new "major"
> release of GenericSetup (1.4.x -> 1.5.0), but not to pick up a "minor"
> update to Zope (2.10.x -> 2.10.latest)? Doesn't make much sense to me:
> if stability matters that much, then don't figure on upgrading products
> to new, possibly incompatible versions.

There is no minor Zope 2.10 release which has these changes.

Wichert.

--
Wichert Akkerman <wichert[at]wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

wichert at wiggy

Mar 5, 2009, 12:37 PM

Post #15 of 15 (1013 views)
Permalink

Re: GenericSetup 1.5 [In reply to]

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com