Hi Martey, GreGroup.
Personally I think that although the multi user change is significant
and effect the database structure and everything, it should not go into
a branch but into trunk.
the reason is that the sooner we deal with the integration issues the
better:
right now its just a matter of detecting the old database structure and
converting it to the new one (I suggest that on runtime the greg will
detect it, and tell the user the database need to be converted, and have
the user press a button to convert it).
if we wait with it, the differences will grow and grow, and it will
become increasingly expensive to merge the two branches, and eventually
no one will dare to do it because it will can possibly hurt too many users.
so, in a sentence:
during development the development of the mutliuser support, its okay to
have a branch, but this branch will only be used by the developers who
are working on it, when its ready for beta testing (including the
database conversion I mentioned above) the trunk tree should be tagged,
and the branch should be merged in, never to be used again.
My thoguhts.
Omry.
Martey Dodoo wrote:
> Hi everyone,
>
> Does anyone have any thoughts on creating a new branch in the
> subversion repository specifically for adding support for multiuser
> features to Gregarius? I would argue that support for multiple users
> is one of Gregarius' most requested features, and that it *must*
> appear in the next release - it is clear that it is important enough
> to have its own branch.
>
> Support for multiple users is likely to be a large undertaking that
> would significantly change Gregarius' database structure. I think that
> part of the reason that development on features essential to multiuser
> support has been slow is because of the conservatism of Gregarius'
> unstable codebase. While this is wonderful for end users, I think it
> slows down the pace of development. Creating a new branch for
> multiuser support would keep the historical stability of the trunk
> while ensuring that development of multiuser features will occur.
>