Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Subject: Re: DOAP dropped from
 http://svn.apache.org/repos/asf/jmeter/site/doap_JMeter.rdf
To: dev@jmeter.apache.org
References: <CAOGo0VaC9aKWjJVGb9YbY_2kFVGNqG4a1K2pxc-hFPcLOtsLzQ@mail.gmail.com>
 <58348404.10109@apache.org>
 <CAOGo0Va+GwqkOgZOPriKwCMDVQK9uuNcE6H+kjGZxwuitYzNRQ@mail.gmail.com>
 <58353D51.1020406@apache.org>
 <CAOGo0VZVegM7eH2qiN9FoZrfkKQ+WdgD87n6zXO37H5Lv5jgLQ@mail.gmail.com>
 <5837E84F.6080201@apache.org>
 <CAOGo0VYxAUAjCYr6Cega18jpdXdnJqvstueapXtj5EkpBz0Nzg@mail.gmail.com>
 <5839DBF3.8030502@apache.org>
 <CAOGo0VbCOAJwC_o5n91AX3W-aq2KUStxgABjrtDo9W-EZ129SA@mail.gmail.com>
From: Milamber <milamber@apache.org>
Organization: Apache Software Fondation
Message-ID: <583AB18A.9080703@apache.org>
Date: Sun, 27 Nov 2016 10:12:26 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101
 Firefox/43.0 SeaMonkey/2.40
MIME-Version: 1.0
In-Reply-To: <CAOGo0VbCOAJwC_o5n91AX3W-aq2KUStxgABjrtDo9W-EZ129SA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Sun, 27 Nov 2016 10:12:32 -0000


On 26/11/2016 23:47, sebb wrote:
> On 26 November 2016 at 19:01, Milamber <milamber@apache.org> wrote:
>>
>> On 26/11/2016 11:04, sebb wrote:
>>> On 25 November 2016 at 07:29, Milamber <milamber@apache.org> wrote:
>>>>
>>>> On 23/11/2016 11:34, sebb wrote:
>>>>> On 23 November 2016 at 06:55, Milamber <milamber@apache.org> wrote:
>>>>>>
>>>>>> On 23/11/2016 00:41, sebb wrote:
>>>>>>> On 22 November 2016 at 17:44, Milamber <milamber@apache.org> wrote:
>>>>>>>> The svn log show:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> r1739835 | sebb | 2016-04-19 01:35:36 +0100 (mar., 19 avril 2016) | 1
>>>>>>>> line
>>>>>>>> Changed paths:
>>>>>>>>        A /jmeter/site/doap_JMeter.rdf (from
>>>>>>>> /jmeter/trunk/doap_JMeter.rdf:1739834)
>>>>>>>>        D /jmeter/trunk/doap_JMeter.rdf
>>>>>>>>
>>>>>>>> DOAP does not really belong in code
>>>>>>>>
>>>>>>>>
>>>>>>>> I can restore the doap file on trunk?
>>>>>>>>
>>>>>>> The DOAP file does not really belong in trunk, because it is not code,
>>>>>>> and does not belong in a release, and we don't want multiple copies in
>>>>>>> tags.
>>>>>>>
>>>>>>> I'm not sure why it was deleted from site when that was updated.
>>>>>>
>>>>>> I suppose that was the release process used this svnmucc script:
>>>>>>
>>>>>> ---
>>>>>> rm
>>>>>> https://svn.apache.org/repos/asf/jmeter/site
>>>>>>
>>>>>> cp
>>>>>> HEAD
>>>>>> https://svn.apache.org/repos/asf/jmeter/branches/docs-3.1/docs
>>>>>> https://svn.apache.org/repos/asf/jmeter/site
>>>>>> ---
>>>>>>
>>>>> Ah, I see.
>>>>> Not sure how easy it would be to keep just the doap.
>>>>> One would need to copy it from the appropriate version of site (before
>>>>> it got removed).
>>>>> Might be tricky to do reliably
>>>>>
>>>>> Maybe a simple solution would be to store the DOAP directly under
>>>>>
>>>>> https://svn.apache.org/repos/asf/jmeter/
>>>>>
>>>>> and fetch it from there.
>>>>>
>>>>> [To edit a file there means checking out non-recursively.]
>>>>>
>>>>> Or we could just create a separate folder:
>>>>>
>>>>> https://svn.apache.org/repos/asf/jmeter/doap
>>>>
>>>>
>>>> Seems the better solution for me. I do or you do?
>>>>
>>> Yes please.
>>
>> Done.
>>
>> What is the new step? copy the doap file into site directory (via svn or
>> manually?)
>>
> Manual svn copy now, but it ought to be possible to add it to the
> svnmucc script.

Done.

I've updated the release creation wiki page to reflect the changes about 
Doap file (if you can check the svnmucc script, thanks)
https://wiki.apache.org/jmeter/ReleaseCreation


>>>>> In each case, the latest DOAP could be copied as part of the svnmucc
>>>>> script.
>>>>>
>>>>>>
>>>>>>
>>>>>>>> On 21/11/2016 09:33, sebb wrote:
>>>>>>>>> I'm not sure why, but the doap has been dropped from
>>>>>>>>> http://svn.apache.org/repos/asf/jmeter/site/doap_JMeter.rdf again.
>>>>>>>>>
>>>>>>>>> It does not belong in the source tree, but does not necessarily have
>>>>>>>>> to be on the site so long as the project file is updated
>>>>>>>>> accordingly.
>>>>>>>>>