You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Stuart McCulloch <mc...@gmail.com> on 2011/07/01 18:24:48 UTC

Should we produce both .zip and .tar.gz of the released project, or just .zip?

As Richard says below, historically Felix releases included both .zip and .tar.gz of the project (these are the main things we vote on)

But the latest Apache parent pom only produces a .zip of the project release by default - so recent releases have only included .zip

However we can choose to have both by adding:

    <properties>
        <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
    </properties>

To the Felix parent pom and deploying v2.1

WDYT?

--
Cheers, Stuart

Begin forwarded message:

> From: "Richard S. Hall" <he...@ungoverned.org>
> Date: 1 July 2011 17:13:20 GMT+01:00
> To: dev@felix.apache.org
> Subject: Re: [VOTE] Release Felix Bundle Repository version 1.6.6
> Reply-To: dev@felix.apache.org
> 
> On 7/1/11 12:10, Stuart McCulloch wrote:
>> On 1 Jul 2011, at 15:59, Richard S. Hall wrote:
>> 
>>> This is the same issue as the Event Admin (?) release, when switching to the new parent pom, we don't get a tar.gz project release, only a zip release. What did we decide here? Are we going to switch to only a zip release?
>> the default (in the parent Apache pom) is to only produce a zip release, but you can get both zip and tar by setting:
>> 
>>     <properties>
>>         <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
>>     </properties>
>> 
>> so we could always add this to the parent Felix pom (and deploy a new 2.1? release of that) if people want both
> 
> It doesn't matter to me, really, but we've always had both and now we only have one. So, it seems like we need to make a decision for consistency purposes.
> 
> -> richard
> 
>>> ->  richard
>>> 
>>> On 6/29/11 19:27, Stuart McCulloch wrote:
>>>> Hi folks,
>>>> 
>>>> We solved 4 issues in this release:
>>>> 
>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22bundlerepository-1.6.6%22
>>>> 
>>>> There are still several outstanding issues:
>>>> 
>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+component+%3D+%22Bundle+Repository+%28OBR%29%22+AND+status+%3D+Open
>>>> 
>>>> Staging repository:
>>>> 
>>>>    https://repository.apache.org/content/repositories/orgapachefelix-008/
>>>> 
>>>> You can use this UNIX script to download the release and verify the signatures:
>>>> 
>>>>    http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>> 
>>>> Usage:
>>>> 
>>>>    sh check_staged_release.sh 008 /tmp/felix-staging
>>>> 
>>>> Please vote to approve this release:
>>>> 
>>>> [ ] +1 Approve the release
>>>> [ ] -1 Veto the release (please provide specific comments)
>>>> 
>>>> This vote will be open for 72 hours.
>>>> 
>>>> --
>>>> Cheers, Stuart
>>>> 


Re: Should we produce both .zip and .tar.gz of the released project, or just .zip?

Posted by Carsten Ziegeler <cz...@apache.org>.
It would be great if you can do that - I fear I won't have time before
end of next week

Regards
Carsten

