2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

I am just guessing: try to click on “development” item on the left side.

-> "Information: Nothing to save" Already tried :)

Cheers, Juraj

...

5. 2. 2015 v 17:13, Nicolai Hess <nicolaihess@web.de>:

Hello,

I fixed some issues for Athens and upload the changes to the repository. Now, I want to use Versionner to create a new configuration. What I tried:

Open a fresh image Open the Athens repository and load the new changesets -> There are some merge conflicts. Why? There shouldn't be any conflicts. How do you do this?

After merging the changes I open Versionner. I thought I have to make a new Release but the button "Release Version" is disabled. What did I miss?

nicolai

2015-02-05 23:06 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

I have downloaded the latest Pharo 4 and it looks like Esteban Lorenzano did the job. There is a new 2.7 version.

No, the version 2.7 is not new, I have some changes that came after that version.

Cheers, Juraj

5. 2. 2015 v 18:28, Nicolai Hess <nicolaihess@web.de>:

2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

...

I am just guessing: try to click on “development” item on the left side.

-> "Information: Nothing to save"

Already tried :)

...

Cheers, Juraj

...

5. 2. 2015 v 17:13, Nicolai Hess <nicolaihess@web.de>:

Hello,

I fixed some issues for Athens and upload the changes to the repository. Now, I want to use Versionner to create a new configuration. What I tried:

Open a fresh image Open the Athens repository and load the new changesets -> There are some merge conflicts. Why? There shouldn't be any conflicts. How do you do this?

After merging the changes I open Versionner. I thought I have to make a new Release but the button "Release Version" is disabled. What did I miss?

nicolai

2015-02-06 1:40 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

Well, then I cannot see packages that are not included in the version 2.7. Can you mention some? I will try to make a new version.

I want to include the latest versions of Athens-Cairo: Athens-Cairo-NicolaiHess.82 and Athens-Text: Athens-Text-NicolaiHess.16 The other packages hasn't change since version 2.7 nicolai

Juraj

5. 2. 2015 v 20:07, Nicolai Hess <nicolaihess@web.de>:

2015-02-05 23:06 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

...

I have downloaded the latest Pharo 4 and it looks like Esteban Lorenzano did the job. There is a new 2.7 version.

No, the version 2.7 is not new, I have some changes that came after that version.

...

Cheers, Juraj

5. 2. 2015 v 18:28, Nicolai Hess <nicolaihess@web.de>:

2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

...

I am just guessing: try to click on “development” item on the left side.

-> "Information: Nothing to save"

Already tried :)

...

Cheers, Juraj

...

5. 2. 2015 v 17:13, Nicolai Hess <nicolaihess@web.de>:

Hello,

I fixed some issues for Athens and upload the changes to the repository. Now, I want to use Versionner to create a new configuration. What I tried:

Open a fresh image Open the Athens repository and load the new changesets -> There are some merge conflicts. Why? There shouldn't be any conflicts. How do you do this?

After merging the changes I open Versionner. I thought I have to make a new Release but the button "Release Version" is disabled. What did I miss?

nicolai

2015-02-06 22:02 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

I have changed two methods of the configuration:

-=-=- stable: spec <symbolicVersion: #stable>

spec for: #'pharo2.x' version: '2.1'. "after some modification in NB made it incompatible with 3.0" spec for: #'pharo3.x' version: '2.3'. *spec for: #'pharo4.x' version: '2.7’. “<<== added, maybe instead of pharo4.x could be common"* -=-=- development: spec <symbolicVersion: #'development'>

spec for: #'common' version: '*2.3-baseline*’. “<<== it is likely not necessary" -=-=-

I have changed it, because I think there should be two lines in Versioner: one with development label, second with stable label. Then everything works. Let me know if it helps. Juraj

Thank you Juraj, that works .... better, but now, commiting the new configuration shows a bunch of "Critical Issues" Critical Warning missing recommend field... Critcal Warning The name of package x does not match file name x.7 Critical Warning No Version specified. .... Not that easy. Maybe, the ConfigurationOfAthens was only written and updated by hand, does not work with Versionner?

6. 2. 2015 v 17:28, Nicolai Hess <nicolaihess@web.de>:

2015-02-06 1:40 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

...

Well, then I cannot see packages that are not included in the version 2.7. Can you mention some? I will try to make a new version.

I want to include the latest versions of Athens-Cairo: Athens-Cairo-NicolaiHess.82 and Athens-Text: Athens-Text-NicolaiHess.16

The other packages hasn't change since version 2.7

nicolai

...

Juraj

5. 2. 2015 v 20:07, Nicolai Hess <nicolaihess@web.de>:

2015-02-05 23:06 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

...

