I am not sure we have come up with an agreeable way to manage the "Fix 
Version" information; personally I only check that value when I am 
fixing a bug and use it to track on which branches the patch has been 
applied.

We could also use it for scheduling, and we do infact do that when we 
get near the "release candidate stage", only then do we start cutting 
down the list of bugs specifically to what is required for the release 
to go out.

You can totally set the "Fix Version" information to unknown.
Jody

Martin Desruisseaux wrote:
> The same pattern seems to occur again and again at every GeoTools releases: 
> we 
> setup most JIRA tasks to the next GeoTools version with absolutly no intend 
> to 
> work on it in that time frame, and when that release occurs we just push up 
> every "Fix Version/s" to the next GeoTools version with no more intend to 
> work 
> on it.
>
> It seems misleading to me, almost dishonet toward our users. Why should taks 
> like that ones:
>
>    - Replace HSQL database by H2 for EPSG factory
>    - Add CRS:1 and CRS:88 authority codes
>    - MapProjection: relax coordinate checks/make them configurable
>
> and the like be targeted for 2.4.4 when I'm absolutly sure that I will never 
> have the time to work on them in that time frame? A user could believe that 
> if 
> he wait for GeoTools 2.4.4 he has reasonable chances to see those tasks 
> fixed, 
> which is false as far as I'm concerned.
>
> I remember that an argument told in the past was that tasks without "Fix 
> Versions/s" fall in black holes. As far as I'm concerned, I do not forget 
> tasks 
> I'm assigned to. Putting everything to the next GeoTools version defeat the 
> purpose of "Fix Versions/s" - this information became totally useless to me 
> since I know they are all wrongs (at least for the tasks I'm assigned to).
>
> Can I set the "Fix Versions/s" of some tasks I'm assigned to as "unknown" 
> (which 
> is the reality) and can we leave them like that? I would like to set a "Fix 
> Versions" only to the tasks I believe I may work on in the near future, in 
> order 
> to give some value to this information. Currently it has absolutly no value.
>
>       Martin
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft 
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Geotools-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to