Re: [Chicken-users] repository branching

[Ivan Raikov]

  Am I the only one who finds this scheme (ha!) confusing?  Is it
possible to use some Subversion trick so that a commit to a top-level
egg directory automatically does copy/commit in the latest release
branch also?  This will really help absent-minded people like myself
to make sure that new egg releases are committed to the current
Chicken release branch.

   -Ivan


"felix winkelmann" <address@hidden> writes:

> Hello!
>
>
> We plan to create a "release 3" branch for all eggs in the svn
> repository in the next days. This means that (together with
> chicken 3.0.0, which will be released at the same time) there
> will be a branch in the egg repository for each major chicken
> version. All changes committed to the current egg directories
> that take place after the branching will have to be merged
> into the release branch copy.