My answers below
+1
But with one very strong
suggestion. In fact, let's say a conditional +1 :)
I think on the "front page" of
your review materials you should mention the same thing you did in
this note: "Note this release changes the major field of version
number since there were some deprecated APIs removed (see N&N
for details)" Or something like that. I'd say probably as a
paragraph in your initial "description".
Thank You, added.= = = = =
More minor, I think it's always nice to say something on front page about "72 bugs fixed" or similar -- this is the place to brag a little. :)
We have this in N&N. I’ve added it to main description also. Also minor, I think "communities" usually should mention the "3 pillars" -- 1. committers and contributors as you do (though, to stay vendor neutral, I would not mention "Zend Technologies" -- but, minor comment). 2. adopters (as I think you do) but also 3. user community (usually reflected in "forum activity, bugs opened by users" or other similar things.
I mostly copy/paste this part between releases. It’s hard to say about our community for now. We lost huge part of them in past in favour to netbeans and later to *storm (me also) :/ Most of them are now organized around adopters plugin hosted on github (we plan merge one of them into next release [1]). I’ll try improve this description in 4.1. These minor suggestions are just that ... suggestions -- not part of the "condition".
= = = = =
Most minor of all -- my own personal user-question :) -- I still see "Unsupported Content type in Editor". I've always assumed that was my own "install mistake" or something. But if that is a known issue, let me know the bug or work around.
This message is from WTP (PHP Editor is based on WTP HTML). There are two open bugs [2] [3] reported in past but I personally not able to reproduce. Thanks. I am very glad you (and others) have kept the project going!
Thank You! |
