What's the status of the 5.x version really now?

"5.x-0.1-beta" doesn't inspire much confidence, and the text regarding the "5.x-0.x-dev" release isn't very encouraging either.

I think problems with upgrade from 4.7 require a big fat warning in the project description and the readme, but imho they should not prevent a generally consumable 1.0 (or 1.x) release to happen.

CommentFileSizeAuthor
#8 project_upgrade_5x.patch.txt1.81 KBdww
#5 project_UPGRADE_2.txt2.15 KBdww
#4 cvslog_UPGRADE.txt920 bytesdww
#3 project_issue_UPGRADE.txt899 bytesdww
#2 project_UPGRADE_1.txt1.53 KBdww
#1 project_UPGRADE.txt1.23 KBdww

Comments

dww’s picture

dww
we/he/they
commented
Title: 5.x status » Create a 5.x-1.0 release
Assigned: Unassigned » dww
Category: support » task
Priority: Normal » Critical
Status: Active » Needs review
StatusFileSize
new project_UPGRADE.txt1.23 KB

Agreed. Sorry, there's just way too much work for me to do, and this has continued to languish. It's now near the top of my radar.

Here's my current plan:

  • The crappy upgrade path will only effect a relatively small # of sites.
  • I'll just add an UPGRADE.txt about it, and mention it on the project page, and release notes for the 5.x-1.0 release. I'll commit UPGRADE.txt to both DRUPAL-4-7--2 and HEAD.
  • All of the above will point to http://drupal.org/node/163616, a handbook page I just wrote outlining the upgrade hell and who's effected by it.
  • Once UPGRADE.txt is in, and some of the other active bugs in the queue are resolved, we'll just make an official 5.x-1.0 release and a DRUPAL-5 branch.
  • HEAD will then become a 5.x-2.* development area for a little while, before we start porting to D6.

A) Copy of UPGRADE.txt attached here for review (it'll be named UPGRADE.txt in the project directly, I just renamed it for attaching it to this issue).

B) Any objections to the plan?

C) Any feedback on that handbook page?

Thanks!
-Derek

dww’s picture

dww
we/he/they
commented
StatusFileSize
new project_UPGRADE_1.txt1.53 KB

Updated copy of project.module's UPGRADE.txt here.

dww’s picture

dww
we/he/they
commented
StatusFileSize
new project_issue_UPGRADE.txt899 bytes

Copy of the (simple) UPGRADE.txt for project_issue

dww’s picture

dww
we/he/they
commented
StatusFileSize
new cvslog_UPGRADE.txt920 bytes

Copy of the (simple) UPGRADE.txt for cvslog

dww’s picture

dww
we/he/they
commented
StatusFileSize
new project_UPGRADE_2.txt2.15 KB

New version for project.module based on IM discussion w/ hunmonk.

dww’s picture

dww
we/he/they
commented
Status: Needs review » Active

Ok, the latest 3 are all committed to their respective directories (on HEAD), and then branched to DRUPAL-4-7--2. Now we just need edits (probably only needed for project/UPGRADE.txt) to talk about the 4.7.x-* to 5.x-1.0 upgrade path (which says "if you're running 4.7.x-1.*, upgrade to 4.7.x-2.* first; if you're at 4.7.x-2.*, upgrade is trivial").

dww’s picture

dww
we/he/they
commented

In addition to the UPGRADE.txt edits, here's my current list of issues I'd like to see fixed before the 5.x-1.0 release: http://groups.drupal.org/node/5448

dww’s picture

dww
we/he/they
commented
Status: Active » Needs review
StatusFileSize
new project_upgrade_5x.patch.txt1.81 KB

Patch against UPDATE.txt in HEAD for the 5.x-1.* upgrade instructions.

Also, FYI, see http://drupal.org/node/163616 for the handbook page on upgrade details for 4.7.x-1.* to 4.7.x-2.*.

hunmonk’s picture

hunmonk commented
Status: Needs review » Reviewed & tested by the community

upgrade docs for 5.x look good.

dww’s picture

dww
we/he/they
commented
Status: Reviewed & tested by the community » Active

Committed the UPGRADE.txt change to HEAD.

hunmonk’s picture

hunmonk commented
Status: Active » Fixed

5.x-1.0 released, and installed on drupal.org

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)