devohoneybee | this was the response back to genderfail

hi [name],

thank you for your feedback.
However, the code update that you refer to is not live and did not have any chance to go live. That was a beta release, we always push code to beta to see if everything works correctly. In many cases it does not and we either fix bugs or pull the code from the final release plan.
We were going to add a gender field to the sign up user flow, which is fine, but by mistake it became a mandatory "female/male" field for everyone. This is why this is not going live. And this is what beta releases are for, to see problems and solve them before any user faces a problem.

I would appreciate if you share this information with your friends that are also concerned. I am sorry that you were misinformed.

Best regards,

--
Anjelika Petrochenko
GM, LiveJournal US

Threaded | Flat

Interesting.

Speaking as a professional software developer.... ummm... no.

Granted, the purpose of a Beta release *is* to find and solve problems that the QA testers didn't find, but Beta releases are a long way down the chain of the SDLC (Software Development Life Cycle). For those who aren't developers, a typical SDLC goes something like this: http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle

Granted, there are variations on this, but these 10 steps represent a fairly typical SDLC.

Pay particular attention to Steps 7 and 8. This is where the testing gets done. This is where this code was at the time everyone found out about it.

Given how far things had progressed, why are we supposed to believe that this was just a mistake?

this was the response back to genderfail

no subject

no subject

(no subject)