>As I said above, the bugs are already marked accordingly.
>Let's not introduce another rating on the Wiki. Everyone
>who is not content with a bug's severity can change it on
>the bug tracker page. However, please be very cautious
>with this. If every bug ends up being rated "block",
>then we will not be able to set priorities for the release!
My intention is to put a list of known (important) bugs/problems easily
accessible for everyone so that new contributors could read them promptly.
Something similar like here http://oadigital.net/software/gvsigoade/gvsigbugs
But we can go on as you suggested below if we get the same goal.
>The bug tracker also has the ability to automatically
>create a release plan for gvSIG CE 1.0:
>http://gvsigce.sourceforge.net/mantis/roadmap_page.php
>Every bug which is marked with "gvSIG CE 1.0" as "Target version"
>will automatically be listed there. I suggest linking to
>that page from the wiki directly, instead of creating another
>resource that needs to be kept up-to-date.
+1. Is it possible to see the content of this link without being asked for
username and password?
>I have added a new release target called "unspecified".
>Everyone wishing to sort out the release of gvSIG CE 1.0
>can help in one of these ways, using the bug tracker:
> ...
I will start with this ASAP.
Cheers!
Jose
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Gvsigce-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gvsigce-community