2011/7/1 Stuart McCulloch <mc...@gmail.com>:
> On 1 Jul 2011, at 17:35, Carsten Ziegeler wrote:
>
>> 2011/7/1 Stuart McCulloch <mc...@gmail.com>:
>>> As Richard says below, historically Felix releases included both .zip and .tar.gz of the project (these are the main things we vote on)
>>>
>>> But the latest Apache parent pom only produces a .zip of the project release by default - so recent releases have only included .zip
>>>
>>> However we can choose to have both by adding:
>>>
>>>    <properties>
>>>        <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
>>>    </properties>
>>>
>>> To the Felix parent pom and deploying v2.1
>>>
>>
>> Yes, we should do this - this was what we discussed after the event admin release suffering from the same problem.
>
> righto - are you planning to update/deploy the new parent pom or should I do that?
>
>> Carsten
>>
>>> WDYT?
>>>
>>> --
>>> Cheers, Stuart
>>>
>>> Begin forwarded message:
>>>
>>>> From: "Richard S. Hall" <he...@ungoverned.org>
>>>> Date: 1 July 2011 17:13:20 GMT+01:00
>>>> To: dev@felix.apache.org
>>>> Subject: Re: [VOTE] Release Felix Bundle Repository version 1.6.6
>>>> Reply-To: dev@felix.apache.org
>>>>
>>>> On 7/1/11 12:10, Stuart McCulloch wrote:
>>>>> On 1 Jul 2011, at 15:59, Richard S. Hall wrote:
>>>>>
>>>>>> This is the same issue as the Event Admin (?) release, when switching to the new parent pom, we don't get a tar.gz project release, only a zip release. What did we decide here? Are we going to switch to only a zip release?
>>>>> the default (in the parent Apache pom) is to only produce a zip release, but you can get both zip and tar by setting:
>>>>>
>>>>>     <properties>
>>>>>         <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
>>>>>     </properties>
>>>>>
>>>>> so we could always add this to the parent Felix pom (and deploy a new 2.1? release of that) if people want both
>>>>
>>>> It doesn't matter to me, really, but we've always had both and now we only have one. So, it seems like we need to make a decision for consistency purposes.
>>>>
>>>> -> richard
>>>>
>>>>>> ->  richard
>>>>>>
>>>>>> On 6/29/11 19:27, Stuart McCulloch wrote:
>>>>>>> Hi folks,
>>>>>>>
>>>>>>> We solved 4 issues in this release:
>>>>>>>
>>>>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22bundlerepository-1.6.6%22
>>>>>>>
>>>>>>> There are still several outstanding issues:
>>>>>>>
>>>>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+component+%3D+%22Bundle+Repository+%28OBR%29%22+AND+status+%3D+Open
>>>>>>>
>>>>>>> Staging repository:
>>>>>>>
>>>>>>>    https://repository.apache.org/content/repositories/orgapachefelix-008/
>>>>>>>
>>>>>>> You can use this UNIX script to download the release and verify the signatures:
>>>>>>>
>>>>>>>    http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>>>>>
>>>>>>> Usage:
>>>>>>>
>>>>>>>    sh check_staged_release.sh 008 /tmp/felix-staging
>>>>>>>
>>>>>>> Please vote to approve this release:
>>>>>>>
>>>>>>> [ ] +1 Approve the release
>>>>>>> [ ] -1 Veto the release (please provide specific comments)
>>>>>>>
>>>>>>> This vote will be open for 72 hours.
>>>>>>>
>>>>>>> --
>>>>>>> Cheers, Stuart
>>>>>>>
>>>
>>>
>>
>>
>>
>> --
>> Carsten Ziegeler
>> cziegeler@apache.org
>
>



-- 
Carsten Ziegeler
cziegeler@apache.org

Re: Should we produce both .zip and .tar.gz of the released project, or just .zip?

Posted by Stuart McCulloch <mc...@gmail.com>.
On 1 Jul 2011, at 17:35, Carsten Ziegeler wrote:

> 2011/7/1 Stuart McCulloch <mc...@gmail.com>:
>> As Richard says below, historically Felix releases included both .zip and .tar.gz of the project (these are the main things we vote on)
>> 
>> But the latest Apache parent pom only produces a .zip of the project release by default - so recent releases have only included .zip
>> 
>> However we can choose to have both by adding:
>> 
>>    <properties>
>>        <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
>>    </properties>
>> 
>> To the Felix parent pom and deploying v2.1
>> 
> 
> Yes, we should do this - this was what we discussed after the event admin release suffering from the same problem.

righto - are you planning to update/deploy the new parent pom or should I do that?

> Carsten
> 
>> WDYT?
>> 
>> --
>> Cheers, Stuart
>> 
>> Begin forwarded message:
>> 
>>> From: "Richard S. Hall" <he...@ungoverned.org>
>>> Date: 1 July 2011 17:13:20 GMT+01:00
>>> To: dev@felix.apache.org
>>> Subject: Re: [VOTE] Release Felix Bundle Repository version 1.6.6
>>> Reply-To: dev@felix.apache.org
>>> 
>>> On 7/1/11 12:10, Stuart McCulloch wrote:
>>>> On 1 Jul 2011, at 15:59, Richard S. Hall wrote:
>>>> 
>>>>> This is the same issue as the Event Admin (?) release, when switching to the new parent pom, we don't get a tar.gz project release, only a zip release. What did we decide here? Are we going to switch to only a zip release?
>>>> the default (in the parent Apache pom) is to only produce a zip release, but you can get both zip and tar by setting:
>>>> 
>>>>     <properties>
>>>>         <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
>>>>     </properties>
>>>> 
>>>> so we could always add this to the parent Felix pom (and deploy a new 2.1? release of that) if people want both
>>> 
>>> It doesn't matter to me, really, but we've always had both and now we only have one. So, it seems like we need to make a decision for consistency purposes.
>>> 
>>> -> richard
>>> 
>>>>> ->  richard
>>>>> 
>>>>> On 6/29/11 19:27, Stuart McCulloch wrote:
>>>>>> Hi folks,
>>>>>> 
>>>>>> We solved 4 issues in this release:
>>>>>> 
>>>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22bundlerepository-1.6.6%22
>>>>>> 
>>>>>> There are still several outstanding issues:
>>>>>> 
>>>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+component+%3D+%22Bundle+Repository+%28OBR%29%22+AND+status+%3D+Open
>>>>>> 
>>>>>> Staging repository:
>>>>>> 
>>>>>>    https://repository.apache.org/content/repositories/orgapachefelix-008/
>>>>>> 
>>>>>> You can use this UNIX script to download the release and verify the signatures:
>>>>>> 
>>>>>>    http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>>>> 
>>>>>> Usage:
>>>>>> 
>>>>>>    sh check_staged_release.sh 008 /tmp/felix-staging
>>>>>> 
>>>>>> Please vote to approve this release:
>>>>>> 
>>>>>> [ ] +1 Approve the release
>>>>>> [ ] -1 Veto the release (please provide specific comments)
>>>>>> 
>>>>>> This vote will be open for 72 hours.
>>>>>> 
>>>>>> --
>>>>>> Cheers, Stuart
>>>>>> 
>> 
>> 
> 
> 
> 
> -- 
> Carsten Ziegeler
> cziegeler@apache.org


