A really important point (which so far hasn't been addressed) is how to
deal with breakages of affiliated packages. I see two ways:
1. If I make a change to some core package, it is my responsibility to
ensure that no affiliated package breaks.
2. It is the responsibility of the affiliated package to fix breakages.
I think both of the above have problems:
With 1, the author of the core package might not have access to the
affiliated package: how do you force your affiliated package to accept a
needed change? This is the current situation with Sage and SageNB.
With 2, breakages will need to fixed after the fact (after the change to
the core package has been merged already), leading to occasional
breakages for end users. This is the current situation with Sage
optional packages.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
