I've been beating up the issue queue here. http://drupal.org/project/issues/install_profile_api?categories=bug is down to a pretty small number of relatively minor bugs. I'd like to roll some official releases. At the very least, I'd like to get a new 6.x out so our "recommended" release doesn't have a README.txt from another module. ;)

But, I think things are relatively stable and happy now. I don't see any reason to keep calling this stuff "beta". Let's just ship 5.x-2.0 and 6.x-1.2. As we fix more bugs, we'll make more releases, but it'd be nice to have a relatively clean slate to work from.

Any objections?

Comments

dmitrig01’s picture

+1

boris mann’s picture

Yep, go for it. Wow, real releases :P

Now, at some point, I'd love to start thinking about less hacking our way around the lack of a bunch of this stuff in core...

webchick’s picture

I greatly welcome patches in that direction. :D I know Henrique/recidive is working on some backend standardization to make CRUD easier. http://groups.drupal.org/node/16711 is a jumping-off point for these efforts.

quicksketch’s picture

Assigned: dww » quicksketch
Status: Active » Fixed

I hope no one minds that I hopped in and finished this task up. I cleaned up the remaining issues for the Drupal 6 branch and backported all the changes (nice work dww on backporting the Drupal 6 version!)

To avoid confusion, I've re-branched the Drupal 6 version into DRUPAL-6--2, since it is a pretty drastic departure from the 5--1 version. So now we have DRUPAL-6--2 and DRUPAL-5--2 branches for active development, which should be mostly in sync. The new releases are both 2.0 versions.

boris mann’s picture

Awesome, thanks Nate. One thing for everyone to review is Alex Barth's thoughts on Port --> in the comments on this Profile Wizard poll: http://groups.drupal.org/node/17916

dww’s picture

Title: Create 5.x-2.0 and 6.x-1.2 official releases » Create 5.x-2.0 and 6.x-2.0 official releases
Version: 6.x-1.x-dev » 6.x-2.0

Agreed, thanks Nate!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.