[Seaside] Seaside 2.7a1 versions 169
Ron at USMedRec.com
Sun Feb 11 23:04:41 UTC 2007
Actually no. If you update from repositories, which my system does
automatically you will see that it changes back and forth from each version
of 169. This means that I update every time my system loads. It also means
that I have no idea which version is considered the current one. It's
better if we do not release two versions with the same number, unless we are
intending to permanently fork in which case I would recommend using a dot
version 169.01 or a new name for the fork. Since that is not the case could
we reconcile and release a new version?
> From: Philippe Marschall
> Sent: Sunday, February 11, 2007 12:01 PM
> 2007/2/11, Ron Teitelbaum <Ron at usmedrec.com>:
> > Hi all,
> > There are two version of Seaside2.7a1-nnn.169
> > The pmm and mb.
> > Could we reconcile and merge the two versions? Having two versions with
> > same version number wreaks havoc with Monticello Configurations.
> Not to my experience since MCC takes the author initials into account.
> Later versions even use the UUID so even having two different versions
> with exactly the same filename works fine.
More information about the Seaside