Mailing-List: contact shindig-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: shindig-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
To: shindig-dev@incubator.apache.org
Path: not-for-mail
From: "Henning P. Schmiedehausen" <henning@schmiedehausen.org>
Newsgroups: hometree.shindig.dev
Subject: Re: Proposal To Branch for 1.0 Today
Date: Fri, 5 Dec 2008 19:30:39 +0000 (UTC)
Organization: INTERMETA - Gesellschaft fuer Mehrwertdienste mbH
Lines: 55
Message-ID: <ghbvgv$5ao$4@island.hometree.net>
References: <30C6B6A2-1D3D-48AA-A7E4-3D8C99CD54EC@tfd.co.uk>
 <c8689b660812022101w6995133amf63360d356606dd@mail.gmail.com>
 <gh6goh$v69$1@island.hometree.net>
 <c8689b660812031728u1c07f280w55ffffaf8a97fdd8@mail.gmail.com>
 <9fec51e20812032109y69ce8db2qb63b6d401f7c46ae@mail.gmail.com>
 <C474ADD5-252D-462A-83AF-B5F86B3D9D11@gmail.com>
 <818767740812040007u7c31fd27l469d53660165780@mail.gmail.com>
 <76EAF719-D769-4EF4-BDE8-61DB693A5042@tfd.co.uk>
 <gh97lg$2rq$1@island.hometree.net>
 <7D1F7E6D-A75F-4F71-B076-2AFEECA531E9@tfd.co.uk>
 <gha3li$dmo$1@island.hometree.net>
 <BA0F131A-42F3-4718-A9CF-E94E8164500F@tfd.co.uk>
Reply-To: henning@schmiedehausen.org
NNTP-Posting-Host: 192.168.2.3
NNTP-Posting-Date: Fri, 5 Dec 2008 19:30:39 +0000 (UTC)
User-Agent: nn/6.6.5

Ian Boston <ieb@tfd.co.uk> writes:

>On 5 Dec 2008, at 02:29, Henning P. Schmiedehausen wrote:

>> Ian Boston <ieb@tfd.co.uk> writes:
>>
>>> Why?
>>> To indicate the version that trunk is targeting.
>>
>> Because that assumes that this is the version the trunk is
>> targetting. If you find out halfway through working, that this should
>> be "2.0.0-SNAPSHOT", then you need to change it.

>my point exactly,
>no branch was done,
>and suddenly the direction of bleeding edge has changed
>anyone binding to the 1.1-SNAPSHOT still gets what they expected as  
>its still deployed or in their local repo.

Yes. They would expect that after doing "mvn clean install", their
code will pick up the latest, greatest changes. That's why they live
on the trunk.

What I do is (and I assume that most people work this way):

/work/myproject %                           (Hmmm. I need to update Shindig)
/work/myproject % pushd /work/shindig-trunk
/work/shindig-trunk % svn -q update
/work/shindig-trunk % mvn -q clean install  (Let's get coffee)
/work/shindig-trunk % popd
/work/myproject % mvn clean install         (That should do it and pick up all the changes)

and it does not. Because in your scenario, the POM version on the
trunk suddently changed. And worse, my code still builds, so I have no
way of *noticing* that these changed, unless I follow the commits.


>It Does depend how long afterwards you realize that all the commits  
>were going somewhere else, but I would hope that any project wouldn't  
>perform this sort of random walk towards a release ? IMHO I dont think  
>Shindig is doing that.

Hearing that from the person that just deleted the designated release
trunk and created a new one from a random point on the trunk makes me
shiver. 

    Ciao
        Henning

-- 
Henning P. Schmiedehausen - Palo Alto, California, U.S.A.
henning@schmiedehausen.org "We're Germans and we use Unix. 
henning@apache.org          That's a combination of two demographic groups
                            known to have no sense of humour whatsoever."
                               -- Hanno Mueller, de.comp.os.unix.programming