First of all, I'm sorry NineSixty hasn't been developed further at this point. I had plans to improve it as a base theme for version 2 but my priorities were lying elsewhere. It also didn't help that I lost some interest but I will definitely pick-up where I left off. This doesn't mean I see 960.gs (the original grid system) as less relevant. In fact, I've been using it in other projects. It's just my role in creating a solid base theme that has been waning.

I do think the NineSixty Drupal theme is less relevant today since anyone with some experience can integrate 960.gs into their themes from scratch and there are plenty of alternatives that add more flexibility and are better maintained. It was never my intention to add too many user friendly options and this will continue in version 2. New features will target theme developers only.

With that said, NineSixty v.1 will be updated for Drupal 7 for those moving onto the new version of core. A new release will be posted to coincide with the Core release on January 5th. Beta versions of NineSixty v.2 for Drupal 6 and 7 will start appearing about a month after.

Comments

dvessel’s picture

dvessel CreditAttribution: dvessel commented

A release is coming later today. I'm first updating the 6.x branch so it's synced up with 7.x. A new 6.x release will come along with this.

derhasi’s picture

derhasi CreditAttribution: derhasi commented

@dvessel, I worked with the 6.1-dev version on my site. Do these changes go into a 6.2 branch, or how will be processed in that case?

dvessel’s picture

dvessel CreditAttribution: dvessel commented

Sorry derhasi for the confusion. The 6.x-1.x-dev and 7.x-1.x-dev branches will be brought back close to the previous 6.x-1.x-dev state. After that I will create a v.2 branch.

For now, don't upgrade. Maybe it wasn't the best move but I reset it so I had a common point to develop both 6.x and 7.x branches in parallel. I wasn't sure of another way to go about it.

fgm’s picture

fgm
Primary language French
Location Paris, France
CreditAttribution: fgm as a volunteer and at OSInet commented
Issue summary: View changes

Since this issue didn't move since 2011 and the last commit was in march 2012 in both 1.x and 2.x, would it be a problem to tag these final commit as the hopefully final version 1.1 and 2.0 respectively, so that the theme doesn't remain flagged as recommending the 1.0 version on the admin/reports/updates screen ?