[Seaside-dev] Seaside 3.1 and beyond

[Philippe Marschall]

On Sun, Feb 9, 2014 at 4:11 PM, Johan Brichau <johan at inceptive.be> wrote:
> Hi Philippe,
>
> The question now becomes: how to manage a 3.1.x and 3.2 version in the repository?
>
> My proposal would be to use a branch on github for developing 3.2.
>
> We have the current 3.1.x packages on github already [1]. The idea is that the master branch always has the current Seaside production version (now coming from the Smalltalkhub repo). There already is a branch for the gemstone3.1 port and my proposal to you is to use a branch for Seaside 3.2 as well. We have automated tests using Travis CI [2]. It would also mean that other people sending in patches for Seaside would use a fork & pull-request. imho, a very convenient way to collaborate and avoid unwanted changes to the repository.
>
> What do you think?

Will you be at ESUG this year? I have to confess I don't have
experience in working with FileTree.

Cheers
Philippe