SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264
|Anonymous | Login||2020-02-26 22:22 UTC|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000779||Endian Firewall||GUI||public||2008-05-09 23:18||2009-06-09 17:08|
|Priority||low||Severity||feature||Reproducibility||have not tried|
|Target Version||future||Fixed in Version|
|Summary||0000779: implement hardware information tool|
|Description||implement tool which allows the user to send us hardware information in order to enable us to build a hardware compatibility matrix|
|Tags||No tags attached.|
|since version 2.2 is already so far behind schedule why not rather push this feature into a 2.2.1 or 2.3 version, as it is a new feature and not a bug fix?|
because we need that information in order to build a hardware compatibility matrix.
There are plenty of people (i suppose) which would upgrade to 2.2 as soon as it will be released. We would loose potential information if we would put this tool into a 2.2.1.
It's however lacking only the gui part, so it's not that effort.
Thank you for the advice
This is an interesting situation!
one of the biggest issues I have noticed with Endian is the slow release of new versions and only the commercial version getting the upgrades released regularly, this appears to bother a few people not just me :)
The hardware information tool makes sense and I agree would help build a list of compatible hardware maybe help with testing etc. but you are only going to get the full benefit if you release this to the open source guys as they are probably the majority of the guys running on all weird and wonderful pieces of hardware, and like you mentioned the sooner you get it out there the more information you will get.
Yet this issue was opened in May 2008 its now 9 months later and it still has not been released and if by measuring against the progress of the roadmap, it’s probably going to be another 9 months before it is released, just think about all that information you are going to loos?
Why not simple release regular patches/updated/versions to the open source community and reap the benefits?
|2008-05-09 23:18||peter-endian||New Issue|
|2008-05-19 14:02||peter-endian||Status||new => assigned|
|2008-05-19 14:02||peter-endian||Assigned To||=> simon-endian|
|2008-06-03 10:06||peter-endian||Target Version||2.2 => 2.2-rc2|
|2008-06-25 13:52||raphael-endian||Priority||normal => immediate|
|2008-07-10 18:51||peter-endian||Priority||immediate => normal|
|2008-07-24 16:05||ra-endian||Target Version||2.2-rc2 => 2.2-rc3|
|2008-07-28 08:57||peter-endian||Target Version||2.2-rc3 => 2.2|
|2008-08-11 07:55||steven||Note Added: 0001515|
|2008-08-11 09:01||peter-endian||Note Added: 0001516|
|2008-09-10 15:41||chris-endian||Target Version||2.2 => 2.3|
|2009-02-19 19:46||steven||Note Added: 0001985|
|2009-02-26 11:39||peter-endian||Priority||normal => low|
|2009-06-09 17:08||peter-endian||Target Version||2.3 => future|
|Copyright © 2000 - 2012 MantisBT Group|