Le 20 mai 2014 à 14:28, Ben Coman a écrit : > Christophe Demarey wrote: >> >> Thanks a lot for all your nice words. >> You were right, there are other contributors to Versionner: first author >> Alexandre Bergel, then Juan Pablo Sandoval but also a lot of feedbacks from >> users (a mention to Sean for that) essential for such a tool. >> >> Le 20 mai 2014 à 10:10, kilon alios a écrit : >> >> >>> can someone explain "save to development" ? >>> >> >> When you do structural changes* in your configuration, it is done "in >> memory". To keep theses changes, you need to save them in the configuration. >> It is always done in the development version (the only version you can edit >> is the development version) that is backed by a baseline. >> If you need to do structural changes, use "Save to development" to flush >> your changes. If you only need to generate a new version with packages >> numbers updated, then use the "release version" button. >> >> * structural change: basically a change made to a baseline: addition/removal >> of a package / project group, edition of requirements or includes directives. >> >> >> If it is not clear, don't hesitate to ask more explanation. >> >> Best regards, >> Christophe. > > So would "Save to baseline" mean the same as "Save to development"?
Kind of. The idea is to hide the baseline complexity from the user point of view. The user only see releases (numbered version) and the development version where changes are possible. 'Save to baseline' is not clear about the baseline that will be used to save. In fact, development points to the latest baseline and creates new one if needed (ex: baseline used by a release that you need to edit).
smime.p7s
Description: S/MIME cryptographic signature
