I'm hoping to release another stable release soon. Knowing that a lot of people only upgrade from stable to stable, I hope that we can at least avoid introducing bugs.

The release will wait for the following issues:
- #735694: timetracking records not taking fixed price from organisation, project or task.
- #746410: tax 1/2 not hidden on screens and print-outs if switched off in admin settings

The following might be committed in time:
- #686362: Allow calculation of total to use rounded tax amounts, and other invoice processing
- #257881: New attribute results in missing icon
- #747316: Show real duration in timetracking

Anything else: I'll try to keep reviewing, but won't commit until after the next stable release has gone.

Please could I encourage everyone to download a copy of the latest development build and test it on a copy of their installation.

Comments

tazus’s picture

tazus commented

Hi, thank you for the update.

However, for my knowledge, I still have the same problem in

http://drupal.org/node/380008#comment-2248870

This problem was duplicated by me.

That's related to team's access to Project, Task and Ticket. The only way the team user can access these items are enable "View All" in Drupal ACL settings.

The interesting part is: the list of Project, Task and Ticket items are correct according to the Assign Project Manager settings. But, when they listed, the individual view just shown "Access Denied".

So, is it possible to get this ironed before 1.32?

juliangb’s picture

juliangb commented

Hi @tazus,

Has this been posted as its own issue yet? A comment in a closed issue will not attract attention.

The main reason that I'd like testing of the -dev release at this point is to catch bugs that may havce been introduced by changes since the last snapshot release, so that people can upgrade production sites with confidence - in my opinion, a snapshot release should be as stable, or more stable as the previous.

Therefore, the way to get that fixed, is to make sure that there is a bug report filed, and push on that issue. It won't get into 1.32, but I'm aiming to publish releases approximately monthly (if enough progress has been made), so if a fix is available, it is likely that it won't be long before it is in a stable version.

tazus’s picture

tazus commented

Hi, as you advised, I create a new issue and worked it http://drupal.org/node/762002.

I kind of found out the problem and test the result but not sure the proper way to patch the problem. I do believe that it should be really quick for you to make proper patch and including this fix into 1.32.

Hope this make this module more robust.

Happy coding!

juliangb’s picture

juliangb commented
Status: Active » Needs review

OK - 6.x-1.32 will ship in the next few days.

I would encourage all to download the development release after midday today and test.

The 6.x-1.32 release will be exactly the same as the current development release assuming no regressions are found.

juliangb’s picture

juliangb commented
Status: Needs review » Fixed

6.x-1.32 has been released.

I will start considering the next official release (6.x-1.33) in approximately a months time, assuming that there has been a decent amount of progress made since then, or sooner if critical bugs are solved.

Status: Fixed » Closed (fixed)

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