help needed with creating moose 5.0 configuration

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
37 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-2
Andrei wrote:

>I added a stable version for the following configurations:
>
>ConfigurationOfGlamourCore
>ConfigurationOfGlamour
>ConfigurationOfGTSpotter
>ConfigurationOfGTInspectorCore
>ConfigurationOfGTInspector
>ConfigurationOfGTPlaygroundCore
>ConfigurationOfGTPlayground
>ConfigurationOfRubric
>
>I'll continue to add stable versions for the remaining configurations that belong to GToolkit.


Thank you. In the version you declare as stable,
the dependencies should not be to numbered versions, so could you please replace e.g. in

ConfigurationOfGlamourCore>>version304: spec
        <version: '3.0.4' imports: #('3.0-baseline' )>

        spec for: #'common' do: [
                spec blessing: #'stable'.
                spec description: 'version 3.0.4'.
                spec author: 'AndreiChis'.
                spec timestamp: '12/09/2014 12:08'.
                spec
                        package: 'Glamour-Announcements' with: 'Glamour-Announcements-AndreiChis.8';
                        package: 'Glamour-Helpers' with: 'Glamour-Helpers-AndreiChis.36';
...
                        package: 'Glamour-Tests-Rubric' with: 'Glamour-Tests-Rubric-AndreiChis.14';
                        package: 'Glamour-Tests-Resources' with: 'Glamour-Tests-Resources-AndreiChis.3'.
               
                spec
                        project: 'Rubric' with: '1.2.5' ].


the reference to Rubric 1.2.5 to #stable (as long as Rubric only defines #stable and #development)

  Stephan






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Tudor Girba-2
Hi Stephan,

That would not work well now because of a conflict with merging in Pharo 4 which requires concrete version numbers for now. So, I suggest we leave GToolkit related configurations to be as they are and we will depend on the #stable of GToolkit. This should be fine given that we do not expect much changes in Pharo 3, and we will have to change the way we approach to overall process from Pharo 4 on.

Would that be Ok?

Cheers,
Doru



On Wed, Dec 10, 2014 at 10:02 AM, Stephan Eggermont <[hidden email]> wrote:
Andrei wrote:
>I added a stable version for the following configurations:
>
>ConfigurationOfGlamourCore
>ConfigurationOfGlamour
>ConfigurationOfGTSpotter
>ConfigurationOfGTInspectorCore
>ConfigurationOfGTInspector
>ConfigurationOfGTPlaygroundCore
>ConfigurationOfGTPlayground
>ConfigurationOfRubric
>
>I'll continue to add stable versions for the remaining configurations that belong to GToolkit.


Thank you. In the version you declare as stable,
the dependencies should not be to numbered versions, so could you please replace e.g. in

ConfigurationOfGlamourCore>>version304: spec
        <version: '3.0.4' imports: #('3.0-baseline' )>

        spec for: #'common' do: [
                spec blessing: #'stable'.
                spec description: 'version 3.0.4'.
                spec author: 'AndreiChis'.
                spec timestamp: '12/09/2014 12:08'.
                spec
                        package: 'Glamour-Announcements' with: 'Glamour-Announcements-AndreiChis.8';
                        package: 'Glamour-Helpers' with: 'Glamour-Helpers-AndreiChis.36';
...
                        package: 'Glamour-Tests-Rubric' with: 'Glamour-Tests-Rubric-AndreiChis.14';
                        package: 'Glamour-Tests-Resources' with: 'Glamour-Tests-Resources-AndreiChis.3'.

                spec
                        project: 'Rubric' with: '1.2.5' ].


the reference to Rubric 1.2.5 to #stable (as long as Rubric only defines #stable and #development)

  Stephan






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Stable is a newer version than development, let's see what happens...

