Re: [Exist-development] New stable branch: 2.0.x

[Adam R. <ad...@ex...>]

Actually may I suggest that developers do not merge to 2.0x stable. If we
want a high quality release one person should manage this, I am happy to be
that person. Howvere I will only merge where commit messages are clear, so
developers must write clear tagged and descriptive messages. I would like
to see us move to git in the near future so that we could control this with
pull requests.
On Feb 15, 2012 11:43 AM, "Wolfgang Meier" <wol...@ex...> wrote:

> To all committers and users: to prepare for the final 2.0 release and
> to continue with active development, we have created a new stable
> branch in SVN, which will replace the 1.4.x branch:
> stable/eXist-2.0.x.
>
> Developers: starting with rev 15855, please decide which commits have
> to be ported to 2.0.x and merge them yourselves. It is difficult for
> us if we have to go through the commit list months later to find the
> changes which have to be merged. As a general guideline, changes
> should be ported to the stable branch if they: 1) fix a bug which
> affects many users and the impact of the bug fix on other areas of
> eXist is limited, 2) fix an issue or improve a feature in code you are
> maintaining and which is sufficiently separate from eXist core, e.g.
> in an extension, 3) documentation updates, web site fixes. If in
> doubt, please send a message to the development list.
>
> Wolfgang
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>