Re: Should we produce both .zip and .tar.gz of the released project, or just .zip?

Posted by Carsten Ziegeler <cz...@apache.org>.
2011/7/1 Stuart McCulloch <mc...@gmail.com>:
> As Richard says below, historically Felix releases included both .zip and .tar.gz of the project (these are the main things we vote on)
>
> But the latest Apache parent pom only produces a .zip of the project release by default - so recent releases have only included .zip
>
> However we can choose to have both by adding:
>
>    <properties>
>        <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
>    </properties>
>
> To the Felix parent pom and deploying v2.1
>

Yes, we should do this - this was what we discussed after the event
admin release suffering from the same problem.

Carsten

> WDYT?
>
> --
> Cheers, Stuart
>
> Begin forwarded message:
>
>> From: "Richard S. Hall" <he...@ungoverned.org>
>> Date: 1 July 2011 17:13:20 GMT+01:00
>> To: dev@felix.apache.org
>> Subject: Re: [VOTE] Release Felix Bundle Repository version 1.6.6
>> Reply-To: dev@felix.apache.org
>>
>> On 7/1/11 12:10, Stuart McCulloch wrote:
>>> On 1 Jul 2011, at 15:59, Richard S. Hall wrote:
>>>
>>>> This is the same issue as the Event Admin (?) release, when switching to the new parent pom, we don't get a tar.gz project release, only a zip release. What did we decide here? Are we going to switch to only a zip release?
>>> the default (in the parent Apache pom) is to only produce a zip release, but you can get both zip and tar by setting:
>>>
>>>     <properties>
>>>         <sourceReleaseAssemblyDescriptor>source-release-zip-tar</sourceReleaseAssemblyDescriptor>
>>>     </properties>
>>>
>>> so we could always add this to the parent Felix pom (and deploy a new 2.1? release of that) if people want both
>>
>> It doesn't matter to me, really, but we've always had both and now we only have one. So, it seems like we need to make a decision for consistency purposes.
>>
>> -> richard
>>
>>>> ->  richard
>>>>
>>>> On 6/29/11 19:27, Stuart McCulloch wrote:
>>>>> Hi folks,
>>>>>
>>>>> We solved 4 issues in this release:
>>>>>
>>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+fixVersion+%3D+%22bundlerepository-1.6.6%22
>>>>>
>>>>> There are still several outstanding issues:
>>>>>
>>>>>    https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+FELIX+AND+component+%3D+%22Bundle+Repository+%28OBR%29%22+AND+status+%3D+Open
>>>>>
>>>>> Staging repository:
>>>>>
>>>>>    https://repository.apache.org/content/repositories/orgapachefelix-008/
>>>>>
>>>>> You can use this UNIX script to download the release and verify the signatures:
>>>>>
>>>>>    http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>>>>
>>>>> Usage:
>>>>>
>>>>>    sh check_staged_release.sh 008 /tmp/felix-staging
>>>>>
>>>>> Please vote to approve this release:
>>>>>
>>>>> [ ] +1 Approve the release
>>>>> [ ] -1 Veto the release (please provide specific comments)
>>>>>
>>>>> This vote will be open for 72 hours.
>>>>>
>>>>> --
>>>>> Cheers, Stuart
>>>>>
>
>



-- 
Carsten Ziegeler
cziegeler@apache.org