Name: ConfigurationOfBitmapCharacterSet-StephanEggermont.9
Author: StephanEggermont
Time: 10 December 2014, 10:52:10.812126 am
UUID: 26927de9-f959-4410-bdc1-3d0933bb9985
Ancestors: ConfigurationOfBitmapCharacterSet-monty.8

Bugfix: development should not refer to an old version, replaced by baseline
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Doru wrote:
>That would not work well now because of a conflict with merging in Pharo 4
>which requires concrete version numbers for now.

Ahh, didn't know that. I assume that is something that will be resolved
soonish?

>So, I suggest we leave GToolkit related configurations to be as they are
>and we will depend on the #stable of GToolkit. This should be fine given
>that we do not expect much changes in Pharo 3, and we will have to
>change the way we approach to overall process from Pharo 4 on.
>
>Would that be Ok?

Let me think and check out loud.

There is lots of development in GToolkit, so it will definitely break
very fast after release, and the developers also have time and access
to patch configurations, so they can fix problems quickly. Not nice,
but no deal breaker.

ConfigurationOfGToolkit already has different baselines for Pharo 3 and 4

development: spec
        <symbolicVersion: #'development'>

        spec for: #'common' version: '0.6-baseline'.
        spec for: #'pharo3.x' version: '0.18-baseline'.
        spec for: #'pharo4.x' version: '0.17-baseline'

so an alternative could be to also have different versions of the other
GT configurations. The Pharo3 one using symbolic names, the 4 version not.

The GToolkit related configurations include Rubric, DeepTraverser and NewDebugger
so the change scope is limited.

I assume ConfigurationOfGlamour can use symbolic dependencies
to roassal2 and glamour core?

I'd prefer adding a symbolic version, but can live with the numbered version
in GToolkit related configurations

Stephan






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Andrei Chis
Hi,

We just need numbered versions for the configurations that are linked to pharo:

ConfigurationOfGlamourCore
ConfigurationOfGTInspectorCore
ConfigurationOfGTPlaygroundCore
ConfigurationOfRubric

I permanently update these configurations every time we integrate into pharo.
For the rest there is no problem to use #stable


Cheers,
Andrei


On Wed, Dec 10, 2014 at 8:40 AM, Stephan Eggermont <[hidden email]> wrote:
Doru wrote:
>That would not work well now because of a conflict with merging in Pharo 4
>which requires concrete version numbers for now.

Ahh, didn't know that. I assume that is something that will be resolved
soonish?

>So, I suggest we leave GToolkit related configurations to be as they are
>and we will depend on the #stable of GToolkit. This should be fine given
>that we do not expect much changes in Pharo 3, and we will have to
>change the way we approach to overall process from Pharo 4 on.
>
>Would that be Ok?

Let me think and check out loud.

There is lots of development in GToolkit, so it will definitely break
very fast after release, and the developers also have time and access
to patch configurations, so they can fix problems quickly. Not nice,
but no deal breaker.

ConfigurationOfGToolkit already has different baselines for Pharo 3 and 4

development: spec
        <symbolicVersion: #'development'>

        spec for: #'common' version: '0.6-baseline'.
        spec for: #'pharo3.x' version: '0.18-baseline'.
        spec for: #'pharo4.x' version: '0.17-baseline'

so an alternative could be to also have different versions of the other
GT configurations. The Pharo3 one using symbolic names, the 4 version not.

The GToolkit related configurations include Rubric, DeepTraverser and NewDebugger
so the change scope is limited.

I assume ConfigurationOfGlamour can use symbolic dependencies
to roassal2 and glamour core?

I'd prefer adding a symbolic version, but can live with the numbered version
in GToolkit related configurations

Stephan






_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Andrei wrote:
>We just need numbered versions for the configurations that are linked to pharo:
>
>ConfigurationOfGlamourCore
>ConfigurationOfGTInspectorCore
>ConfigurationOfGTPlaygroundCore
>ConfigurationOfRubric
>
>I permanently update these configurations every time we integrate into pharo.
>For the rest there is no problem to use #stable

