pharo 3.0 versionner and creating a development version
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work). Any hints? Norbert
hi Norbert. did you noticed that versionner is *already* in the image? cheers, Esteban On 11 Feb 2014, at 11:05, Norbert Hartl <norbert@hartl.name> wrote:
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work).
Any hints?
Norbert
Am 11.02.2014 um 10:07 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
hi Norbert.
did you noticed that versionner is *already* in the image?
Hahahaâ¦no :) Thatâs soo me! Ok, but it does not have much influence on my question. I still donât get how to just create a new development version or a new version at all. Norbert
cheers, Esteban
On 11 Feb 2014, at 11:05, Norbert Hartl <norbert@hartl.name> wrote:
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work).
Any hints?
Norbert
heh⦠answer that is Christophe's work :) On 11 Feb 2014, at 11:54, Norbert Hartl <norbert@hartl.name> wrote:
Am 11.02.2014 um 10:07 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
hi Norbert.
did you noticed that versionner is *already* in the image?
Hahahaâ¦no :) Thatâs soo me! Ok, but it does not have much influence on my question. I still donât get how to just create a new development version or a new version at all.
Norbert
cheers, Esteban
On 11 Feb 2014, at 11:05, Norbert Hartl <norbert@hartl.name> wrote:
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work).
Any hints?
Norbert
Hi Norbert, Le 11 févr. 2014 à 11:05, Norbert Hartl a écrit :
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work).
Any hints?
I wrote a small documentation on Versionner: http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner. With Versionner, a development version is always a baseline. If none is found, it will create one from the selected version. Why is it a baseline? because you don't want to update your configuration each time you publish new packages. When you are ready to release, Versionner creates: a numbered version with fixed packages revisions, and the next development version (a baseline). Tell me if you need more information. Regards, Christophe.
Am 11.02.2014 um 14:48 schrieb Christophe Demarey <Christophe.Demarey@inria.fr>:
Hi Norbert,
Le 11 févr. 2014 à 11:05, Norbert Hartl a écrit :
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work).
Any hints?
I wrote a small documentation on Versionner: http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner. With Versionner, a development version is always a baseline. If none is found, it will create one from the selected version. Why is it a baseline? because you don't want to update your configuration each time you publish new packages.
When you are ready to release, Versionner creates: a numbered version with fixed packages revisions, and the next development version (a baseline).
Tell me if you need more information.
Iâm not sure I understand. On the symbolic version front we have bleedingEdge that is loading a baseline without exact version information (it loads the newest packages). Then we have development versions that have specific package versions but are not released (not tagged stable). And we have releases that have a sense of to-be-published. Now we have only baselines/development and released versions? I liked to have the three levels because it matches all the requirements in my workflow. That is baseline = development, development = be used by other projects/collaborators before it is released, stable = ready to be released. Anyway if it is the case that there is only baseline and released version I do not understand why the versions are having the blessing development. How are those supposed to be tagged stable? At the moment I find it quite confusing how it is. I need maybe one or two more hints. Norbert
It's hard to think this one through without use cases⦠On the positive, it may be better to mark every numbered version as #'release' and then use semantic versioning to update if you run into trouble (i.e. release 2.0 and if you have to adjust the packages, 2.0.1). Because now that we have stable versions, there seem to be two competing systems - the tag of the numbered version and the symbolic version. In practice, it looks like a lot of numbered versions never get updated (i.e. versions that are symbolic #'stable' are not #'release' in the version spec) ----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-3-0-versionner-and-creating-a-development-versio... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Le 11 févr. 2014 à 16:15, Norbert Hartl a écrit :
Am 11.02.2014 um 14:48 schrieb Christophe Demarey <Christophe.Demarey@inria.fr>:
Hi Norbert,
Le 11 févr. 2014 à 11:05, Norbert Hartl a écrit :
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work).
Any hints?
I wrote a small documentation on Versionner: http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner. With Versionner, a development version is always a baseline. If none is found, it will create one from the selected version. Why is it a baseline? because you don't want to update your configuration each time you publish new packages.
When you are ready to release, Versionner creates: a numbered version with fixed packages revisions, and the next development version (a baseline).
Tell me if you need more information.
Iâm not sure I understand. On the symbolic version front we have bleedingEdge that is loading a baseline without exact version information (it loads the newest packages). Then we have development versions that have specific package versions but are not released (not tagged stable). And we have releases that have a sense of to-be-published. Now we have only baselines/development and released versions?
Yes. It is quite strange to have three levels of stability. A few users use that and we tried to find a simple process to manage configurations. As in many other languages, you develop, release, then develop again. In another way, I can also understand that you prefer another process or that you need an "extra" level.
I liked to have the three levels because it matches all the requirements in my workflow. That is baseline = development, development = be used by other projects/collaborators before it is released, stable = ready to be released.
your definition of the development version looks like a release-candidate. Why not publish (yes release ;) ) a RC version for this purpose?
Anyway if it is the case that there is only baseline and released version I do not understand why the versions are having the blessing development. How are those supposed to be tagged stable?
They shouldn't. I fixed that friday and it will be integrated soon.
At the moment I find it quite confusing how it is. I need maybe one or two more hints.
I understand. Versionner was thought to encourage people to follow a workflow that may be different of their current one. But there is still place to discussion, move and adding some other functionalities. Versionner needs feedback and will evolve from feedback. Thanks, Christophe.
Am 11.02.2014 um 16:43 schrieb Christophe Demarey <Christophe.Demarey@inria.fr>:
Le 11 févr. 2014 à 16:15, Norbert Hartl a écrit :
Am 11.02.2014 um 14:48 schrieb Christophe Demarey <Christophe.Demarey@inria.fr>:
Hi Norbert,
Le 11 févr. 2014 à 11:05, Norbert Hartl a écrit :
I try really hard to move to 3.0 at the moment. To me versionner became that important that this is a requirement for me to change the version. Iâm testing the bleeding edge version of versionner in 3.0 and this looks really cool. But somehow I cannot create a development version of my project. Whatever I try the only thing I can achieve is that versionner is producing a new baseline method. I used all of the three buttons at the top and did also examine all of the menus (those that work).
Any hints?
I wrote a small documentation on Versionner: http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner. With Versionner, a development version is always a baseline. If none is found, it will create one from the selected version. Why is it a baseline? because you don't want to update your configuration each time you publish new packages.
When you are ready to release, Versionner creates: a numbered version with fixed packages revisions, and the next development version (a baseline).
Tell me if you need more information.
Iâm not sure I understand. On the symbolic version front we have bleedingEdge that is loading a baseline without exact version information (it loads the newest packages). Then we have development versions that have specific package versions but are not released (not tagged stable). And we have releases that have a sense of to-be-published. Now we have only baselines/development and released versions?
Yes. It is quite strange to have three levels of stability. A few users use that and we tried to find a simple process to manage configurations. As in many other languages, you develop, release, then develop again. In another way, I can also understand that you prefer another process or that you need an "extra" level.
I liked to have the three levels because it matches all the requirements in my workflow. That is baseline = development, development = be used by other projects/collaborators before it is released, stable = ready to be released.
your definition of the development version looks like a release-candidate. Why not publish (yes release ;) ) a RC version for this purpose?
Anyway if it is the case that there is only baseline and released version I do not understand why the versions are having the blessing development. How are those supposed to be tagged stable?
They shouldn't. I fixed that friday and it will be integrated soon.
At the moment I find it quite confusing how it is. I need maybe one or two more hints.
I understand. Versionner was thought to encourage people to follow a workflow that may be different of their current one. But there is still place to discussion, move and adding some other functionalities.
Versionner needs feedback and will evolve from feedback.
Ok. What I wrote above is just what Iâm used to and what is my current way of working. But I must confess that this extra level of mine is probably not necessary. At least it complicates things and you can always argue that if you want three then the next one wants to have four levels. I need to think about a way how to build up my workflow on top of versionner not within. thanks for the great work! The new UI looks really great! Norbert
participants (4)
-
Christophe Demarey -
Esteban Lorenzano -
Norbert Hartl -
Sean P. DeNigris