From: Matthew C. <mat...@gm...> - 2011-06-27 20:58:35
|
Of course. Except for quoted strings, refactoring errors are all caught by the compiler. I've made sure to check the quoted strings. I don't think there's a problem releasing 3.0 before the paper, is there? Whereas holding up the paper due to the software not being ready would be a problem. I really need to get MyriMatch updated and using the refactored IdentData is one of the things I wanted to get in. I suppose we could just leave the version where it is and only bump it when the paper is submitted(accepted?). That'd be kind of awkward though. :) -Matt On 6/27/2011 2:35 PM, Parag Mallick wrote: > Hiya, > > Please do make sure that the various idConverters and idcat, etc. don't get broken with the switch. Also - we should try to time pwiz 3.0 with the submission of the paper. I should be circulating a draft in the next few days. It will need significant input, especially with regards to the supplemental bits, from the peeps on the list. > > Thx. > ~ Parag M ~ > > > > On Jun 27, 2011, at 12:27 PM, Matthew Chambers wrote: > >> Hi all, >> >> A while ago Rob and I discussed improving the naming scheme for mziddata: the namespace (mziddata), >> directory (mziddata) and the main type (MzIdentML) are confusingly inconsistent and do not match >> MSData (located in msdata for directory and namespace). We agreed on identdata and IdentData as the >> new name/location. >> >> I'm thinking of releasing the result (refactored mzIdentML 1.1 which is now in the public review >> phase) as pwiz 3.0. >> >> This is a heads up since it'll break client code. Since I'm not aware of any clients other than >> Bumbershoot at the moment, I'm not too concerned. >> >> -Matt |