Ok, let's do that.

Stephan
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Tudor Girba-2
Thanks.

Doru

On Wed, Dec 10, 2014 at 2:40 PM, Stephan Eggermont <[hidden email]> wrote:
Andrei wrote:
>We just need numbered versions for the configurations that are linked to pharo:
>
>ConfigurationOfGlamourCore
>ConfigurationOfGTInspectorCore
>ConfigurationOfGTPlaygroundCore
>ConfigurationOfRubric
>
>I permanently update these configurations every time we integrate into pharo.
>For the rest there is no problem to use #stable

Ok, let's do that.

Stephan
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
CollectionsExtensions is referred to in both ConfigurationOfMooseAlgos
and ConfigurationOfGlamour. Semantically it is part of MooseAlgos

The dependencies in baseline25 are not so nicely written.
I assume the test packages depend on the packages they test.
Moose-Algos-GraphObjectTraverser has no test package

Name: ConfigurationOfMooseAlgos-StephanEggermont.52
Author: StephanEggermont
Time: 10 December 2014, 3:32:57.214482 pm
UUID: 3dca6af0-2cf6-428b-be2b-ec8236bab163
Ancestors: ConfigurationOfMooseAlgos-TudorGirba.51

Created a stable version

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Name: ConfigurationOfMerlin-StephanEggermont.38
Author: StephanEggermont
Time: 10 December 2014, 3:45:22.666298 pm
UUID: d09ed99c-a364-4aca-8655-13f1fe3018c3
Ancestors: ConfigurationOfMerlin-StephaneDucasse.37

stable updated
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Name: ConfigurationOfNewDebugger-StephanEggermont.9
Author: StephanEggermont
Time: 10 December 2014, 3:53:40.486453 pm
UUID: 0c5dfd2f-606f-45ac-8618-1f05b3a5d2d3
Ancestors: ConfigurationOfNewDebugger-AndreiChis.8

Added new stable version Pharo3 and 4
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Name: ConfigurationOfPastell-StephanEggermont.12
Author: StephanEggermont
Time: 10 December 2014, 4:01:06.450525 pm
UUID: 7fb6a243-6514-4a6e-91ec-7930144c0e7d
Ancestors: ConfigurationOfPastell-DiegoLont.11

new stable version, depend on stable XMLParser

That's it for me for today.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Tudor Girba-2
What's left?

Doru

On Wed, Dec 10, 2014 at 4:02 PM, Stephan Eggermont <[hidden email]> wrote:
Name: ConfigurationOfPastell-StephanEggermont.12
Author: StephanEggermont
Time: 10 December 2014, 4:01:06.450525 pm
UUID: 7fb6a243-6514-4a6e-91ec-7930144c0e7d
Ancestors: ConfigurationOfPastell-DiegoLont.11

new stable version, depend on stable XMLParser

That's it for me for today.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Andrei Chis
I'm going now through the remaining configurations from GToolkit.

Andrei

On Wed, Dec 10, 2014 at 12:39 PM, Tudor Girba <[hidden email]> wrote:
What's left?

Doru

On Wed, Dec 10, 2014 at 4:02 PM, Stephan Eggermont <[hidden email]> wrote:
Name: ConfigurationOfPastell-StephanEggermont.12
Author: StephanEggermont
Time: 10 December 2014, 4:01:06.450525 pm
UUID: 7fb6a243-6514-4a6e-91ec-7930144c0e7d
Ancestors: ConfigurationOfPastell-DiegoLont.11

new stable version, depend on stable XMLParser

That's it for me for today.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Andrei Chis
- added a stable version to: GTSpotter, GTInspector, GTPlayground, Glamour
- updated stable in Roassal2
- added a stable version to GTDebugger but did not finish as the dependency to NewDebugger seems strange; I'll have a look
- added a stable version to GToolkit. Here there is a direct reference to the package 'Glamour-Morphic-Theme' even if glamour is loaded. Is that needed? Also another question: there are two packages that are in the baseline but are not curently loaded (GT-Coder, GT-Tools); do I need to also add them to a version or not?


