You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Patrick Hunt <ph...@apache.org> on 2010/01/15 23:59:49 UTC
Status on upcoming ZK 3.3.0 release
ZK 3.3.0 is currently slated for March 10th. You can see a JIRA level
overview here:
https://issues.apache.org/jira/browse/ZOOKEEPER/fixforversion/12313976
Mahadev and I did an initial triage of the 3.3.0 JIRAs today. There are
currently 77 open issues slated for inclusion in this release, vs 110
already addressed.
What does this mean for you? If there's a JIRA assigned to you or that
you created that's listed for 3.3.0 please review it. If you don't plan
on working on it for 3.3.0 reschedule it (3.4.0 or later), if you do
plan to work on it please do so (sooner == better). If you want to get
something into 3.3.0 that's not listed for 3.3.0 please submit a patch
asap. As the 3.3.0 deadline approaches I will continue triaging the
issues, in particular I will start pushing out non-blocker JIRAs that
are not actively being worked on.
Thank you,
Patrick
Re: Status on upcoming ZK 3.3.0 release
Posted by Patrick Hunt <ph...@apache.org>.
Looks like MOVED issue has been resolved (ZOOKEEPER-710). I'm planning
to publish a 3.3.0 release candidate tomorrow.
Patrick
Patrick Hunt wrote:
> Another update. 121 has been resolved, all of the remaining patches have
> been applied and non-blockers moved out of 3.3.0.
>
> A new issue has recently been identified (see SESSION MOVED thread on
> the user list). One user is reporting "session moved" errors in 3.2.2
> when there shouldn't be. No jira on this yet but the user is creating a
> JIRA to track. This is a blocker for 3.3.0 until we can triage and
> identify the underlying problem. This is the last remaining issue so
> we'll be focused on this over the next day or two, once addressed I'll
> cut RC 0 for 3.3.0.
>
> Patrick
>
> Patrick Hunt wrote:
>> The release candidate has been blocked by ZOOKEEPER-121. We're working
>> to address, it's been failing intermittently on hudson. Additionally
>> Hudson itself has been very unstable, Mahadev and I have been working
>> to address this as well but that's slowing us considerably. Once the
>> blockers are dealt with, which should be any time now if hudson
>> cooperates, I should be publishing a release candidate.
>>
>> Patrick
>>
>> Patrick Hunt wrote:
>>> I was planning to cut a release candidate today, however there are a
>>> few blockers outstanding for this release that we need to address
>>> before I can do so. We're in the final stretch though.
>>>
>>> There are a number of open issues still pending for 3.3.0, however
>>> most of these are non-blockers and I've talked with the assigned
>>> party about policy (as soon as the blockers are addressed I will push
>>> remaining non-blockers to 3.4.0 and cut a release candidate). Unless
>>> you feel strongly about an issue push it to 3.4.0 asap.
>>>
>>> Recent changes have caused intermittent test failures (blocker
>>> issues) on hudson. Hudson runs with clover so these are probably
>>> timing related (clover test builds run much more slowly). We are
>>> working to address these with highest priority. Additionally Hudson
>>> itself has been unstable of late which is impacting our ability to
>>> process patches. Over the next few days things will stabilize and
>>> we'll cut the release candidate for 3.3.0.
>>>
>>> I encourage people following this list to run the tests themselves
>>> (checkout trunk and type "ant test") and enter JIRAs for any issues
>>> you find. Better now than once the release candidate is cut. Better
>>> now than when you need to roll out the changes to your environment
>>> and find issues that will take a fix release to address.
>>>
>>> Regards,
>>>
>>> Patrick
>>>
>>>
>>> Patrick Hunt wrote:
>>>> March 10 is rapidly approaching. There aren't any blockers left, my
>>>> plan is to commit any reviewed "patch availables" and push any
>>>> remaining non-blockers into 3.4.0 on Weds as part of cutting the
>>>> 3.3.0 release candidate. If you have something that you want to get
>>>> into 3.3.0 you need to get the patch in now. Final warning. ;-)
>>>>
>>>> Patrick
>>>>
>>>> Patrick Hunt wrote:
>>>>> Just a reminder, 3.3.0 is coming up fast. I will re-triage the JIRA
>>>>> list sometime next week with an eye towards reducing the list of
>>>>> "fix for 3.3.0", pushing non-critical, non-resourced issues to the
>>>>> 3.4.0 release. So if you have something you want to get into 3.3.0
>>>>> that's a non-blocker please submit a patch asap.
>>>>>
>>>>> Patrick
>>>>>
>>>>> Patrick Hunt wrote:
>>>>>> ZK 3.3.0 is currently slated for March 10th. You can see a JIRA
>>>>>> level overview here:
>>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER/fixforversion/12313976
>>>>>>
>>>>>>
>>>>>> Mahadev and I did an initial triage of the 3.3.0 JIRAs today.
>>>>>> There are currently 77 open issues slated for inclusion in this
>>>>>> release, vs 110 already addressed.
>>>>>>
>>>>>> What does this mean for you? If there's a JIRA assigned to you or
>>>>>> that you created that's listed for 3.3.0 please review it. If you
>>>>>> don't plan on working on it for 3.3.0 reschedule it (3.4.0 or
>>>>>> later), if you do plan to work on it please do so (sooner ==
>>>>>> better). If you want to get something into 3.3.0 that's not listed
>>>>>> for 3.3.0 please submit a patch asap. As the 3.3.0 deadline
>>>>>> approaches I will continue triaging the issues, in particular I
>>>>>> will start pushing out non-blocker JIRAs that are not actively
>>>>>> being worked on.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Patrick
Re: Status on upcoming ZK 3.3.0 release
Posted by Patrick Hunt <ph...@apache.org>.
Another update. 121 has been resolved, all of the remaining patches have
been applied and non-blockers moved out of 3.3.0.
A new issue has recently been identified (see SESSION MOVED thread on
the user list). One user is reporting "session moved" errors in 3.2.2
when there shouldn't be. No jira on this yet but the user is creating a
JIRA to track. This is a blocker for 3.3.0 until we can triage and
identify the underlying problem. This is the last remaining issue so
we'll be focused on this over the next day or two, once addressed I'll
cut RC 0 for 3.3.0.
Patrick
Patrick Hunt wrote:
> The release candidate has been blocked by ZOOKEEPER-121. We're working
> to address, it's been failing intermittently on hudson. Additionally
> Hudson itself has been very unstable, Mahadev and I have been working to
> address this as well but that's slowing us considerably. Once the
> blockers are dealt with, which should be any time now if hudson
> cooperates, I should be publishing a release candidate.
>
> Patrick
>
> Patrick Hunt wrote:
>> I was planning to cut a release candidate today, however there are a
>> few blockers outstanding for this release that we need to address
>> before I can do so. We're in the final stretch though.
>>
>> There are a number of open issues still pending for 3.3.0, however
>> most of these are non-blockers and I've talked with the assigned party
>> about policy (as soon as the blockers are addressed I will push
>> remaining non-blockers to 3.4.0 and cut a release candidate). Unless
>> you feel strongly about an issue push it to 3.4.0 asap.
>>
>> Recent changes have caused intermittent test failures (blocker issues)
>> on hudson. Hudson runs with clover so these are probably timing
>> related (clover test builds run much more slowly). We are working to
>> address these with highest priority. Additionally Hudson itself has
>> been unstable of late which is impacting our ability to process
>> patches. Over the next few days things will stabilize and we'll cut
>> the release candidate for 3.3.0.
>>
>> I encourage people following this list to run the tests themselves
>> (checkout trunk and type "ant test") and enter JIRAs for any issues
>> you find. Better now than once the release candidate is cut. Better
>> now than when you need to roll out the changes to your environment and
>> find issues that will take a fix release to address.
>>
>> Regards,
>>
>> Patrick
>>
>>
>> Patrick Hunt wrote:
>>> March 10 is rapidly approaching. There aren't any blockers left, my
>>> plan is to commit any reviewed "patch availables" and push any
>>> remaining non-blockers into 3.4.0 on Weds as part of cutting the
>>> 3.3.0 release candidate. If you have something that you want to get
>>> into 3.3.0 you need to get the patch in now. Final warning. ;-)
>>>
>>> Patrick
>>>
>>> Patrick Hunt wrote:
>>>> Just a reminder, 3.3.0 is coming up fast. I will re-triage the JIRA
>>>> list sometime next week with an eye towards reducing the list of
>>>> "fix for 3.3.0", pushing non-critical, non-resourced issues to the
>>>> 3.4.0 release. So if you have something you want to get into 3.3.0
>>>> that's a non-blocker please submit a patch asap.
>>>>
>>>> Patrick
>>>>
>>>> Patrick Hunt wrote:
>>>>> ZK 3.3.0 is currently slated for March 10th. You can see a JIRA
>>>>> level overview here:
>>>>> https://issues.apache.org/jira/browse/ZOOKEEPER/fixforversion/12313976
>>>>>
>>>>> Mahadev and I did an initial triage of the 3.3.0 JIRAs today. There
>>>>> are currently 77 open issues slated for inclusion in this release,
>>>>> vs 110 already addressed.
>>>>>
>>>>> What does this mean for you? If there's a JIRA assigned to you or
>>>>> that you created that's listed for 3.3.0 please review it. If you
>>>>> don't plan on working on it for 3.3.0 reschedule it (3.4.0 or
>>>>> later), if you do plan to work on it please do so (sooner ==
>>>>> better). If you want to get something into 3.3.0 that's not listed
>>>>> for 3.3.0 please submit a patch asap. As the 3.3.0 deadline
>>>>> approaches I will continue triaging the issues, in particular I
>>>>> will start pushing out non-blocker JIRAs that are not actively
>>>>> being worked on.
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Patrick
Re: Status on upcoming ZK 3.3.0 release
Posted by Patrick Hunt <ph...@apache.org>.
The release candidate has been blocked by ZOOKEEPER-121. We're working
to address, it's been failing intermittently on hudson. Additionally
Hudson itself has been very unstable, Mahadev and I have been working to
address this as well but that's slowing us considerably. Once the
blockers are dealt with, which should be any time now if hudson
cooperates, I should be publishing a release candidate.
Patrick
Patrick Hunt wrote:
> I was planning to cut a release candidate today, however there are a few
> blockers outstanding for this release that we need to address before I
> can do so. We're in the final stretch though.
>
> There are a number of open issues still pending for 3.3.0, however most
> of these are non-blockers and I've talked with the assigned party about
> policy (as soon as the blockers are addressed I will push remaining
> non-blockers to 3.4.0 and cut a release candidate). Unless you feel
> strongly about an issue push it to 3.4.0 asap.
>
> Recent changes have caused intermittent test failures (blocker issues)
> on hudson. Hudson runs with clover so these are probably timing related
> (clover test builds run much more slowly). We are working to address
> these with highest priority. Additionally Hudson itself has been
> unstable of late which is impacting our ability to process patches. Over
> the next few days things will stabilize and we'll cut the release
> candidate for 3.3.0.
>
> I encourage people following this list to run the tests themselves
> (checkout trunk and type "ant test") and enter JIRAs for any issues you
> find. Better now than once the release candidate is cut. Better now than
> when you need to roll out the changes to your environment and find
> issues that will take a fix release to address.
>
> Regards,
>
> Patrick
>
>
> Patrick Hunt wrote:
>> March 10 is rapidly approaching. There aren't any blockers left, my
>> plan is to commit any reviewed "patch availables" and push any
>> remaining non-blockers into 3.4.0 on Weds as part of cutting the 3.3.0
>> release candidate. If you have something that you want to get into
>> 3.3.0 you need to get the patch in now. Final warning. ;-)
>>
>> Patrick
>>
>> Patrick Hunt wrote:
>>> Just a reminder, 3.3.0 is coming up fast. I will re-triage the JIRA
>>> list sometime next week with an eye towards reducing the list of
>>> "fix for 3.3.0", pushing non-critical, non-resourced issues to the
>>> 3.4.0 release. So if you have something you want to get into 3.3.0
>>> that's a non-blocker please submit a patch asap.
>>>
>>> Patrick
>>>
>>> Patrick Hunt wrote:
>>>> ZK 3.3.0 is currently slated for March 10th. You can see a JIRA
>>>> level overview here:
>>>> https://issues.apache.org/jira/browse/ZOOKEEPER/fixforversion/12313976
>>>>
>>>> Mahadev and I did an initial triage of the 3.3.0 JIRAs today. There
>>>> are currently 77 open issues slated for inclusion in this release,
>>>> vs 110 already addressed.
>>>>
>>>> What does this mean for you? If there's a JIRA assigned to you or
>>>> that you created that's listed for 3.3.0 please review it. If you
>>>> don't plan on working on it for 3.3.0 reschedule it (3.4.0 or
>>>> later), if you do plan to work on it please do so (sooner ==
>>>> better). If you want to get something into 3.3.0 that's not listed
>>>> for 3.3.0 please submit a patch asap. As the 3.3.0 deadline
>>>> approaches I will continue triaging the issues, in particular I will
>>>> start pushing out non-blocker JIRAs that are not actively being
>>>> worked on.
>>>>
>>>> Thank you,
>>>>
>>>> Patrick
Re: Status on upcoming ZK 3.3.0 release
Posted by Patrick Hunt <ph...@apache.org>.
I was planning to cut a release candidate today, however there are a few
blockers outstanding for this release that we need to address before I
can do so. We're in the final stretch though.
There are a number of open issues still pending for 3.3.0, however most
of these are non-blockers and I've talked with the assigned party about
policy (as soon as the blockers are addressed I will push remaining
non-blockers to 3.4.0 and cut a release candidate). Unless you feel
strongly about an issue push it to 3.4.0 asap.
Recent changes have caused intermittent test failures (blocker issues)
on hudson. Hudson runs with clover so these are probably timing related
(clover test builds run much more slowly). We are working to address
these with highest priority. Additionally Hudson itself has been
unstable of late which is impacting our ability to process patches. Over
the next few days things will stabilize and we'll cut the release
candidate for 3.3.0.
I encourage people following this list to run the tests themselves
(checkout trunk and type "ant test") and enter JIRAs for any issues you
find. Better now than once the release candidate is cut. Better now than
when you need to roll out the changes to your environment and find
issues that will take a fix release to address.
Regards,
Patrick
Patrick Hunt wrote:
> March 10 is rapidly approaching. There aren't any blockers left, my plan
> is to commit any reviewed "patch availables" and push any remaining
> non-blockers into 3.4.0 on Weds as part of cutting the 3.3.0 release
> candidate. If you have something that you want to get into 3.3.0 you
> need to get the patch in now. Final warning. ;-)
>
> Patrick
>
> Patrick Hunt wrote:
>> Just a reminder, 3.3.0 is coming up fast. I will re-triage the JIRA
>> list sometime next week with an eye towards reducing the list of "fix
>> for 3.3.0", pushing non-critical, non-resourced issues to the 3.4.0
>> release. So if you have something you want to get into 3.3.0 that's a
>> non-blocker please submit a patch asap.
>>
>> Patrick
>>
>> Patrick Hunt wrote:
>>> ZK 3.3.0 is currently slated for March 10th. You can see a JIRA level
>>> overview here:
>>> https://issues.apache.org/jira/browse/ZOOKEEPER/fixforversion/12313976
>>>
>>> Mahadev and I did an initial triage of the 3.3.0 JIRAs today. There
>>> are currently 77 open issues slated for inclusion in this release, vs
>>> 110 already addressed.
>>>
>>> What does this mean for you? If there's a JIRA assigned to you or
>>> that you created that's listed for 3.3.0 please review it. If you
>>> don't plan on working on it for 3.3.0 reschedule it (3.4.0 or later),
>>> if you do plan to work on it please do so (sooner == better). If you
>>> want to get something into 3.3.0 that's not listed for 3.3.0 please
>>> submit a patch asap. As the 3.3.0 deadline approaches I will continue
>>> triaging the issues, in particular I will start pushing out
>>> non-blocker JIRAs that are not actively being worked on.
>>>
>>> Thank you,
>>>
>>> Patrick
Re: Status on upcoming ZK 3.3.0 release
Posted by Patrick Hunt <ph...@apache.org>.
March 10 is rapidly approaching. There aren't any blockers left, my plan
is to commit any reviewed "patch availables" and push any remaining
non-blockers into 3.4.0 on Weds as part of cutting the 3.3.0 release
candidate. If you have something that you want to get into 3.3.0 you
need to get the patch in now. Final warning. ;-)
Patrick
Patrick Hunt wrote:
> Just a reminder, 3.3.0 is coming up fast. I will re-triage the JIRA list
> sometime next week with an eye towards reducing the list of "fix for
> 3.3.0", pushing non-critical, non-resourced issues to the 3.4.0 release.
> So if you have something you want to get into 3.3.0 that's a non-blocker
> please submit a patch asap.
>
> Patrick
>
> Patrick Hunt wrote:
>> ZK 3.3.0 is currently slated for March 10th. You can see a JIRA level
>> overview here:
>> https://issues.apache.org/jira/browse/ZOOKEEPER/fixforversion/12313976
>>
>> Mahadev and I did an initial triage of the 3.3.0 JIRAs today. There
>> are currently 77 open issues slated for inclusion in this release, vs
>> 110 already addressed.
>>
>> What does this mean for you? If there's a JIRA assigned to you or that
>> you created that's listed for 3.3.0 please review it. If you don't
>> plan on working on it for 3.3.0 reschedule it (3.4.0 or later), if you
>> do plan to work on it please do so (sooner == better). If you want to
>> get something into 3.3.0 that's not listed for 3.3.0 please submit a
>> patch asap. As the 3.3.0 deadline approaches I will continue triaging
>> the issues, in particular I will start pushing out non-blocker JIRAs
>> that are not actively being worked on.
>>
>> Thank you,
>>
>> Patrick
Re: Status on upcoming ZK 3.3.0 release
Posted by Patrick Hunt <ph...@apache.org>.
Just a reminder, 3.3.0 is coming up fast. I will re-triage the JIRA list
sometime next week with an eye towards reducing the list of "fix for
3.3.0", pushing non-critical, non-resourced issues to the 3.4.0 release.
So if you have something you want to get into 3.3.0 that's a non-blocker
please submit a patch asap.
Patrick
Patrick Hunt wrote:
> ZK 3.3.0 is currently slated for March 10th. You can see a JIRA level
> overview here:
> https://issues.apache.org/jira/browse/ZOOKEEPER/fixforversion/12313976
>
> Mahadev and I did an initial triage of the 3.3.0 JIRAs today. There are
> currently 77 open issues slated for inclusion in this release, vs 110
> already addressed.
>
> What does this mean for you? If there's a JIRA assigned to you or that
> you created that's listed for 3.3.0 please review it. If you don't plan
> on working on it for 3.3.0 reschedule it (3.4.0 or later), if you do
> plan to work on it please do so (sooner == better). If you want to get
> something into 3.3.0 that's not listed for 3.3.0 please submit a patch
> asap. As the 3.3.0 deadline approaches I will continue triaging the
> issues, in particular I will start pushing out non-blocker JIRAs that
> are not actively being worked on.
>
> Thank you,
>
> Patrick