View Single Post
Posts: 207 | Thanked: 967 times | Joined on Apr 2014 @ Madrid, Spain
#479
Originally Posted by trancethrust View Post
Note that 2.0.6 still has not appeared in testing, and that 2.0.5 hasn't even cleared voting yet.

Is it an idea to slow down releases?
Hi!

My policy is to wait at least 24 hours between uploading to devel and promoting to testing. The idea is that biggest bugs can be detected early and not be exposed to the bigger subset of people who use testing. So don't worry, today 2.0.6 will reach testing.

On the other hand, I can't force people to vote on new releases. The has been only two positive votes, but no negatives. What does this mean? People don't like new release or they just don't care to vote them?

I'm open to ideas, so please propose anything you believe can be helpful.

EDIT: Given that the segfaults seem to continue, I won't be promoting this version to extras-testing. I've also found some cases in which new group receipts functionality isn't working very well, so I'd rather wait to solve both issues before promoting a version that I know is not going to add much. Sorry
__________________
OVI and downloads.maemo.nokia.com mirror
Yappari for Maemo
pyLedger for Maemo


If you want to donate, please read this. If you still want to donate, contact me via private message or email. Thank you.

Last edited by ceene; 2015-03-01 at 15:25.
 

The Following 5 Users Say Thank You to ceene For This Useful Post: