I don't much like the idea of modules with warnings (alpha, beta, use with extreme caution, not for live site, etc), listed under an official release heading, I understand that the official release heading doesn't pertain to the module itself (which IMHO) is a mistake because it only adds to confusion.

just my 2 cents - why bother realizing it when its not ready, if anything it should go under development heading. Anything that goes under official release should be functional for live site.

Comments

nicholasthompson’s picture

nicholasthompson
Primary language English
commented
Status: Active » Closed (works as designed)

I worked on the dev version and got it "working" and made an alpha out of it. I then fixed some more bugs and made another alpha... I clearly state that its in development and the dev branch is (or at least was until recently) ahead of the alpha branch.

I assume that as you dislike my approach of releasing an alpha of my work before its 'finished', you must also dislike the approach Drupal Core takes - they had a beta out recently and a Release Candidate right now - even though there are currently 12 critical and 69 non-critical issues pending on it. Maybe they should wait till its all fixed before releasing Drupal 6? ;-)

darumaki’s picture

darumaki commented

My critique wasn't so much you releasing something with warnings and such but was that it was listed under official releases, it can confuse people, it would have been better to list it under development releases. Just because you have it stated doesn't mean people won't download it and use it live due to it being under official release, people are noobs they only see the official release heading and their eyes light up.

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

Thats true - and I appreciate your post.... but 2 points...

(1) Stupid people will be stupid no matter what you do. If someone decides to put an alpha release directly onto a live site and it promptly breaks then they're probably just as likely to do the same with a dev release! Its only sensible people who test dev/alpha/beta/release candidate before putting on live.

(2) Unfortunately, there is not way of putting a branched version under the development list. I dont 100% understand CVS and its version jargon - but DRUPAL-5--2 being the dev version appears under the dev list, however the DRUPAL-5--2-ALPHA1 (2 and 3) are branches which are considered 'official' releases...