What about a new release? The last 'recommended' release is half a year old, and nowhere near the current code. Long fixed issues are not seen in the queue either, unless searching or the like. No wonder, that people report bugs, where recommended code doesn't work, and no issue is open.
I know, but my estimate (from what I've seen) is another half a year, before all that gets fixed. So the roadmap is good, but perhaps a bit too ambitious - or the intermediate state too confusing for "normal" users. I would prefer more frequent releases, even if these were Alphas (rather than Alphas called "-rc") or whatnot, as otherwise people are forced to figure this out painfully, and then run -dev version on sites (which is wrong, by definition).
Please don't take this as offense, I really appreciate all the work done here. I'm just saying my opinion, to provide a bit of feedback.
no offense taken. In fact you have it spot on. i've made a mistake calling my releasec RC* because they are really alpha releases (feature development). The plan is to stay consistent to current workflow until we make an official 1.0 release after which we will make ammends to the workflow to be more tranditional alpha >beta> rc > final.
Saying that, I think it is also a good idea to add that the alphas are stabe and data should not be lost even as features are added/refactored. That was the only "goal" of the first release - have something there so that people can upgrade from Drupal 5 if needs be.
Comments
Comment #1
litwol commentedHave been fixed in development branch already. Please search old issues before reporting bugs. thanks.
Comment #2
JirkaRybka commentedWhat about a new release? The last 'recommended' release is half a year old, and nowhere near the current code. Long fixed issues are not seen in the queue either, unless searching or the like. No wonder, that people report bugs, where recommended code doesn't work, and no issue is open.
Comment #3
litwol commentedactually this is our RC3 road map, nothing more and nothing less: http://drupal.org/node/372201#comment-1747296
Comment #4
JirkaRybka commentedI know, but my estimate (from what I've seen) is another half a year, before all that gets fixed. So the roadmap is good, but perhaps a bit too ambitious - or the intermediate state too confusing for "normal" users. I would prefer more frequent releases, even if these were Alphas (rather than Alphas called "-rc") or whatnot, as otherwise people are forced to figure this out painfully, and then run -dev version on sites (which is wrong, by definition).
Please don't take this as offense, I really appreciate all the work done here. I'm just saying my opinion, to provide a bit of feedback.
Comment #5
litwol commentedno offense taken. In fact you have it spot on. i've made a mistake calling my releasec RC* because they are really alpha releases (feature development). The plan is to stay consistent to current workflow until we make an official 1.0 release after which we will make ammends to the workflow to be more tranditional alpha >beta> rc > final.
Comment #6
naheemsays commentedSaying that, I think it is also a good idea to add that the alphas are stabe and data should not be lost even as features are added/refactored. That was the only "goal" of the first release - have something there so that people can upgrade from Drupal 5 if needs be.