That's all for today :)
I'll fix tomorrow the problem with GTDebugger <-> NewDebugger

Andrei

On Wed, Dec 10, 2014 at 1:36 PM, Andrei Chis <[hidden email]> wrote:
I'm going now through the remaining configurations from GToolkit.

Andrei

On Wed, Dec 10, 2014 at 12:39 PM, Tudor Girba <[hidden email]> wrote:
What's left?

Doru

On Wed, Dec 10, 2014 at 4:02 PM, Stephan Eggermont <[hidden email]> wrote:
Name: ConfigurationOfPastell-StephanEggermont.12
Author: StephanEggermont
Time: 10 December 2014, 4:01:06.450525 pm
UUID: 7fb6a243-6514-4a6e-91ec-7930144c0e7d
Ancestors: ConfigurationOfPastell-DiegoLont.11

new stable version, depend on stable XMLParser

That's it for me for today.


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Dory wrote:
>What's left?

- a few small ones
- next interesting ones are Glamour, PetitParser and Roassal2.
- adding a test version to C-O-Moose with the stable versions of all dependencies
- if everything works, make a snapshot so we know what exact versions were loaded...


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2

Name: ConfigurationOfPetitParser-StephanEggermont.57
Author: StephanEggermont
Time: 12 December 2014, 11:29:41.588663 am
UUID: 9cf8b80c-3e08-49ee-a014-4c6e815afaa3
Ancestors: ConfigurationOfPetitParser-usmanbhatti.56

Stable version for Moose 5

Name: ConfigurationOfPetitSQLParser-StephanEggermont.23
Author: StephanEggermont
Time: 12 December 2014, 11:35:05.659061 am
UUID: 981097a0-66e7-4933-91cb-bfca289c2862
Ancestors: ConfigurationOfPetitSQLParser-TudorGirba.22

New stable version for Moose 5
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: help needed with creating moose 5.0 configuration

Stephan Eggermont-3
In reply to this post by Tudor Girba-2
Name: ConfigurationOfFame-StephanEggermont.29
Author: StephanEggermont
Time: 12 December 2014, 1:44:19.682481 pm
UUID: a59ec3f1-2e02-4e1e-a35b-2b195f3f8f1c
Ancestors: ConfigurationOfFame-StephanEggermont.28

wrong version fix in place

Name: ConfigurationOfSmallDude-StephanEggermont.30
Author: StephanEggermont
Time: 12 December 2014, 1:52:50.120165 pm
UUID: a71f5053-b9c9-4024-8457-631db8e8cdf4
Ancestors: ConfigurationOfSmallDude-TudorGirba.29

Version for Moose 5.0

Name: ConfigurationOfPetitSQLParser-StephanEggermont.24
Author: StephanEggermont
Time: 12 December 2014, 1:59:02.954291 pm
UUID: 5150f87c-ee94-43cc-886d-d1933b341ab3
Ancestors: ConfigurationOfPetitSQLParser-StephanEggermont.23

Use the new version in #stable

Name: ConfigurationOfPetitSQLParser-StephanEggermont.25
Author: StephanEggermont
Time: 12 December 2014, 2:07:43.151571 pm
UUID: d631128c-fd0e-4ea6-a4b4-3f6d1ff7c784
Ancestors: ConfigurationOfPetitSQLParser-StephanEggermont.24

typo

I've added a first version of the release5.0 version, only containing
stable versions of the depending configurations. Loading that gives
an emergency debugger.


Gofer new
        smalltalkhubUser: 'Moose' project: 'Moose';
        configuration;
        load.
((Smalltalk at: #ConfigurationOfMoose) project version: #'release5.0') load
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12