4 Sep
2015
4 Sep
'15
11:42 a.m.
On Fri, Sep 4, 2015 at 11:25 AM, stephan <stephan(a)stack.nl> wrote:
On 04-09-15 10:50, Usman Bhatti wrote:
A new version only will not solve the problem. The fix also needs to be
committed somewhere and if I commit the fix it in the main branch (see
screenshot below), I need to merge all the the changes done for Moose 6.0
(and update other packages that these packages depend on) and hence break
my tools in Moose 5.1.
I do not see how it can solved without creating a branch.
Indeed, once the fix committed, a new version will be created and the
stable will be updated.
[image: Inline image 1]
Logically, we should create a 5.1 repo (project
in STHub) to keep things
separate and clean, even for a minor non-blocking bug like this. Looking at
separate branches of a repo inside Monticello looks a bit weird to me. Then
we'll probably have to upgrade the configuration of Glamour Core for Moose
5.1 to load the fix. If ok with you, I can take care of the two tasks.
regards.
No. We don't do branch repos. Don't start creating a mess.
When the git support with libgit is released we can change things,
now we just need a new version and a configuration with different
versions for pharo 4 and 5 for stable/named versions.
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
