Good news, the first release of 0.16.0 has been released. All critical bugs have been looked at and fixed.
- BUG352 – Unable to assign existing tasks
- BUG361 – New instance does not contain bug config
- BUG362 – Bug Client Has No permission
- BUG363 – Project not showing connected customer if customer has no organisation
- BUG364 – Multiple Bug Clients – can not search second bug client for bugs
- BUG370 – Quote Template – CSS field should be plain text
- BUG371 – Extracting/Printing PDF not currently working
- BUG372 – Service lines will appear in quote preview even when there are no service lines
- BUG375 – Can not reset password
- BUG376 – Update to Python 3 has broken models
- BUG377 – Email Quote
- BUG378 – No back to users
- BUG380 – Responsible Customers
- BUG381 – Lack of space at bottom of page
- BUG382 – Webserver is down
- BUG385 – Organisation Campus not rendering
- BUG386 – Search ALL does not work
- BUG387 – New project does not work
This branch is currently focused on fixing security issues and bugs. We are hoping to have another release at the end of the week.
Well this is a bit of a click bait title which I didn’t mean for, however I will outline some of my struggles of porting from Python 2.7 to Python 3.6+.
It is the little changes that seems to hurt. Last night I found the following bug – https://bugzilla.nearbeach.org/show_bug.cgi?id=385. What could it mean? My following process weeded out the exact issue (after each test I returned to the original code);
- Remove ALL context – worked
- Set template onto BLANK – worked
- Remove bottom part of the “New Campus” template – did not work
- Remove top part of the “New Campus” template – worked
- Decided the issue was with one of the fields. Removed all fields and start placing them back one at a time
This processes led me to find out that my special widget was producing this issue. So I went to the “forms_special_fields.py” and search for the “render(” function. It found them.
def render(self, name, value, attrs=None, choices=()):
The code above works in Python2.7, however there was a slight change. This code has to now be
def _render(self, name, value, attrs=None, choices=()):
A simple _ was causing a massive critical issue.
Alpha Development-0.16.0 Status
The bug testing and fixing of 0.16.0 is still going ahead rather well. We currently have found 25 initial bugs. We want to make sure that there are NO critical bugs when we release 0.16.0 and then fix up the remaining bugs in later releases.
At the same time we are also fixing up our documentation to represent the change from Python2.7 to Python3.6+. This will include the pictures on Github and also our Confluence site.
This has been a huge release for NearBeach. The following has been achieved;
- Migration from Python 2 to Python 3
- Migration from Django 1.11 to Django 2.1
- Groups can now be children of other groups – further development in the near future
- Users can have “Reports To” under each group
- Create Quote Template for printing/emailing
- New project has an enhanced datapicker
- New task has an enhanced datepicker
Current known issues
As development-0.15.1 is an alpha release we know that there are many issues within the system. We were hoping to fix many of these issues before release however hit an issue during this month. It was unforseen that we had to move to python 3. It was a move that was on the table.
Please note this release will be buggy and we are fixing most bugs in the next development branch (0.16).
We will be updating our documentation over the next week. We currently have commented out most of the sections. We will also be adding a Ubuntu 18.04 section and hopefully a CentOS version before the final release of 0.16 branch.
Test Server Down
Our test server is currently down. We have noticed the issue is caused by Apache consuming large amount of space which in turn is causing MySQL to crash. We are looking at alternative options for apache. We will first determine if it is an apache issue or if it is because of a hungry piece of code I have written. We do require this server for testing purposes this month. More information in the coming week.
I am happy to announce that development branch 0.15.0 will be released tonight. This is also the last branch that be written in python2.7. Now officially we are moving onto python3 (YAY!).
NearBeach is designed to be easy every step of the way. This includes;
- Setting up
Recently we have come across a function that will work perfectly fine on our local station tests, however did not work in the server. This was because the library that the function relied on would not work heedless.
I have been looking for a solution and I think I have found one. The problem is that we need to upgrade to Python3. This is not a small feat.
We have been meaning to do this for a while now as python2.7 runs out of life in the next couple of years. We also want to keep up to date with the latest Django version. We are hoping to make a full upgrade this week whilst completing all this month’s enhancements.
NearBeach currently connects flawlessly to Bugzilla, however we know there are a lot more bug tracking tools out there. We are currently playing around with MantisBT. More news to come soon
The users can now add and edit quote templates and preview their quotes. Only a few more critical functions to add into this functionality before I will state it is completed. We are hoping to have this functionality completed by the weekend of the 25th.
Other functionality which we want to roll out is adding the ability for groups to have children and report to fields within them. This will allow more depth and structure to the groups within NearBeach. We are currently planning to see what works and what will cause more issues.
Please also consider donating to our patreon, every dollar does count: https://www.patreon.com/NearBeach
“Good news, everyone!” – Professor Hubert J. Farnsworth As most of you know, the futurama character would then go on to say “The alpha development branch 0.14 has been completed.”.
0.14 branch focused heavily on stability for NearBeach, bringing it up to a minimal viable product (MVP). This is exciting news for us, as it now becomes a transition between faintly using our own product to the start of using our product to help produce our product. We are finally happy in the direction that NearBeach is taking and will be meeting over the next few weeks to discuss the features and requirements that are missing from NearBeach.
If you have any features or requirements that are missing from NearBeach, we want to hear about them. You can either respond to this post or send us a tweet @nearbeach_inc. Without your input we will not progress.
So over the next couple of days I will be implementing campus’ for the customer module where customers are not connected to an organisation. This will be useful for cases where you have an independent consultant that you need to know their business location etc.
Another development will be the rollout of TinyMCE to help improve user experience and gathering of notes. TinyMCE still is in testing mode and we will be deciding whether to use the LITE or normal version.