Martin Desruisseaux ha scritto: > 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.
I agree with you on how a user may feel. Yet experience tells me that if an issue does not get scheduled for a release, it won't be fixed, ever. This thing of moving issues forward is also made a lot stronger by timed releases, since nobody tries to figure out what needs to be fixed for what release, but it just happens that what's urgent for some devs gets fixed, and everything else is not. This is happening with GeoServer too. So I'm not sure what the best course of action will be... in any case, for issues that are assigned to you, you're definitely free to modify the "fix for" to whatever you feel it's most appropriate, you are the maintainer of those modules, if anybody thinks of complaining because you modified the "fix for" field, ask them for a patch ;) Cheers Andrea ------------------------------------------------------------------------- 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
