Meta issue listing the things that I'd like to see happen for a 6.x-1.35 release. Plus of course, any patch that works and is tested. It may sound like a long way away, but I would like to crack on with a few things and a direction always helps.

The aim behind a lot of these will be to refactor things to use more Drupal APIs and to utilise other contributed modules, which will help with the port to Drupal 7.

I will start to list issues in a comment so that I can edit it afterwards.

Comments

juliangb’s picture

juliangb commented

Attributes:
#532420: Change attributes into taxonomy (task)

Views integration:
#854570: Incorrectly coded views support (bug)
#496458: PHP Error in Views when filtering by "Storm: Task Priority" (bug)
#902962: Handler for attributes icons in views (bug)
#916302: No "Storm: Ticket Duration" and "Duration Unit" fields in views (bug)

More tests:
#891934: Tests for Storm Ticket (feature)
(Ideally we should strive for 100% code coverage - even if this makes it tougher on developers).

Simplifications:
#671622: Remove duplication between name and fullname (task) (people)
#685140: Remove prefix and fullname fields. (task) (organizations)

Other:
#899970: Inconsistent attribute key length fields (bug)

juliangb’s picture

juliangb commented

Need to add a note to the changelog for 6.x-1.35 stating that custom views may have to be rebuilt. This is needed to get the benefits by proper views integration.

See #854570: Incorrectly coded views support.

juliangb’s picture

juliangb commented
Title: Roadmap for 6.x-1.35 » Release of 6.x-1.35
Priority: Normal » Major
Status: Active » Needs review

I think it would be a good idea to release 6.x-1.35 soon.

Therefore, I suggest that we immediately start a mini-freeze - with the only commits being to fix bugs introduced since 6.x-1.34 - in order that we can have the confidence to call this a stable release.

We haven't made as much progress against my hit list for this release as I had hoped (due to me being away from my development machine) - these can be postponed to the next release.

Please could everyone start testing upgrading to the current -dev release to test.

It would be very helpful also for people to post here to say that they are on the latest -dev.

Assuming there are no issues, I hope to release 6.x-1.25 in 1-2 weeks time.

tchurch’s picture

tchurch commented

I've had issues with my issues (just not working) so I'll take a small break and go back to them later.

I'll start testing what we now have in -dev.
I intend to get some testing of -dev done today and over the weekend so I'll give feedback then.

juliangb’s picture

juliangb commented

Thanks tchurch.

Just to confirm that the issues with your issues are not anything that has been so far committed?

tchurch’s picture

tchurch commented

No. My issues are with pending issues I'm trying to develop a patch for.

From my brief testing so far, the current -dev version (1.35) seems OK. I will continue to play over the weekend and finish them.

juliangb’s picture

juliangb commented

Should try to finish #899970: Inconsistent attribute key length fields before releasing.

juliangb’s picture

juliangb commented

Release is tagged in CVS - I will create a release node within a few days.

juliangb’s picture

juliangb commented
Status: Needs review » Fixed

Released.

Status: Fixed » Closed (fixed)

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