3 Dec
2009
3 Dec
'09
3:23 p.m.
I copy the baseline from the default to a released
version because the default will change in the future, but version 4.0-beta.2 should not
be affected by those changes.
I see
but I thought that baseline should only change when you change package structure.
Cheers,
Doru
On 3 Dec 2009, at 14:55, Stéphane Ducasse wrote:
but
each time we commit we can generate a new version of the method
for me this is important that we can load the latest version but also that we know all
the packages and their versions.
We do that all the time in pharo.
The problem with your answer is the granularity of the release, if you release daily then
this is ok (may be every week would be ok).
But why can we release at each modification. We do that for pharo and this helps spotting
bug introdcution.
There is a no technical challenges and this would lower frsuatration.
Then I do not understand why you change the baseline if there is no new packages.
FOr me the baseline is the package/repository structure
Stef
On Dec 3, 2009, at 1:15 PM, Tudor Girba wrote:
--
www.tudorgirba.com
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Stef,
As I mentioned before, default represents the work in progress. It can happen that the
work in progress is the same as the previously released version, and that is why you will
see duplication.
Another possibility would be to reuse the previous configuration and just mention the
delta (of adding new packages), but I am not sure this would scale in the long run.
So, the current process is:
- work on default
- when we release, we copy the method in a new baselineXXX
- we create a hardcoded version in versionXXX
Cheers,
Doru
--
www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev