Status of Node Gallery 3.x

I'll go through that list, and mark the ones that I think should go in before alpha release as 'critical'. I also need to go through the code and make sure that all the @todo's are also issues.

Welcome back, btw - you were missed :)

Setting them to "fixed" gives people a chance to say "wait a sec!".

From http://drupal.org/node/156119:

Fixed
The issue has been resolved (usually by committing a patch). Issues that remain in this state without any additional comments will automatically be set to "closed (fixed)" after two weeks. This gives interested parties time to reactivate the issue if they see a problem with the fix and also allows time to see that a change has been made.

I took a little time to update my demo site with the latest and greatest NG3 + jQuery UI + plupload + views_galleriffic: http://ng3demo.sysadminsjourney.com

Not very :)

I did get rid of all the unused theme code and tpl files, but got sidetracked with other issues. It's my focus for this week though. If nothing else, I want to get everything existing moved out into .tpl.php files (manage images, sort images, image navigator) for easier overrides. If I have time and it's not too hard, I'll probably ship some default css to add a little zip to some of the views.

I just updated the gid issue - I think we should hold off on that one.

#972678: Consolidate Views? - do you want to handle this one?
#973310: Description text should wrap on manage images page. - I don't think this is a "blocker", but I really hate it. What's more, I have no idea where to start looking on that one. Do you have any ideas?
#974228: NG Navigator Block - I'm going to update that issue in a few minutes
#959608: Refactor 3.x theme code - there's just a bit more to do over there

Once these are dealt with, I want to personally go through a lot of permissions testing. I have a nasty habit of developing with UID 1, and NG2 had a whole slew of permission issues when I first came on as co-maintainer. I would create an issue for it, but I can't quantify exactly what needs done, I basically just have to come up with scenarios in my head and act them out.

Well, if you'd like to take on the first part of #977942: Presets for sort image page, go for it. I'd like to have the reset to default sort button in place before alpha.

Aside from that, we need to get our doxygen docs all in place, as well as start working on a 3.x handbook section.

Looking at the latest usage statistics, it looks like we saw a big bump in 3.x users this past week (the issue queue indicates that too), so I think we're getting really close to alpha. Once we get some basic docs in place, I'm good with tagging it and opening the flood gates.

I got some time today to review and commit some code. Comments:

#676486: Views filter and sort for Image date - if someone can review that and mark it RTBC, I'll commit it in. Even if it doesn't perform well, it will only affect those who use the sort/filter so I'm not too worried there.

#389462: Allow sub galleries - I understand and share your opinion on it. I hope you can see my point that we're just too late into the 3.0 life cycle to commit such a huge patch with far-reaching effects. Since development is slowing on 3.0, what do you think of just maintaining that as a patch to 3.x, and we can roll it into 3.1? IMO, that one feature alone is enough to make a 3.1 release.

#828228: Additional options for NG3 / provide shortcuts to settings - those features are so small, I think we can slip them in through alpha/beta as the users request them. It may simply be a documentation/help issue - I've gotten quite used to knowing where to go for those settings (but I know I'm not the typical NG user). Either way, this one isn't a blocker.

I've done the permissions testing, and it all seemed good to me, so we can cross that off the list.

So, at this point, I think I'm going to call a "code slush" like core did for D7, where only "critical" missing features, or very minor features are implemented. Also, IMO, we don't need documentation for an alpha, because we might find bugs that cause the docs to change. However, docs need to be done between alpha and beta, so a "call to arms" task is a good idea. Perhaps @dbeall and @dddave are still lurking and can lend their talents in testing and documenting???

Another missing milestone is that of a string freeze for our translators. I would anticipate making beta1 be the start of the string freeze, so translators can start working on translations starting with beta1.

At this stage, I think we're ready for alpha. I'll plan on tagging dev on Monday with an alpha1 tag unless anyone objects between now and then.

Just tagged 3.0-alpha1 and updated the project page with notes about it.. Woooohoooo!

@ktmom, great that you're subscribing and all, but please don't change the issue settings unless you know what you're doing. Resetting issue settings back to 3.x-dev, normal, and active.

I think that with the some of the scalability issues addressed, the added caching (and subsequent bugfix against that new code) and some of the other minor bugs, alpha2 is drawing near.

Here's a link to all relevant issues we need to look at before alpha2.

alpha2 is drawing near. Here's a list of all non-Documentation issues pertaining to NG3.

Here's a list of all documentation and language issues still remaining. Note that IMO missing docs and translations can be added throughout alpha and beta, but must be complete by .0 release.

All new features being added need to be implemented while still in alpha, beta will be reserved for bugfixes and doc/language updates only.

I'm pretty sure we'll have alpha2 tagged in the next day or two.

Just a quick update to subscribers on this issue - alpha2 should be released today. We'll plan on doing an alpha3 shortly after that, and with any luck, beta1 will come after alpha3.

Anyone who actually reads the project page before downloading the module will likely choose 3.x. I don't know what happened, but I don't really trust those Dec 12 numbers - I find it hard to believe we gained 100+ users on the 2.x-dev snapshot in one week. I've seen 'blips' like that before, and they usually self-correct the following week.

