You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
(2) |
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(5) |
May
(3) |
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2005 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
(8) |
May
(2) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
2006 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(3) |
Sep
(3) |
Oct
(2) |
Nov
|
Dec
(1) |
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(5) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Daniel A. E. <ze...@ze...> - 2006-01-05 19:56:55
|
Hi. We're planning on releasing BUGS 1.7.2 Jan 6th, so here's a heads up about that. Usually we notify earlier but this time the release is already heavily tested and shouldn't bring any surprises, so there's no need extending the test period which started January 2nd. You can download BUGS 1.7.2 FINAL from here: http://www.zegeniestudios.net/BUGS_1.7.2.zip . Following January 6th, it will be available from our sourceforge.net download area. Thank you for your interest in BUGS - the Bug Genie. |
From: Daniel A. E. <ze...@ze...> - 2005-12-06 18:02:56
|
An exploit has been uncovered, which allows anyone with login access to BUGS to update and alter bug descriptions, thereby gaining access to hidden bug reports and -details, as well as deleting and altering bugs. The bug applies to all versions of BUGS. You can read more about the issue, as described here: http://bugs.c3pc.com/bugs/view_bug.php?bug_id=362 The BUGS team has published a fix for this bug, which was posted just recently. The fix can be downloaded from the link above. We want to thank macournoyer for bringing this to our attention. -the BUGS team ------- This is an important security update, published to subscribers of this mailing list. To unsubscribe from this mailing list, visit http://bugs-bug-genie.sourceforge.net for more information |
From: Daniel A. E. <ze...@ze...> - 2005-12-05 02:40:11
|
Welcome to this third BUGS Newsletter! In this issue: * Development status update * December release: BUGS 1.7.2 * BUGS 2 "new feature" highlight: Calendar(s) The BUGS newsletter is a service we provide so you can easily stay up-to-date with the latest new information regarding "BUGS - the Bug Genie". The newsletter will be published once every month. Development status update ---------- BUGS 2 is shaping up to be a real winner. This last week we saw a boost in development, and next week will hopefully be just as productive. Unfortunately (?) we must also dedicate some time to work on the next 1.x release, 1.7.2, which will be released this month. As some of you noticed, we cleaned up many of the issues reported at our bug reporting site, http://bugs.c3pc.com/bugs/ . This gave us a good overview of where we're at, and allowed us to focus on a few forgotten issues. To those of you who haven't noticed yet, we have also provided a quick search link for "BUGS 2 feature requests" as well as a similar quick link to see fixed issues. These links will hopefully help you when you are looking to see if your favourite feature is suggested or not. It's not too late to suggest features for BUGS 2 yet! December relase: BUGS 1.7.2 ---------- As mentioned above, we will release an updated version of our succesful 1.7 series, this month. This release will introduce an updated "Force email notifications" setting, where users will receive emails even if they have not visited the bug - if this setting is turned on. This is great for projects with lazy users, or when you just forget it once in a while. Let us know how you like this feature. 1.7.2 will also feature fixes for recently reported bugs and issues. * Also notice that 1.7.2 will feature important security fixes * This release fixes important security issues, and is a highly recommended upgrade. BUGS 2 "new feature" highlight: Calendar(s) ---------- With big projects, it's nice to have some kind of timeline available. BUGS 2 will feature a calendar which will integrate nicely into the different project roadmaps and scheduled milestones. Calendar events can be planned, and shared with others, as well as public (and private) tasks. The new frontpage will inform you of scheduled tasks and calendar items. BONUS: For those of you who read this far, here is a picture that shows how far we're come with BUGS 2. While this is not the most revealing picture we've released, it's a sneak peek that shows of some of BUGS 2 new features. See it here: http://www.zegeniestudios.net/preview1.png Let us know what you think. Sincerely, - the BUGS team ---------- ( You are receiving this newsletter because you are subscribed to one of our mailing lists. If you don't want to receive this newsletter anymore, plese unsubscribe from all BUGS mailing lists. To do this, please visit http://bugs-bug-genie.sourceforge.net/ ) |
From: <ze...@ze...> - 2005-09-05 19:51:33
|
Welcome to the second BUGS newsletter! In this issue: * BUGS 2 development update - the B2 framework * Next release: BUGS 2 or BUGS 1.8? * Upgrading to BUGS 2 * BUGS 2 "new feature" highlight: Tasks The BUGS newsletter is a service we provide so you can easily stay up-to-date with the latest new information regarding "BUGS - the Bug Genie". The newsletter will be published once every month. BUGS 2 development update - the B2 framework ---------- We are still on course with our next major BUGS update. BUGS 2 (cleverly codenamed B2) will be our best release this far, but we have still got a long way to go. We are currently working on the framework for BUGS 2, which will allow us great flexibility when continuing the development. With BUGS 1, we had a "basic" web interface on top of a database structure, dependant on MySQL. With B2, we are looking at a complete framework rewrite. Actually a framework "write", since there never was much of a framework to begin with. With the B2 framework, we want to make it easy to expand the basic BUGS 2 functionality with independent modules, as well as making it easy for our users to make their own additions to BUGS 2. The B2 framework consists of functions and classes which you can include in your own modules, or simply call from your websites to interact with BUGS 2. This modular approach also allows us to support more than one database engine - a feature we know several users are looking forward to. More on the database engine support in Issue #3, by the way. The B2 frameworks also allows us to concentrate effort on module development, which in turn makes the whole system more reliable, and opens up for a whole lot of new possibilities. As you can easily tell, we're very excited about B2. Next release: BUGS 2 or BUGS 1.8? ---------- A lot of the feedback we've received lately has been about adding some kind of group system to BUGS 1.x, which makes us wonder if some of you would prefer if we dedicate time to work on that feature for BUGS 1.x, releasing BUGS 1.8 instead of using all our energy on developing B2 and BUGS 2. Spending more time on developing features for 1.x would probably delay the B2 development by a few months, something we'd prefer not to. We're still committed to BUGS 2 development, and will most likely not do anything but bugfix releases for 1.7.x. Upgrading to BUGS 2 ---------- "Will I be able to update to BUGS 2 from my current BUGS 1 installation?" is a question we've received more than just a few times. We are making every effort to make sure that upgrading from BUGS 1 to BUGS 2 will be as painless as possible, and we'll make sure that the upgrade routine is as easy and safe as it is today. Rest assured that BUGS 1 will be completely upgradeable! BUGS 2 "new feature" highlight: Tasks ---------- Last issue we talked about the new "User groups" feature, which will be introduced in B2. This month we're looking at another great new feature: Tasks. Tasks will allow you to delegate work between different groups easily. Tasks can be added to a bug report for completion before the bug can be marked as "fixed", but you can also have "independent tasks" which aren't connected to bug reports. Tasks can be assigned to groups, teams and/or users, and can have statuses and other attributes set. This feature also makes BUGS 2 viable as a "trouble ticket" system, making it even more versatile than it is today. Tasks is another feature we're very excited about! This last month has seen a lot of "brainstorming" activity surrounding BUGS 2 and B2 in general. Stay tuned for the next issue with even more exciting updates! Sincerely, - the BUGS team ---------- ( You are receiving this newsletter because you are subscribed to one of our mailing lists. If you don't want to receive this newsletter anymore, plese unsubscribe from all BUGS mailing lists. To do this, please visit http://bugs-bug-genie.sourceforge.net/ ) |
From: <ze...@ze...> - 2005-08-05 13:57:47
|
Welcome to the first BUGS newsletter! In this issue: * BUGS 2 on target for a Q1 2006 release * Introducing the core BUGS team * BUGS 2 "new feature" highlight: User groups The BUGS newsletter is a service we provide so you can easily stay up-to-date with the latest new information regarding "BUGS - the Bug Genie". The newsletter will be published once every month. BUGS 2 on target for a Q1 2006 release ----------- The BUGS team has finally settled down after the summer, and we are now working hard to get the basic framework up and running (The BUGS 2 framework will be further explained in Issue #2 of this newsletter). We are currently working on the standard framework functions, the public "API" calls, so we can increase the productivity later on in the process. BUGS 2 does not have a release date yet, but we are targetting a mid-Q1 2006 release. If you want to know more details, look for the roadmap in Issue #2 of this newsletter. The roadmap will also be posted at our new website, when it is up and running. Introducing the BUGS team ----------- The core BUGS team currently consists of three members: * Daniel Andre (zegenie), Project Leader * Ray (rrjen), Head of development * Kim Eric, Core development Every one of us is actively participating in the BUGS 2 development process, and we are all skilled at what we do. Kim Eric, who is the latest addition to our development team, has several years of experience in PHP, HTML, JavaScript and Commercial web design. To us, he's a great catch, and we're happy to have him onboard. The BUGS team are always happy to answer any questions you have - direct them to bug...@ze... . Ruffdogs ( http://www.ruffdogs.com ) is also able to assist in getting BUGS up and running within your company. Together, zegenie studios and Ruffdogs provide one of the best support solutions available. BUGS 2 "new feature" highlight: User groups ------------ One of the main shortcomings of BUGS "1" is the lack of a proper user group system. While we have a fairly sophisticated user group system, opening up for a wide range of roles, the system as it is today remains painfully limited. There is no way to customize roles, although you can select one of the 9 different built-in roles. BUGS 2 will also come with a predefined set of roles, but will give administrators and staff members the option to customize roles, create new user groups, and put members in more than one group, if desirable. The BUGS 2 user/groups system will be easily cinfigurable through a centralized control panel, much like the one you see in BUGS "1". All in all, these last few weeks have been good for the project, and we are looking forward to continue working on it, throughout the fall. Stay with us for more updates! Sincerely, - the BUGS team http://bugs-bug-genie.sourceforge.net -------- You are receiving this email because you signed up at one of our mailing lists. If you don't want to receive more emails from us, please visit http://bugs-bug-genie.sourceforge.net and remove yourself from the mailing list. |
From: Daniel A. E. <ze...@ze...> - 2005-08-04 02:13:29
|
Hi everyone! * BUGS 2 is now being actively developed, alongside our maintenance of the 1.7.x release branch. As previously mentioned, BUGS 1.7 was the latest point release in our 1.x release series, and we are now only providing hotfixes and security fixes to the 1.x series. Feel free to let us know if you find there are any important issues still not fixed in the 1.7.x version. As usual, you can reach us through our live BUGS installation located at http://bugs.c3pc.com/bugs/ , as well as email, bug...@ze... . BUGS 2 is under heavy development, and currently, the core section of the system is being developed, whereas the standard modules will be developed when the core system is complete. * BUGS Team expanded! We are happy to announce the addition of Kim Eric into our development team. Kim Eric will be joining the core development team, and will be doing module development, and user support. The BUGS development team is now Daniel Andre (zegenie), Ray (rrjen) and Kim Eric (detektstudios). (BUGS usernames in paranthesis). The translation team is also being expanded, and we are looking forward to adding you to the team. If you feel like contributing to BUGS 2 translation, email us at tra...@ze.... Remember to mention BUGS as your translation subject, since we are currently hosting multiple projects. Any and all questions as usually goes to ze...@ze... Until next time! - the BUGS Team |
From: <ze...@ze...> - 2005-06-29 00:18:15
|
Hi, everyone! IRC support now available! Following the release of our 1.7.1 version, we have now added another=20 support option for your convenience. The project developers can now be=20 met in our IRC support channel #bugs-bug-genie, hosted at the FreeNode=20 irc network. If you have any questions, comments or just feel like=20 dropping by, join #bugs-bug-genie at one of the freenode.net irc=20 servers. If you don't have an IRC client available, you can also join=20 #bugs-bug-genie from the webchat available at http://www.guilinux.com If we are not around, feel free to leave a message, and one of us will=20 try and answer it as soon as possible. There are also talented=20 individuals, with experience from BUGS available at #guilinux, in case=20 our support channel should be empty. Our website is getting a facelift! We are trying to upgrade our website look and feel, to reflect the=20 upcoming changes. We will have less time available maintaining the new=20 website, so at least we want it to look good and provide much=20 information while our development team focuses on bringing v2 into=20 reality. We will introduce the new website sometime during summer, when=20 our developers are getting ready and settled. Thanks for listening! --=20 Sincerely, Daniel Andr=E9 Eikeland Project leader, "BUGS - the Bug Genie" http://bugs-bug-genie.sourceforge.net |
From: <ze...@ze...> - 2005-05-10 02:04:26
|
Everyone! Today marks a major milestone. After two years of active "BUGS"=20 development, we have finally released our last and latest 1.x version,=20 "BUGS" 1.7! Initially available in English and Norwegian, this is our latest and=20 greatest release, which we are proud to bring you! You can get the=20 release from our website at : http://bugs-bug-genie.sourceforge.net/ Key new features includes: * Localization (English and Norwegian initially available) * PM System (Private messaging) * Improved, enhanced report generation * Vastly improved administration interface for=20 products/editions/builds, including the ability to set=20 products/editions/builds as "default" selection, server-wide and=20 user-selectable. * Guest account * New fields available: "Elapsed time", "Estimated time" and "Percent=20 completed" * Improved privacy options ...along with a bunch of speed and stability improvements... All users are encouraged to update to this new version. Feel free to send us your comments and ideas! --=20 Sincerely, Daniel Andr=E9 Eikeland Project leader, "BUGS - the Bug Genie" http://bugs-bug-genie.sourceforge.net |
From: <ze...@ze...> - 2005-05-04 00:35:54
|
Hi everyone. We needed to implement some last minute features and fixes for the=20 upcoming 1.7 version, hence the delay in the release. The last minute=20 changes included: * Some minor bug fixes * Opera 8 + KHTML (Safari, konqueror) rendering errors * Minor feature updates / additions * Enhanced email localization: You can now add any %variable% to the email template, giving you=20 much, much greater control of the email notifications. The variables=20 should be self-explaning, and are: subject: %bug_id% %bug_title% =20 message: %bug_id% %bug_title% %bug_link% %app_name% %pct_complete% %user_uname% (assigned) %user_realname% (assigned) %dup_bug% (Duplicate bug number - returns '0' if not set) %bug_desc% - bug long description %bug_status% %bug_sev% %bug_prio% %bug_cat% %bug_milestone% %bug_comment% %bug_link% %bug_dup_link% This last code-a-thon has delayed the release a bit, but seeing as this=20 will most likely be the last 1.x release, we wanted to make this release=20 as solid as possible. All changes are commited to CVS, but will not be=20 released as an RC. Please watch this space for release information. Thanks! --=20 Sincerely, Daniel Andr=E9 Eikeland Project leader, "BUGS - the Bug Genie" http://bugs-bug-genie.sourceforge.net |
From: Daniel A. <ze...@ze...> - 2005-04-21 16:25:16
|
Hi everyone. We are now in the final stages of wrapping up the upcoming BUGS 1.7. We are very excited about this release and want to get it released as soon as possible. We are trying to fix the few remaining issues and bugs, and would very much appreciate any and all feedback from everyone who has downloaded the betas or release candidates. Thanks in advance. Oh, and all comments and feedback to zegenie AT zegeniestudios DOT net, please. -- Sincerely, Daniel Andre Eikeland Project leader, "BUGS - the Bug Genie" http://bugs-bug-genie.sourceforge.net |
From: Danny A. C. G. <da...@bi...> - 2005-04-06 16:34:00
|
Hi, It will be nice to provide diffs from builds.. as phpBB does. And a list of changed files in that build. This is easy for ppl like me that run a changed version. My version has auth done by the main site and db, and I have added a 'platform' property (I dont know if 1.7 has something like this.. mine is 1.4, but I want to upgrade soon.) Thanks -- Danny Angelo Carminati Grein Project Manager Bitcrafters Inc. http://www.bitcrafters.com.br |
From: Mike W. <pe...@gm...> - 2005-04-06 04:27:35
|
Here is some data on the switch example: Time for elseif: 4.5061111450195E-005 Time for switch: 1.4066696166992E-005 I put in 11 different numbers sorry for all this white space... But the results are almost idential even when $task = ""; if ($task != ""){ if ($task == 1){ print "1"; } elseif ($task == 2){ print "2"; } elseif ($task == 3){ print "3"; } elseif ($task == 4){ print "4"; } elseif ($task == 5){ print "5"; } elseif ($task == 6){ print "6"; } elseif ($task == 7){ print "7"; } elseif ($task == 8){ print "8"; } elseif ($task == 9){ print "9"; } elseif ($task == 10){ print "10"; } elseif ($task == 11){ print "11"; } } And a switch statement: switch($task) { case 1: print "1"; break; case 2: print "2"; break; case 3: print "3"; break; case 4: print "4"; break; case 5: print "5"; break; case 6: print "6"; break; case 7: print "7"; break; case 8: print "8"; break; case 9: print "9"; break; case 10: print "10"; break; case 11: print "11"; break; } > Some of it is fairly simple.... > > instead of if () {} elseif () {} elseif () {} you can use a switch > which is more maintainable and also faster in parcing since its not > having to check so much items... > > take for instance the $task in the admin.php file, now you do not need > a if ($task="") {...} as well because if its not in the switch it wont > even render thus dropping a few lines of code as well as maintaining > more readable and also quicker code since it is not doing so many > checks for each elseif. It actually is running like the following: > if ($something) { ... } else { if () { } else { if () { } } as you > can see pretty inefficent where as a case just simply follows down the > line. Then the most used go at the top making it extremely quick. > > switch($task) { > case 'cats': > break; > case 'othersection: > break; > } > > also with the print function being rendered on everyline you are > wasting quite sometime giving php the command to print where as > print "me"; > print "this"; > > could be (notice the . ): > print "me" . > "this"; > > Here is the results of doing a small test on 20 lines with just print > "something"; and then using my style with the same output: > Time for prints: 4.7922134399414E-005 > Time for appends: 2.3126602172852E-005 > > This is in microtype by the way :) > > I will add more later I have been trying to find my way to fix the > admin category bug of not showing any categories but I am still a > little unfamiliar with how this code base is other than the main files > so I have to take a peak into it somemore as I only had around 30 > minutes early to start. > > Mike > >> Hi, Mike. >> >> Thanks for posting your thoughts and comments. Could you explain how >> things could be speeded up with our current code? We most definately >> wouldn't mind doing a 1.7.x release with code improvements, but being >> the person I am, I'd like to learn more about how these things are >> speeded up. Please tell us more. >> >> Oh, and please reply to the mailing list - that way, we all benefit >> from your answers. >> >> Thanks! >> >> Mike Willbanks wrote: >> >>> Hey guys, >>> >>> I would like to say hello to you all and give thanks for creating this >>> software. >>> >>> However I would like to help smooth out some of the code and also help >>> out a bit. I was looking at the source in the 1.6 release and some of >>> the coding practices aren't quite where they should be. For instance >>> all of the else if() {} blocks and the print statements on each line. >>> >>> Just this alone would make a major increase in the speed of the >>> program. >>> So if 1.7 is the last planned release on the 1.x build I would >>> suggest >>> maybe making a 1.7.x build with some code revamping. >>> >>> >>> Mike >> >> > > |
From: Mike W. <pe...@gm...> - 2005-04-06 03:53:17
|
Some of it is fairly simple.... instead of if () {} elseif () {} elseif () {} you can use a switch which is more maintainable and also faster in parcing since its not having to check so much items... take for instance the $task in the admin.php file, now you do not need a if ($task="") {...} as well because if its not in the switch it wont even render thus dropping a few lines of code as well as maintaining more readable and also quicker code since it is not doing so many checks for each elseif. It actually is running like the following: if ($something) { ... } else { if () { } else { if () { } } as you can see pretty inefficent where as a case just simply follows down the line. Then the most used go at the top making it extremely quick. switch($task) { case 'cats': break; case 'othersection: break; } also with the print function being rendered on everyline you are wasting quite sometime giving php the command to print where as print "me"; print "this"; could be (notice the . ): print "me" . "this"; Here is the results of doing a small test on 20 lines with just print "something"; and then using my style with the same output: Time for prints: 4.7922134399414E-005 Time for appends: 2.3126602172852E-005 This is in microtype by the way :) I will add more later I have been trying to find my way to fix the admin category bug of not showing any categories but I am still a little unfamiliar with how this code base is other than the main files so I have to take a peak into it somemore as I only had around 30 minutes early to start. Mike > Hi, Mike. > > Thanks for posting your thoughts and comments. Could you explain how > things could be speeded up with our current code? We most definately > wouldn't mind doing a 1.7.x release with code improvements, but being > the person I am, I'd like to learn more about how these things are > speeded up. Please tell us more. > > Oh, and please reply to the mailing list - that way, we all benefit > from your answers. > > Thanks! > > Mike Willbanks wrote: > >> Hey guys, >> >> I would like to say hello to you all and give thanks for creating this >> software. >> >> However I would like to help smooth out some of the code and also help >> out a bit. I was looking at the source in the 1.6 release and some of >> the coding practices aren't quite where they should be. For instance >> all of the else if() {} blocks and the print statements on each line. >> >> Just this alone would make a major increase in the speed of the program. >> So if 1.7 is the last planned release on the 1.x build I would suggest >> maybe making a 1.7.x build with some code revamping. >> >> >> Mike > |
From: zegenie <ze...@ya...> - 2005-04-05 22:07:35
|
Hi, Mike. Thanks for posting your thoughts and comments. Could you explain how things could be speeded up with our current code? We most definately wouldn't mind doing a 1.7.x release with code improvements, but being the person I am, I'd like to learn more about how these things are speeded up. Please tell us more. Oh, and please reply to the mailing list - that way, we all benefit from your answers. Thanks! Mike Willbanks wrote: > Hey guys, > > I would like to say hello to you all and give thanks for creating this > software. > > However I would like to help smooth out some of the code and also help > out a bit. I was looking at the source in the 1.6 release and some of > the coding practices aren't quite where they should be. For instance > all of the else if() {} blocks and the print statements on each line. > > Just this alone would make a major increase in the speed of the program. > So if 1.7 is the last planned release on the 1.x build I would suggest > maybe making a 1.7.x build with some code revamping. > > > Mike > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Bugs-bug-genie-developers mailing list > Bug...@li... > https://lists.sourceforge.net/lists/listinfo/bugs-bug-genie-developers > |
From: Mike W. <pe...@gm...> - 2005-04-05 19:56:56
|
Hey guys, I would like to say hello to you all and give thanks for creating this software. However I would like to help smooth out some of the code and also help out a bit. I was looking at the source in the 1.6 release and some of the coding practices aren't quite where they should be. For instance all of the else if() {} blocks and the print statements on each line. Just this alone would make a major increase in the speed of the program. So if 1.7 is the last planned release on the 1.x build I would suggest maybe making a 1.7.x build with some code revamping. Mike |
From: Mike W. <mi...@di...> - 2005-04-05 19:54:53
|
Hey guys, I would like to say hello to you all and give thanks for creating this software. However I would like to help smooth out some of the code and also help out a bit. I was looking at the source in the 1.6 release and some of the coding practices aren't quite where they should be. For instance all of the else if() {} blocks and the print statements on each line. Just this alone would make a major increase in the speed of the program. So if 1.7 is the last planned release on the 1.x build I would suggest maybe making a 1.7.x build with some code revamping. Mike |
From: <ze...@ze...> - 2005-04-05 12:07:44
|
Hi, everyone! We're now very close to releasing 1.7, our last release in the 1.x=20 series. We've uploaded the RC1 of BUGS 1.7, available from our website=20 at http://bugs-bug-genie.sourceforge.net . Please test this version and help us iron out the last remaining issues!=20 If no serious issues are found, this will be the last beta / rc before=20 the release of 1.7. Thanks! --=20 Sincerely, Daniel Andr=E9 Eikeland Project leader, "BUGS - the Bug Genie" http://bugs-bug-genie.sourceforge.net |
From: Danny A. C. G. <da...@bi...> - 2005-03-09 20:43:19
|
Is there any planned feature or something to indicate what platform the bug occur for the given version/build? I implemented this for 1.4 here.. but I want to know if there is any or is in planning on next releases? thanks -- Danny Angelo Carminati Grein IT Manager Bitcrafters Inc. http://www.bitcrafters.com.br |
From: <ze...@ze...> - 2005-03-09 00:40:54
|
Hi again, everyone! Tonight, we released beta 2 of our upcoming 1.7 release. We've fixed all=20 bugs reported since the first beta, and we've added all the features=20 scheduled for 1.7, as well as a few last minute changes (thanks to=20 "bizzo" and "mck"). The language file was also updated with about 20-25=20 changes (compared to 1800 lines, that's relatively few ;) ), but those=20 who should know that, the translation team, has already been notified.=20 We will hopefully have a at least a few high quality translations by the=20 time we release 1.7. Please test the new beta by following the link provided at our=20 sourceforge.net website. Thank you! --=20 Sincerely, Daniel Andr=E9 Eikeland Project leader, "BUGS - the Bug Genie" http://bugs-bug-genie.sourceforge.net |
From: <ze...@ze...> - 2005-03-01 01:23:35
|
Hi, everyone! BUGS - The Bug Genie 1.7 is now available from our website. You can=20 download it by accessing the download page, located at=20 http://bugs-bug-genie.sourceforge.net/dwnld1.php This version is fully localized and incorporates all the recent changes,=20 and planned features for version 1.7. Please feel free to report all=20 your comments and suggestions either to this mailing list, zegenie AT=20 zegeniestudios DOT net, or (preferrably) in our bug tracker, located at=20 http://bugs.c3pc.com/bugs/ Please test this version as thoroughly as possible! Thanks! --=20 Sincerely, Daniel Andr=E9 Eikeland Project leader, "BUGS - the Bug Genie" http://bugs-bug-genie.sourceforge.net |
From:
<ze...@ze...> - 2005-01-12 01:37:00
|
Everyone! Localization of the upcoming BUGS 1.7 is now completed - a manual=20 proof-reading, editing and translation of about 26,000 lines of code=20 (give or take a few hundred). If you would like to help out translating the sample file into another=20 language, please let me know within the end of the week. Release=20 candidates will be released to the public within friday. Any translated language files that are received before the official=20 release will be included, and the translator(s) will be credited. If=20 anyone is able to translate from norwegian to english (very fast), that would be great, as well. Thank you. --=20 Sincerely, Daniel Andr=E9 Eikeland Project leader, "BUGS - The Bug Genie" http://bugs-bug-genie.sourceforge.net |
From:
<ze...@ze...> - 2005-01-02 23:29:12
|
Hi! Due to the sheer amount of work required to get 1.7 up and running with its planned features, we have found it necessary to postpone the release of 1.7 to mid-/late January. The planned features will all be in there, and maybe some other goodies, but some more testing and (most of all) coding is needed until it is complete. If anyone wants to chip in, let me know at ze...@ze... :) If you've got any questions, direct them to the email address above, or to this mailing list. Thanks. -the BUGS team |
From: Renat L. <rl...@ge...> - 2004-09-22 16:08:12
|
Folks, Just a quick note to let you know that BUGS is now available through Gentoo= Portage. Please consider mentioning this on your website. Best, --=20 Renat Lumpau Gentoo developer GPG key id #C6A838DA on http://pgp.mit.edu Key fingerprint =3D 04AF B5EE 17CB 1000 DDA5 D3FC 1338 ADC2 C6A8 38DA |
From: <rr...@us...> - 2004-09-13 13:31:31
|
Hi all! To get the latest reported bugs and requests available to everyone as fast as possible, we are splitting the 1.6 release in two, making all fixes and implemented new features into a 1.6 release, and postponing the brand new 'View reported bugs' page (where users can create and save own Quick Links and Layouts) to a 1.7 release. As the 1.7 release still are scheduled this year, it shouldn't take too long to get all the planned new features implemented. Meanwhile we will continue to include any needed new fixes or requests together with the planned changes. The 1.6 BETA2 are planned to be available from our Home Page late this week. Hopefully this split will please many of our users waiting for the fixes and implemented features. the BUGS Team |
From: <rr...@us...> - 2004-07-13 15:34:04
|
Faster and more secure then ever and with better theme and stylesheet support... Try the latest beta version and give some feedback before the final release. Download from our home page http://bugs-bug-genie.sourceforge.net or try out our upgraded online reporting database from http://bugs-bug-genie.sourceforge.net/bugs/ (sf.net home pages are currently a bit slow if using MySQL database, but...) the BUGS Team |