I've just committed a revision to the trunk merging the changes made in the v2.0 branch back into the 1.5.3 codebase. It has taken a while (off and on for the past year or so), but it gives us one common codebase again. By committing this now, I am looking for help to finish it and release a v2.0.
The efforts to achieve a v2.0 died off nearly two years ago, but there was some good progress made on features like:
- expenses
- approvals (for timesheet and expenses)
- internationalisation
It would have been a shame if these were left to rot. There is another branch (txsheet-2.0-timezone) that has not yet been merged back.
The trunk version (revision 496) is not finished, or tested thoroughly, and there is not installer for it. Given an appropriate database, the code shows most of the pages without errors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now we try to use 1.5.3. But unfortunately we do not have enough approvals.
I had a conversation with Mark, that would see improvements set (pre version 2.0). But without the approval can not yet use the TS as we need.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've just committed a revision to the trunk merging the changes made in the v2.0 branch back into the 1.5.3 codebase. It has taken a while (off and on for the past year or so), but it gives us one common codebase again. By committing this now, I am looking for help to finish it and release a v2.0.
The efforts to achieve a v2.0 died off nearly two years ago, but there was some good progress made on features like:
- expenses
- approvals (for timesheet and expenses)
- internationalisation
It would have been a shame if these were left to rot. There is another branch (txsheet-2.0-timezone) that has not yet been merged back.
The trunk version (revision 496) is not finished, or tested thoroughly, and there is not installer for it. Given an appropriate database, the code shows most of the pages without errors.
Can we expect in the near future a new version? And if so - what will there?
It depends on what you mean by a new version. If you are looking for a shrink-wrapped production release, then that may take a while.
What's your usage of TSNG? What version are you using today? How mission-critical is it? What level of support do you (can you) provide?
The new features will be as in the message above, and any more we can get in. What are you looking for?
Now we try to use 1.5.3. But unfortunately we do not have enough approvals.
I had a conversation with Mark, that would see improvements set (pre version 2.0). But without the approval can not yet use the TS as we need.