Just wondering whether there is something simple and effective to prevent loosing versions when more than 1 person is developing.
Before creating a new version, what about checking if there are new packages in the squeaksource rep? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
Gofer support a merge operation (which I haven't looked at) which could be done if a later version is found ... I think that addressing this problem is important ... Dale On Feb 24, 2011, at 10:53 AM, Alexandre Bergel wrote: > Just wondering whether there is something simple and effective to prevent loosing versions when more than 1 person is developing. > > Before creating a new version, what about checking if there are new packages in the squeaksource rep? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > |
Yes, but the merging can be done with Metacello. I think it works pretty well.
So, I will check before saving that no new version is available. This is what most source code management do actually. Alexandre On 24 Feb 2011, at 16:09, Dale Henrichs wrote: > > Gofer support a merge operation (which I haven't looked at) which could be done if a later version is found ... I think that addressing this problem is important ... > > Dale > > On Feb 24, 2011, at 10:53 AM, Alexandre Bergel wrote: > >> Just wondering whether there is something simple and effective to prevent loosing versions when more than 1 person is developing. >> >> Before creating a new version, what about checking if there are new packages in the squeaksource rep? >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
Alexandre,
I've added a check for new versions to the package save code in the toolbox, so you'll get a warning about possibly newer versions when Metacello 1.0beta.28.4 is released... Automatic merge will wait for another time. Dale On Feb 24, 2011, at 11:14 AM, Alexandre Bergel wrote: > Yes, but the merging can be done with Metacello. I think it works pretty well. > So, I will check before saving that no new version is available. This is what most source code management do actually. > > Alexandre > > > On 24 Feb 2011, at 16:09, Dale Henrichs wrote: > >> >> Gofer support a merge operation (which I haven't looked at) which could be done if a later version is found ... I think that addressing this problem is important ... >> >> Dale >> >> On Feb 24, 2011, at 10:53 AM, Alexandre Bergel wrote: >> >>> Just wondering whether there is something simple and effective to prevent loosing versions when more than 1 person is developing. >>> >>> Before creating a new version, what about checking if there are new packages in the squeaksource rep? >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > |
Free forum by Nabble | Edit this page |