You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Christian Schneider <ch...@die-schneider.net> on 2013/06/20 14:24:15 UTC
Distributed OSGi release on next tuesday?
We currently have 3 open issues for D-OSGi 1.5.0.
https://issues.apache.org/jira/browse/DOSGI/fixforversion/12323560
I would like to do a release next tuesday.
What do you think?
Christian
Re: Distributed OSGi release on next tuesday?
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi,
On 20/06/13 14:35, A. Rothman wrote:
> Hi,
>
> I finished fixing all the major bugs I've come across in the past couple
> of months. Code review and some more testing by others would be greatly
> appreciated - I'm sure there's room for improvement, but that's hard to
> do without feedback.
>
> A few things remain on my todo list, none of them blockers (mostly
> cleanup):
>
> 1. https://issues.apache.org/jira/browse/DOSGI-108 - awaiting verdict
> (cschneider/dkulp?)
>
I -1 on reverting.
Thanks, Sergey
> 2. Upgrading dependencies (and specifically
> https://issues.apache.org/jira/browse/DOSGI-191) - what is the policy on
> this? When do all the dependencies get upgraded?
>
> 3. Refactoring to create utils module (still awaiting response to the
> mail from a few days ago)
>
> 4. Split zookeeper discovery into listening/publishing subpackages
>
> 5. Standardizing variable names to make the code more consistent and
> readable
>
> I can probably do them all in time, but would like to hear feedback if
> anyone is for/against them or has better ideas before I proceed.
>
> Finally, among the 34 unresolved issues, there seem to be a bunch
> related to distribution/deployment, possibly several are no longer
> relevant (e.g. single-bundle stuff). If anyone can sift through them and
> close the low hanging fruit (at least) that would be nice.
>
> Amichai
>
>
> On 06/20/2013 03:51 PM, Sergey Beryozkin wrote:
>> Hi Christian
>> On 20/06/13 13:24, Christian Schneider wrote:
>>> We currently have 3 open issues for D-OSGi 1.5.0.
>>> https://issues.apache.org/jira/browse/DOSGI/fixforversion/12323560
>>>
>>> I would like to do a release next tuesday.
>>> What do you think?
>>>
>> Can you do a sanity check with Felix please ?
>>
>> Also FYI, I'd actually not mind trying to get
>> https://issues.apache.org/jira/browse/DOSGI-182
>>
>> done before 1.5 is out unless it requires much more effort than I
>> anticipated
>>
>> Cheers, Sergey
>>
>>> Christian
>>>
>>
>>
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Re: Distributed OSGi release on next tuesday?
Posted by "A. Rothman" <am...@amichais.net>.
On 06/20/2013 05:58 PM, Christian Schneider wrote:
> On 20.06.2013 15:35, A. Rothman wrote:
>> Hi,
>>
>> I finished fixing all the major bugs I've come across in the past
>> couple of months. Code review and some more testing by others would
>> be greatly appreciated - I'm sure there's room for improvement, but
>> that's hard to do without feedback.
>>
>> A few things remain on my todo list, none of them blockers (mostly
>> cleanup):
>>
>> 1. https://issues.apache.org/jira/browse/DOSGI-108 - awaiting verdict
>> (cschneider/dkulp?)
> I commented in the issue. As a summary I would prefer keeping the
> comma separated config for now.
>>
>> 2. Upgrading dependencies (and specifically
>> https://issues.apache.org/jira/browse/DOSGI-191) - what is the policy
>> on this? When do all the dependencies get upgraded?
>>
> Basically the dependency upgrades should match the kind of version we
> release. For a bugfix release there should only be bugfix upgrades for
> a minor release bugfix or minor upgrades... So I propose we upgrade
> to 3.3.2. We can also upgrade to 3.4.0 but as the release is planned
> quite soon I prefer the smaller upgrade. If you want to upgrade
> dependencies create an issue for it and if it may have big impact it
> makes sense to discuss on the list.
>
> I created https://issues.apache.org/jira/browse/DOSGI-192 to track this.
>
>> 3. Refactoring to create utils module (still awaiting response to the
>> mail from a few days ago)
> I would prefer to wait with this till the next release.
No problem.
>>
>> 4. Split zookeeper discovery into listening/publishing subpackages
> Looks like a smaller change so I agree we can do this for 1.5.0. Can
> you create an issue and do the change if you have time?
Sure.
>>
>> 5. Standardizing variable names to make the code more consistent and
>> readable
> This sounds like a bigger change. At least it may affect a lot of
> code. Can you propose a new naming scheme on the list?
Yep, it'll affect tons of code, but change nothing :-)
I'll start a separate thread on this.
>>
>> I can probably do them all in time, but would like to hear feedback
>> if anyone is for/against them or has better ideas before I proceed.
>>
>> Finally, among the 34 unresolved issues, there seem to be a bunch
>> related to distribution/deployment, possibly several are no longer
>> relevant (e.g. single-bundle stuff). If anyone can sift through them
>> and close the low hanging fruit (at least) that would be nice.
> I regularly go through the issues and ask for feedback. I then close
> them if there is no feedback after some time. Of course anyone feel
> free to do the same.
Cool. I did a few, but as a noob I'm uncomfortable touching others just yet.
>
> Christian
>
Re: Distributed OSGi release on next tuesday?
Posted by "A. Rothman" <am...@amichais.net>.
On 06/20/2013 09:12 PM, A. Rothman wrote:
>
> On 06/20/2013 06:53 PM, Daniel Kulp wrote:
>> On Jun 20, 2013, at 10:58 AM, Christian Schneider
>> <ch...@die-schneider.net> wrote:
>>> On 20.06.2013 15:35, A. Rothman wrote:
>>>> Hi,
>>>>
>>>> I finished fixing all the major bugs I've come across in the past
>>>> couple of months. Code review and some more testing by others would
>>>> be greatly appreciated - I'm sure there's room for improvement, but
>>>> that's hard to do without feedback.
>>>>
>>>> A few things remain on my todo list, none of them blockers (mostly
>>>> cleanup):
>>>>
>>>> 1. https://issues.apache.org/jira/browse/DOSGI-108 - awaiting
>>>> verdict (cschneider/dkulp?)
>>> I commented in the issue. As a summary I would prefer keeping the
>>> comma separated config for now.
> In JIRA? I think your comment may have gone missing..
Oops... don't I feel silly :-)
But would love to hear your input as well as :-)
Re: Distributed OSGi release on next tuesday?
Posted by "A. Rothman" <am...@amichais.net>.
On 06/20/2013 06:53 PM, Daniel Kulp wrote:
> On Jun 20, 2013, at 10:58 AM, Christian Schneider <ch...@die-schneider.net> wrote:
>> On 20.06.2013 15:35, A. Rothman wrote:
>>> Hi,
>>>
>>> I finished fixing all the major bugs I've come across in the past couple of months. Code review and some more testing by others would be greatly appreciated - I'm sure there's room for improvement, but that's hard to do without feedback.
>>>
>>> A few things remain on my todo list, none of them blockers (mostly cleanup):
>>>
>>> 1. https://issues.apache.org/jira/browse/DOSGI-108 - awaiting verdict (cschneider/dkulp?)
>> I commented in the issue. As a summary I would prefer keeping the comma separated config for now.
In JIRA? I think your comment may have gone missing...
Re: Distributed OSGi release on next tuesday?
Posted by Daniel Kulp <dk...@apache.org>.
On Jun 20, 2013, at 10:58 AM, Christian Schneider <ch...@die-schneider.net> wrote:
> On 20.06.2013 15:35, A. Rothman wrote:
>> Hi,
>>
>> I finished fixing all the major bugs I've come across in the past couple of months. Code review and some more testing by others would be greatly appreciated - I'm sure there's room for improvement, but that's hard to do without feedback.
>>
>> A few things remain on my todo list, none of them blockers (mostly cleanup):
>>
>> 1. https://issues.apache.org/jira/browse/DOSGI-108 - awaiting verdict (cschneider/dkulp?)
> I commented in the issue. As a summary I would prefer keeping the comma separated config for now.
>>
>> 2. Upgrading dependencies (and specifically https://issues.apache.org/jira/browse/DOSGI-191) - what is the policy on this? When do all the dependencies get upgraded?
>>
> Basically the dependency upgrades should match the kind of version we release. For a bugfix release there should only be bugfix upgrades for a minor release bugfix or minor upgrades... So I propose we upgrade to 3.3.2. We can also upgrade to 3.4.0 but as the release is planned quite soon I prefer the smaller upgrade. If you want to upgrade dependencies create an issue for it and if it may have big impact it makes sense to discuss on the list.
>
> I created https://issues.apache.org/jira/browse/DOSGI-192 to track this.
I thought we are discussing a 1.5.0 release which would be a minor release, not a patch/bugfix release. In that case, a zookeeper version upgrade would be fine.
Dan
>> 3. Refactoring to create utils module (still awaiting response to the mail from a few days ago)
> I would prefer to wait with this till the next release.
>>
>> 4. Split zookeeper discovery into listening/publishing subpackages
> Looks like a smaller change so I agree we can do this for 1.5.0. Can you create an issue and do the change if you have time?
>>
>> 5. Standardizing variable names to make the code more consistent and readable
> This sounds like a bigger change. At least it may affect a lot of code. Can you propose a new naming scheme on the list?
>>
>> I can probably do them all in time, but would like to hear feedback if anyone is for/against them or has better ideas before I proceed.
>>
>> Finally, among the 34 unresolved issues, there seem to be a bunch related to distribution/deployment, possibly several are no longer relevant (e.g. single-bundle stuff). If anyone can sift through them and close the low hanging fruit (at least) that would be nice.
> I regularly go through the issues and ask for feedback. I then close them if there is no feedback after some time. Of course anyone feel free to do the same.
>
> Christian
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Distributed OSGi release on next tuesday?
Posted by Christian Schneider <ch...@die-schneider.net>.
On 20.06.2013 15:35, A. Rothman wrote:
> Hi,
>
> I finished fixing all the major bugs I've come across in the past
> couple of months. Code review and some more testing by others would be
> greatly appreciated - I'm sure there's room for improvement, but
> that's hard to do without feedback.
>
> A few things remain on my todo list, none of them blockers (mostly
> cleanup):
>
> 1. https://issues.apache.org/jira/browse/DOSGI-108 - awaiting verdict
> (cschneider/dkulp?)
I commented in the issue. As a summary I would prefer keeping the comma
separated config for now.
>
> 2. Upgrading dependencies (and specifically
> https://issues.apache.org/jira/browse/DOSGI-191) - what is the policy
> on this? When do all the dependencies get upgraded?
>
Basically the dependency upgrades should match the kind of version we
release. For a bugfix release there should only be bugfix upgrades for a
minor release bugfix or minor upgrades... So I propose we upgrade to
3.3.2. We can also upgrade to 3.4.0 but as the release is planned quite
soon I prefer the smaller upgrade. If you want to upgrade dependencies
create an issue for it and if it may have big impact it makes sense to
discuss on the list.
I created https://issues.apache.org/jira/browse/DOSGI-192 to track this.
> 3. Refactoring to create utils module (still awaiting response to the
> mail from a few days ago)
I would prefer to wait with this till the next release.
>
> 4. Split zookeeper discovery into listening/publishing subpackages
Looks like a smaller change so I agree we can do this for 1.5.0. Can you
create an issue and do the change if you have time?
>
> 5. Standardizing variable names to make the code more consistent and
> readable
This sounds like a bigger change. At least it may affect a lot of code.
Can you propose a new naming scheme on the list?
>
> I can probably do them all in time, but would like to hear feedback if
> anyone is for/against them or has better ideas before I proceed.
>
> Finally, among the 34 unresolved issues, there seem to be a bunch
> related to distribution/deployment, possibly several are no longer
> relevant (e.g. single-bundle stuff). If anyone can sift through them
> and close the low hanging fruit (at least) that would be nice.
I regularly go through the issues and ask for feedback. I then close
them if there is no feedback after some time. Of course anyone feel free
to do the same.
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: Distributed OSGi release on next tuesday?
Posted by "A. Rothman" <am...@amichais.net>.
Hi,
I finished fixing all the major bugs I've come across in the past couple
of months. Code review and some more testing by others would be greatly
appreciated - I'm sure there's room for improvement, but that's hard to
do without feedback.
A few things remain on my todo list, none of them blockers (mostly cleanup):
1. https://issues.apache.org/jira/browse/DOSGI-108 - awaiting verdict
(cschneider/dkulp?)
2. Upgrading dependencies (and specifically
https://issues.apache.org/jira/browse/DOSGI-191) - what is the policy on
this? When do all the dependencies get upgraded?
3. Refactoring to create utils module (still awaiting response to the
mail from a few days ago)
4. Split zookeeper discovery into listening/publishing subpackages
5. Standardizing variable names to make the code more consistent and
readable
I can probably do them all in time, but would like to hear feedback if
anyone is for/against them or has better ideas before I proceed.
Finally, among the 34 unresolved issues, there seem to be a bunch
related to distribution/deployment, possibly several are no longer
relevant (e.g. single-bundle stuff). If anyone can sift through them and
close the low hanging fruit (at least) that would be nice.
Amichai
On 06/20/2013 03:51 PM, Sergey Beryozkin wrote:
> Hi Christian
> On 20/06/13 13:24, Christian Schneider wrote:
>> We currently have 3 open issues for D-OSGi 1.5.0.
>> https://issues.apache.org/jira/browse/DOSGI/fixforversion/12323560
>>
>> I would like to do a release next tuesday.
>> What do you think?
>>
> Can you do a sanity check with Felix please ?
>
> Also FYI, I'd actually not mind trying to get
> https://issues.apache.org/jira/browse/DOSGI-182
>
> done before 1.5 is out unless it requires much more effort than I
> anticipated
>
> Cheers, Sergey
>
>> Christian
>>
>
>
Re: Distributed OSGi release on next tuesday?
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Sergey,
I will test with felix tomorrow.
I do not mind having some more issues fixed. I just moved the issue to the
next release as it is not ciritical for the release from my point of view.
Christian
2013/6/20 Sergey Beryozkin <sb...@gmail.com>
> Hi Christian
>
> On 20/06/13 13:24, Christian Schneider wrote:
>
>> We currently have 3 open issues for D-OSGi 1.5.0.
>> https://issues.apache.org/**jira/browse/DOSGI/**fixforversion/12323560<https://issues.apache.org/jira/browse/DOSGI/fixforversion/12323560>
>>
>> I would like to do a release next tuesday.
>> What do you think?
>>
>> Can you do a sanity check with Felix please ?
>
> Also FYI, I'd actually not mind trying to get
> https://issues.apache.org/**jira/browse/DOSGI-182<https://issues.apache.org/jira/browse/DOSGI-182>
>
> done before 1.5 is out unless it requires much more effort than I
> anticipated
>
> Cheers, Sergey
>
> Christian
>>
>>
>
> --
> Sergey Beryozkin
>
> Talend Community Coders
> http://coders.talend.com/
>
> Blog: http://sberyozkin.blogspot.com
>
Re: Distributed OSGi release on next tuesday?
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Christian
On 20/06/13 13:24, Christian Schneider wrote:
> We currently have 3 open issues for D-OSGi 1.5.0.
> https://issues.apache.org/jira/browse/DOSGI/fixforversion/12323560
>
> I would like to do a release next tuesday.
> What do you think?
>
Can you do a sanity check with Felix please ?
Also FYI, I'd actually not mind trying to get
https://issues.apache.org/jira/browse/DOSGI-182
done before 1.5 is out unless it requires much more effort than I
anticipated
Cheers, Sergey
> Christian
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com