I would also like to inlcude
https://issues.apache.org/jira/browse/SM-2068 if it comes by time as a
karaf patch; otherwise it could wait for 2.2.2.

Kind regards,
Andreas

On Sat, Apr 9, 2011 at 12:16 PM, Andreas Pieber <[email protected]> wrote:
> Ok, I've looked at all openend issues for 2.2.1 no and would say:
>
> I think those should be fixed. I try to fix what is possible till
> sunday but help is welcomed :)
>
> https://issues.apache.org/jira/browse/KARAF-534
> https://issues.apache.org/jira/browse/KARAF-559
> https://issues.apache.org/jira/browse/KARAF-557
> https://issues.apache.org/jira/browse/KARAF-562
>
> I think we should also include the following issues, but I'm waiting
> for answer there:
>
> https://issues.apache.org/jira/browse/KARAF-535
> https://issues.apache.org/jira/browse/KARAF-536
> https://issues.apache.org/jira/browse/KARAF-497
>
> All other issues could be moved to 2.2.2 IMHO
>
> Kind regards,
> Andreas
>
> On Thu, Mar 31, 2011 at 11:20 AM, Achim Nierbeck
> <[email protected]> wrote:
>> Hi,
>>
>> what I really would like to see in a 2.2.1 are the following issues:
>>
>>
>> - KARAF-518
>> - KARAF-534
>> and KARAF-547
>>
>> I'll take care of KARAF-529 this evening :)
>>
>> regards, Achim
>>
>> 2011/3/31 Jean-Baptiste Onofré <[email protected]>:
>>> Thanks Jamie for this.
>>>
>>> I'm gonna review some jira issues (especially one opened around Windows zip
>>> assembly).
>>>
>>> Regards
>>> JB
>>>
>>> On 03/30/2011 05:48 PM, Jamie G. wrote:
>>>>
>>>> Hi,
>>>>
>>>> I've recently added release tasks for Apache Karaf 2.2.1 and 2.1.5 to
>>>> Jira, and added 2.2.2 and 2.1.6 to version management.
>>>>
>>>> Over the next while if you could all review your issues reported to
>>>> 2.2.1 and 2.1.5 to see if they can make the proposed release
>>>> candidates, or be moved out to the next revision, would be great. We
>>>> do not have a specific time line set for attempting to release either
>>>> branch updates, we can discuss each in turn here or on separate
>>>> threads.
>>>>
>>>> Cheers,
>>>> Jamie
>>>
>>
>

Reply via email to