I have downloaded the latest Pharo 4 and it looks like Esteban Lorenzano did the job. There is a new 2.7 version.

No, the version 2.7 is not new, I have some changes that came after that version.

...

Cheers, Juraj

5. 2. 2015 v 18:28, Nicolai Hess <nicolaihess@web.de>:

2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>:

...

I am just guessing: try to click on “development” item on the left side.

-> "Information: Nothing to save"

Already tried :)

...

Cheers, Juraj

...

5. 2. 2015 v 17:13, Nicolai Hess <nicolaihess@web.de>:

Hello,

I fixed some issues for Athens and upload the changes to the repository. Now, I want to use Versionner to create a new configuration. What I tried:

Open a fresh image Open the Athens repository and load the new changesets -> There are some merge conflicts. Why? There shouldn't be any conflicts. How do you do this?

After merging the changes I open Versionner. I thought I have to make a new Release but the button "Release Version" is disabled. What did I miss?

nicolai

Hi,

8. 2. 2015 v 8:26, Nicolai Hess <nicolaihess@web.de>:

2015-02-07 13:17 GMT+01:00 Nicolai Hess <nicolaihess@web.de <mailto:nicolaihess@web.de>>:

2015-02-06 22:02 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com <mailto:juraj.kubelka@gmail.com>>: I have changed two methods of the configuration:

-=-=- stable: spec <symbolicVersion: #stable>

spec for: #'pharo2.x' version: '2.1'. "after some modification in NB made it incompatible with 3.0" spec for: #'pharo3.x' version: '2.3'. spec for: #'pharo4.x' version: '2.7’. “<<== added, maybe instead of pharo4.x could be common" -=-=- development: spec <symbolicVersion: #'development'>

spec for: #'common' version: '2.3-baseline’. “<<== it is likely not necessary" -=-=-

I have changed it, because I think there should be two lines in Versioner: one with development label, second with stable label. Then everything works. Let me know if it helps. Juraj

Thank you Juraj, that works .... better, but now, commiting the new configuration shows a bunch of "Critical Issues" Critical Warning missing recommend field... Critcal Warning The name of package x does not match file name x.7 Critical Warning No Version specified. ....

Not that easy. Maybe, the ConfigurationOfAthens was only written and updated by hand, does not work with Versionner?

I think, for now I will try to change the Configuration by hand without versionner.

There three warnings revealed by: (MetacelloToolBox validateConfiguration: ConfigurationOfAthens). It is easy to fix, well I guess. The one is a misspelling, two are about missing #versionString: and I suppose there should be versionString: #’stable’. It is fixed in ConfigurationOfAthens-JurajKubelka.46.mcz. Then I have created by hand version 2.8. The “strange” think is that development do not point to the latest version. Is the 2.8 supposed to be stable or development version? ConfigurationOfAthens-JurajKubelka.46.mcz contains the 2.8 version as development version. Cheers, Juraj

Hello Nicolai, Le 5 févr. 2015 à 22:28, Nicolai Hess a écrit :

2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com>: I am just guessing: try to click on “development” item on the left side.

-> "Information: Nothing to save"

With Versionner, when you want to edit (i.e. add/remove a dependency, a group) you always edit the development version. When you do not need to update anything but just do a release to fix dependencies version numbers, you select the development version and then click on 'release'. The 'save' button is only useful if you did some changes related to dependencies/groups. That said, Versionner does not manage platform specific versions. It implies Versionner miss some information if the configuration has platform specific variants and Versionner may generates new incomplete versions. For configurations with platform specific information, I suggest to do not use Versionner. I will see if the support of platform specifics parts could be added to Versionner. Best regards, Christophe.

Christophe I also wonder if this is not the configuration we discussed with igor with the pattern/workflow he wanted (and made sense) but that was not supported by versionner. Stef Le 9/2/15 09:18, Christophe Demarey a écrit :

Hello Nicolai,

Le 5 févr. 2015 à 22:28, Nicolai Hess a écrit :

...

2015-02-05 21:56 GMT+01:00 Juraj Kubelka <juraj.kubelka@gmail.com <mailto:juraj.kubelka@gmail.com>>:

I am just guessing: try to click on “development” item on the left side.

-> "Information: Nothing to save"

With Versionner, when you want to edit (i.e. add/remove a dependency, a group) you always edit the development version. When you do not need to update anything but just do a release to fix dependencies version numbers, you select the development version and then click on 'release'. The 'save' button is only useful if you did some changes related to dependencies/groups. That said, Versionner does not manage platform specific versions. It implies Versionner miss some information if the configuration has platform specific variants and Versionner may generates new incomplete versions. For configurations with platform specific information, I suggest to do not use Versionner. I will see if the support of platform specifics parts could be added to Versionner.

Best regards, Christophe.