On Thu, Apr 29, 2010 at 11:30 AM, Torsten Bergmann <[email protected]> wrote:
> You mean "it should not be modified". Yes, sorry. I meant should NOT. > I know, but one should > also not delete *.mcz's from a repository ;) > > I know. But that's now your fault, neither mine. I was just pragmatic due to lack of time and it should > be no problem since it works for now. > > But just if it works, it doesn't mean it is correct. The idea is that when you release a version, it has to be reproducable. If it is not, then mark it as broken. Now, people may get confused, as depending when they loaded 1.0 they have different versions of OB. This different versions may include or solve different bugs...and that's difficult to track. If you agree, I can do what I offered: bless 1.0 as broken a create a 1.0.1 with the working versions. Let me know, Mariano > Bye > T. > > -------- Original-Nachricht -------- > > Torsten: I saw you changed version 1.0 of ConfigurationOfOmniBrowser to > > change the version of OmniBrowser package. > > However, I don't think this is a good thing. When a version is released, > > it > > should be "modifieded". For any reason. > > > > The good behavior, from my point of view, in this case is to put bless > the > > 1.0 version as broken and create a new version 1.0.1 with such change/fix > > > > What do you think ? > > > > Cheers > > > > Mariano > > -- > GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