I'm open to re-wording the project page, but IMHO, 2.x won't stop growing until we make 3.x the 'recommended' release. I'm not quite ready for that just yet, we need documentation, and we also need all our "helpers" ready to help with the issues that pop up in the queue for admins who don't check the docs when upgrading major releases.

What I am personally pleased with, however, is that 2.x issues have pretty much stopped showing up in the queue and we're only dealing with 3.x support/feature/bug requests.

@quebec

IMO, NG3-alpha2 has fewer bugs, performs better, and has way more features than NG2. If it were my choice, no one would be running NG2 anymore :)

You're pretty well guaranteed to not lose any data on the upgrade from NG2 to NG3, but any custom theming and views will need to be redone. I highly recommend upgrading in a test setup first. I know firsthand of a few sites running NG3 in production since before alpha.

Regarding your idea - do you mean like http://drupal.org/project/node_gallery_user_profile ?

@Quebec - this is discussion for another topic - if you have further questions, please open an issue over at ng_user_profile's queue. Quick answer: once installed, the module will render the view anytime someone hits the user//galleries link. So, if using author_pane module, you can add your own links using some form of token, then yes, you should be golden.

Just a quick update. Development has slowed a bit recently, @scroogie has a big project that has limited his time. I actually managed to convince the powers at $dayjob to adopt Drupal as the platform for our intranet and to make me the lead dev. While this is awesome news, it means I'm basically working two positions until a replacement is found for my old position. Throw in tax season, and the fact my big screen TV died, and I haven't had much Drupal time lately :)

I hope to have this thing wrapped up by DC Chicago, but make no guarantees.

Hah, you would think so. But you have to research, shop for the best price, etc. I'm wall mounting this one, so I need to run power, HDMI, etc. It takes way less time to *watch* TV. I'm conducting a 100 hour burn-in on it now, so I have 4 days before I can start really using it :)

Here's what I'm using:

Non-documentation TODO's

Documentation TODO's

No problem. I think we need alpha3 to get the image rotation and a few other small features out to the masses for some testing, but with any luck that alpha will be very short lived and we can roll into beta from there. Beta1 will signify that no new features will be implemented, and therefore no new strings will be added at that point. Grammatical/spelling errors and clarifications can be done throughout beta. My hunch (and hope) is that the beta will primarily be used for fleshing out documentation, and fixing a few minor bugs.

I'm going to do all that I can to get some of these straggling bugs out of the way this week. I *really* need that permissions patch tested, and the best way to do that is to roll it into a release.

Introducing that large of a patch into a release without testing means I'm going to tag it as alpha3 instead of beta1. Once alpha3 proves stable, I'll tag beta1. Once docs are complete and bugs squashed, we'll release 3.0.

It's my opinion that we've hit a stability milestone with 3.x. Users keep on going up, yet the number of bug reports are going down. The only issue I'd consider fixing before tagging beta1 is #1043532: Breadcrumbs use hardcoded strings instead of menu entries, but as noted we could fix that one after beta/final if we wanted to (it's not a blocker).

If I get time this weekend, I'll tag beta1 from the current dev release. @scroogie, if you have time before Sunday, feel free - I have a family trip to go on.

Once beta1 is released, we need to really concentrate on docs. Once docs are complete, and any bugs found have been resolved, we can tag beta2, and mark it as the recommended release.

NG 3.0-beta1 tagged, and release created. Builds should appear soon.

I was able to get some time to work on the help/documentation tonight, and committed in some new stuff. Aside from docs, the only bug I'm aware of that can block a 3.0 release is #1193832: Gallery List defies i18n. I'm hoping one of the maintainers who speaks German can weigh in on that one (hint, hint :) )

I'll keep cranking on the help, but I'd love any feedback or suggestions. Just install the dev version, make sure advanced_help is installed and hit /help/node_gallery.

I got crazy with the advanced help. In the interest of time, I got rid of all the "advanced topics" stubs. Some of it was in place already (new relationships), some belongs in other modules (node gallery vbo), and some is so advanced that a user wouldn't care about it and a dev would grok the source (api). If someone wants to write it, great, but I don't want it to hold us up.

So, without further ado: http://live.justintime.gotpantheon.com/admin/advanced_help/node_gallery

I would love someone to go over that a bit, and file new issues for anything they find wrong. Looking at the issue queue, once this is knocked out I think we're ready to tag beta2, and make it the recommended release. After a few weeks of watching for issues, we can tag 3.0. Here that?? It's Hell freezing over!

@scroogie - those are fixed, I'll push them up later today. Regarding linking inline, that's one of the cool things about advanced help. If you link from your help into a site URL that isn't under /help, it will place the little ? mark link there automatically. To see an example, hit admin/content/node-type/node-gallery-gallery/fields.

@dddave - http://live.justintime.gotpantheon.com/help/advanced_help/translation

6.x-3.0-beta2 released today. I'll give it a few days to get out to the early adopters, then mark it as the recommended release so long as no blockers crop up.

Just marked 3.0-beta2 as the recommended release.

No show-stoppers have cropped up, and at this point I'm confident 3.x will remain the recommended release. I'm marking this as fixed - the status of 3.x is "use it!".