Hi
I ***REALLLY*** want that we are able to use moose for future code analysis so I want to be able to script and reload version of moose. So now if I modify something in moose how do I create a new version in ConfigurationOfMoose?
Stef
I copy here a set of instructions that I wrote one week ago:
For Metacello release, I have the following process: - copy the current default into a new method called baselineXXX - change the annotation to be 'VERSION.MINORVERSION-baseline' - select the Configuration class in OBSystemBrowser, and invoke "Spawn New Version"
Again, the tools support is not great. For example, "Spawn New Version" will not publish automatically the nested projects and it will not update the version number of those projects. So, at this point you will have to manually publish every nested project using the "Spawn New Version" and in the container project to update the version of the nested browser.
It is because of the many manual steps that it is not feasible at this point to release faster.
Cheers, Doru
On 3 Dec 2009, at 09:11, Stéphane Ducasse wrote:
Hi
I ***REALLLY*** want that we are able to use moose for future code analysis so I want to be able to script and reload version of moose. So now if I modify something in moose how do I create a new version in ConfigurationOfMoose?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
But each time alex publishes a new mondrian version he should update the configurationOfMondrian so for the nesting this would be ok for now.
Stef
On Dec 3, 2009, at 2:10 PM, Tudor Girba wrote:
I copy here a set of instructions that I wrote one week ago:
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke "Spawn New Version"
Again, the tools support is not great. For example, "Spawn New Version" will not publish automatically the nested projects and it will not update the version number of those projects. So, at this point you will have to manually publish every nested project using the "Spawn New Version" and in the container project to update the version of the nested browser.
It is because of the many manual steps that it is not feasible at this point to release faster.
Cheers, Doru
On 3 Dec 2009, at 09:11, Stéphane Ducasse wrote:
Hi
I ***REALLLY*** want that we are able to use moose for future code analysis so I want to be able to script and reload version of moose. So now if I modify something in moose how do I create a new version in ConfigurationOfMoose?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Ok, I will doo this
Alexandre
On 3 Dec 2009, at 11:02, Stéphane Ducasse wrote:
But each time alex publishes a new mondrian version he should update the configurationOfMondrian so for the nesting this would be ok for now.
Stef
On Dec 3, 2009, at 2:10 PM, Tudor Girba wrote:
I copy here a set of instructions that I wrote one week ago:
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke
"Spawn New Version"
Again, the tools support is not great. For example, "Spawn New Version" will not publish automatically the nested projects and it will not update the version number of those projects. So, at this point you will have to manually publish every nested project using the "Spawn New Version" and in the container project to update the version of the nested browser.
It is because of the many manual steps that it is not feasible at this point to release faster.
Cheers, Doru
On 3 Dec 2009, at 09:11, Stéphane Ducasse wrote:
Hi
I ***REALLLY*** want that we are able to use moose for future code analysis so I want to be able to script and reload version of moose. So now if I modify something in moose how do I create a new version in ConfigurationOfMoose?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
BTW the menus should not be capitalized since none of them are.
Stef
On Dec 3, 2009, at 2:10 PM, Tudor Girba wrote:
I copy here a set of instructions that I wrote one week ago:
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke "Spawn New Version"
Again, the tools support is not great. For example, "Spawn New Version" will not publish automatically the nested projects and it will not update the version number of those projects. So, at this point you will have to manually publish every nested project using the "Spawn New Version" and in the container project to update the version of the nested browser.
It is because of the many manual steps that it is not feasible at this point to release faster.
Cheers, Doru
On 3 Dec 2009, at 09:11, Stéphane Ducasse wrote:
Hi
I ***REALLLY*** want that we are able to use moose for future code analysis so I want to be able to script and reload version of moose. So now if I modify something in moose how do I create a new version in ConfigurationOfMoose?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
so do you know the internal of that stuff? what is left to be done to arrive to the point we can generate the methods?
BTW do you rename all the time the versions (version0012, version0013....) or reuse a number? because the different versions are versioning in the squeak source. So conceptually a little fix would not deserve a version change. In pharo we give systematic new name because of the update stream but here we do not need that.
Stef
I copy here a set of instructions that I wrote one week ago:
For Metacello release, I have the following process:
- copy the current default into a new method called baselineXXX
- change the annotation to be 'VERSION.MINORVERSION-baseline'
- select the Configuration class in OBSystemBrowser, and invoke "Spawn New Version"
Again, the tools support is not great. For example, "Spawn New Version" will not publish automatically the nested projects and it will not update the version number of those projects. So, at this point you will have to manually publish every nested project using the "Spawn New Version" and in the container project to update the version of the nested browser.
It is because of the many manual steps that it is not feasible at this point to release faster.
Cheers, Doru
On 3 Dec 2009, at 09:11, Stéphane Ducasse wrote:
Hi
I ***REALLLY*** want that we are able to use moose for future code analysis so I want to be able to script and reload version of moose. So now if I modify something in moose how do I create a new version in ConfigurationOfMoose?
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Stéphane Ducasse -
Tudor Girba