>Could you please explain the logic behind this as I am confused. Is this 
>due to an inefficient process, technical limitation, or other reason 
>(lack of manpower doesn't qualify as that seems self inflicted by the 
>project)? Are you somehow tracking submissions to take care of when this 
>unlocked so people don't waste their time needing to resubmit them?

Our process.  *OUR* process.  This is not your process.  Meaning it
isn't your decision.

>While they may exist I know of no other project, including OS, that halt 
>development like this for long, if at all, to do a release. Again, they 
>may exist I just don't know of any and find the process awkward and 
>confusing.

Other projects split their developers between "making the release" and
"working on the future", and as a result they take a long time to make
crappier releases.

That's their choice.

It is not our choice.

It is *NOT YOUR CHOICE*, and you don't have standing to comment.

Reply via email to