[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jwt-dev] JWT release

The problem occurs with these files whatever the way we call the
Converter (be it in the tests or simply in WE). I think this bug has
been around for quite a long time, so in my opinion there's no need to
hurry and try to fix it so close to the release. And as you said, it's
unlikely it will affect anyone. So if you're OK with it, let's ship JWT
"as is" :)

Ok, thanks. I'll run the build and publish the final version then.

About the "version" attribute of this bug, though, I think we'll need to
discuss a little the way we use it. It seems it's been used as a
"milestone" attribute until now, i.e. to mark the version "in which the
bug should be fixed", whereas it appears its purpose is to mark the
version "in which the bug is known to occur".
For the 1.2.0 release, though, Marc created some milestones, and we
started using the milestone attribute. So the current status of this bug
is OK: no milestone is set, which means we don't know (yet) when it will
be fixed.

Good observation, I didn't realize that. Then let's do it the way it's supposed to be done in the future :)


Regards,
Chris

Le jeu. 31 mai 2012 11:10:43 CEST, Christian Saad a Ãcrit :
Hi Yoann,

thanks for the work on the outstanding bugs! I understand there is a
problem with the converter handling the 0.6.0 to 0.7.0
transformations. As far as I remember, this particular transformation
is more complicated than others because of major changes in the file
format.

Is this a problem that generally occurs with these files or is it only
a problem with the tests? If the handling works in the normal case I
would suggest moving the bug to the next version. Otherwise we need to
decide on whether this bug can be fixed in the remaining time or if we
should ship JWT with this known defect. Honestly, I don't think there
are any old JWT 0.6.0 files around in any case.

Regards,
Chris