On Thu, Sep 15, 2016 at 06:41:10PM +0300, Alexander Ploumistos wrote: > On Thu, Sep 15, 2016 at 5:25 PM, Mary Clarke <mclarke@xxxxxxxxxx> wrote: > > > > The Modularity working group is looking to standardize terminology that users use to interact with functionality around modules. > > > Perhaps it would be better if someone provided some examples for the > functions described here - at least for the vaguest terms. Is there a > wiki page, mailing list thread, irc log or something to get a better > idea about them? > > Also, if > > > * Upgrade: updates the module to the latest release but the same version of the module > > what would upgrading/updating to a higher version of a module be called? This is exactly why I'm against the "version" keyword here :) Just because another "version"/"stream" provides newer upstream version of your software doesn't mean it's really an upgrade for you. It might, it might not be. You need to consider other module metadata too. Anyway, the verb we've been using for switching between module "versions"/"streams" so far is "rebase", AFAIC. I believe that's also open for discussion. P
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
