Code or development freeze

[#1]

i have seen a few posts recently by people who would know indicating that there is a freeze on code changes and/or development.
Given the problems being raised in various areas is there any indication as to when the resource with be put in to Development/QA to allow this to be lifted.

[#2]

Hi OldJim;
We aren't under freeze at the moment just under tight control following the launch of ADSL2+ which touched on a number of different systems.  Therefore change requests are being reviewed individually, however, this shouldn't have any impact on problem fixes we are still rolling these out as a priority.
Thanks,
Fletch

[#3]

Thanks.
So the problems with home phone accounts
http://community.plus.net/forum/index.php/topic,80886.msg660876.html#msg660876
and the bug fix here
http://community.plus.net/forum/index.php/topic,80314.msg660794.html#msg660794
will be addressed soon hopefully

[#4]

http://community.plus.net/forum/index.php/topic,80302.0.html
the service status link is still broken as well on the main plusnet help support page, one would think this is a very easy change even under this semi code freeze, but its been weeks now

[#5]

@OldJim:  HomePhone problems are the priority - we have a few fixes rolling on Wednesday afternoon, and then a further batch later in the week.
@ASBODOG: I'll bump this along tomorrow...

[#6]

Quote from: ASBO

http://community.plus.net/forum/index.php/topic,80302.0.html the service status link is still broken as well on the main plusnet help support page, one would think this is a very easy change even under this semi code freeze, but its been weeks now

I'm not convinced that was offically raised as a problem. I did mean to do this when it was first brought to my attention but I was distracted at the time for reasons that I can't now remember. I've now raised it as a problem just in case nobody else picked it up (ref: 59328).

[#7]

Quote from: Bob

I've now raised it as a problem just in case nobody else picked it up (ref: 59328).

As per Chris's post here, this has now been fixed.