Thoughts on cutting a beta release for 6.x-2.x-dev branch

I could definitely use some feedback on any and all of the 6.x-2.x issues. I can do the coding, but some of the things are conceptual and need brains to bounce off of. Any and all help would be appreciated.

I'd like to move to a full 2.0 release as soon as possible, but there a few issues that are holding things back.

I also really need a stake in the ground for the 2.x family. Without an alpha (or beta/rc/whichever), we are using dev (HEAD) on multiple sites. It's so hard to know which site has which version!

An alpha, asap, would be truly appreciated and make me love the skinr team even more.

We would all LOVE to see skinr have a stable 2.x release! However with Jacine basically mia for the next month or so we all need to step it up in the issue queue. I am trying to do so and perhaps you can help out also. Bala is only one person... he can't do everything himself.

I've been testing driving Skinr on a large multi-site install for a big client — and I haven't run into any problems or bugs yet. Nothing for me to report in the issue queue... so that's good news.

For what it's worth, we've gone through and marked all the current outstanding issues that need to be addressed before the official 2.x release as critical in the issue queue. If you can go through and help widdle down and close all the critical issues, we can get a point release out. Here is a quick link:

http://drupal.org/project/issues/skinr?text=&status=Open&priorities=1&ca...

And the list of issues:

#744706: Add Features support
#838234: _skinr_add_file() creates wrong file paths
#866184: Skinr forces Panels 3.7 into legacy mode
#796780: Run Skinr first to avoid problems with other modules during hook_init
#885584: Fatal error: Call to undefined function skinr_flatten_skins_array()
#825358: Conditional javascript not loading correctly in dev release
#855602: Allowing modules to contains skins

I think we can remove #885584 as a release blocker. As this has been confirm to only be a 6.x-1 issue.

Skinr 6.x-2.0 release blockers:

Open critical issues for Skinr 6.x-2.x-dev

In my opinion, Skinr is probably ready for a 6.x-2.0-alpha1 now, for a beta1 after #744706: Add Features support (new feature), and for 2.0 when the rest of critical issues are fixed.

hmm, I guess I better stop slacking off and go work on that issue :-) .

I'm in a tough spot. I cannot fix most of these issues personally, and my attempts to get help have basically been ignored or pushed aside for paid work and until they build up to a completely unmanageable level. I am disappointed and feel like this is never going to happen.

I've been soliciting help from other developers... @ericduran has been a big help and @sun has agreed to help with the Drupal 7 port when he gets some time, but other than that, there are quite a few big issues that need resolving before this is ready:

Critical and Major

marking as postponed because jacine and moonray would like to focus on the d7 version and then go back to 6 since major changes are being made.

Closing D6 tickets.