But this only works for releasing simple configurations that do not depend on other configurations.
This would work for rubric, for example, but not for other configurations we have in gtools.
then you have two options:
1) you rewrite your configurations to not need nested configurations. This is not recommendable in huge projects like Seaside, but things like GTools are easily (I did a quick check and your 3 configurations have in total 7 packages��� would not be a problem to have them without nesting projects and just using the packages). In fact, this is how Dale recommends using configurations (if I understood him right).
2) we enhance the tools to also allow the commit of nested packages.
I think both approaches needs to be done: you don���t need unnecessary complexity in your configurations and we need to add some nesting support to commit new version.
What is not admisible, IMO, is to do something that is wrong just because it looks easier in the short term (and I say ���in short term��� because what looks easier now will generate a lot of problems in the future).
cheers,
Esteban