Re: Closing open bugs by end of week?

On Wed, Oct 8, 2014 at 8:06 AM, GALINDO Virginie <
Virginie.Galindo@gemalto.com> wrote:

>  Yeap, Mark, clear, lets keep bugzilla thread, as long as bugs are live
> and make progress J
>
> What about the serie of linked bugs, like error management ?
>

​Typically, if noone comments, I try to make a series of increasingly
concrete suggestions to provoke any objections and then go ahead if there
are none. This pre-supposes people are actually watching the bug updates on
the list, which since our agreed mode of working is on-list is reasonable,
I think.

On that one, seems like we should convert everything that might possibly be
handled by a library to OperationError.

...Mark​




>  Virginie
>
>
>
> *From:* Mark Watson [mailto:watsonm@netflix.com]
> *Sent:* mercredi 8 octobre 2014 17:07
> *To:* GALINDO Virginie
> *Cc:* Harry Halpin; public-webcrypto@w3.org
> *Subject:* Re: Closing open bugs by end of week?
>
>
>
>
>
>
>
> On Wed, Oct 8, 2014 at 7:56 AM, GALINDO Virginie <
> Virginie.Galindo@gemalto.com> wrote:
>
> Mark,
>
> Thanks for your work provided in following bug status.
>
> Let’s open thread on the mailing list for the ones requiring discussions.
>
>
>
> ​I think the necessary discussions are ongoing on bugzilla. MIght be best
> to keep them there to avoid parallel threads on the same topic.
>
>
>
> ...Mark​
>
>
>
>
>
>  Regards,
>
> Virginie
>
>
>
>
>
> *From:* Mark Watson [mailto:watsonm@netflix.com]
> *Sent:* mardi 7 octobre 2014 17:02
> *To:* Harry Halpin
> *Cc:* GALINDO Virginie; public-webcrypto@w3.org
> *Subject:* Re: Closing open bugs by end of week?
>
>
>
> Harry, all,
>
>
>
> I added a new tab, 10/7, to the spreadsheet at
> https://docs.google.com/spreadsheets/d/1rpc7Q7o4nxoKjYT8Qx4MhueQ-rUuIIM53yp7miUuxnw/edit?usp=sharing
>
>
>
> This gives the current bug status.
>
>
>
> There are only 2 which are truly editorial and one of those relates to
> references which could be fixed with the pubrules fixes after we have made
> a decision.
>
>
>
> There are several others which are pending discussion, but which I do not
> believe should delay exit from Last Call - they are in many cases the kind
> of things that might normally be discovered during the implementation
> phase, which is typically after CR. We have delayed our specification so
> much that several implementations are complete before the "call for
> implementations", so we have implementation feedback already [I don't
> consider this as getting feedback early in the W3C process but rather that
> the W3C process has got way way behind.]
>
>
>
> To exit Last Call I believe it is primarily the extensibility issue we
> need to resolve.
>
>
>
> ...Mark
>
>
>
> On Tue, Oct 7, 2014 at 6:06 AM, Harry Halpin <hhalpin@w3.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 10/07/2014 03:01 PM, GALINDO Virginie wrote:
> > Harry, Quick clarification : as indicated last week, our next
> > meeting is on *20th of October*.
>
> Regardless, we'd need all open bugs that are editorial *closed* by the
> 13th to give the WG time to review, in particlar if there are various
> decisions.
>
>   cheers,
>      harry
>
>
>
> > This does not prevent us to be ready for next Friday, indeed.
> > Virginie
> >
> > -----Original Message----- From: Harry Halpin
> > [mailto:hhalpin@w3.org] Sent: mardi 7 octobre 2014 14:39 To:
> > public-webcrypto@w3.org Subject: Closing open bugs by end of week?
> >
> > Solving remaining bugs:
> >
> > We *really* need to go to Last Call ASAP. Our next meeting is Oct.
> > 13th. Or do we need another week extension?
> >
> > Here's the list:
> >
> https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Web%20Cryptography%20API%20Document&product=Web%20Cryptography&query_format=advanced
> >
> >  Mark or Ryan - do either of you have time to go through the bugs
> > that are still open and do the editorial commits needed to close
> > them?
> >
> > Then, the Working Group still probably isn't quite sure exactly
> > what bugs it needs to review due to substantial open issues and
> > which ones are minor nit-picks.
> >
> > For example, there's a few bugs left hanging like this one:
> >
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=25198
> >
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=25706
> >
> > I suggest just at least editor just making the changes ASAP even if
> > editors do not yet agree (although ideally they agree) and then
> > giving everyone time to review.
> >
> > cheers, harry
> >
> > ________________________________ This message and any attachments
> > are intended solely for the addressees and may contain confidential
> > information. Any unauthorized use or disclosure, either whole or
> > partial, is prohibited. E-mails are susceptible to alteration. Our
> > company shall not be liable for the message if altered, changed or
> > falsified. If you are not the intended recipient of this message,
> > please delete it and notify the sender. Although all reasonable
> > efforts have been made to keep this transmission free from viruses,
> > the sender will not be liable for damages caused by a transmitted
> > virus.
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQIcBAEBAgAGBQJUM+U4AAoJEPgwUoSfMzqcZ1YQAJ2IF19uYhbOxDgX7VsPM0bx
> uZs2xozBqfXUsry7fM+tTb1QRuClQqPMmN5FlcfnNjF9UclefJZsV+zMzhKUn8q7
> jK8Tw4RSNv6eKJZyrG02k8/7vk2zVGFLhlw5fA6PU/+mo4qLcXWgIg8z59KODzuZ
> 0KAuz3Xh6Byxg236hqGSryXr5T4OHMS71m48vXy5s4sG4a2oCXA14up4lKRyT36F
> rbGNMAAefIH6YvX6XAMASk3pKtZo4c1N4CM0QKSUZzWdQpQ62WfxTFbsrVZY7zss
> H7WHUmkrmTrPgsa5YAEpFj6KEHGR6Rl11s+8rIK80+4YYFb/UNwJQkICfePLAN/I
> ggsmb2AKs9Nd2jeIRH1RvDzcTn3/rIrtwZAH5uFSnOTQajYhiBZY5phXn2w6Ik/I
> PUGTMyaTO4gpKC8gUF7Iv/278kpclKoQEj0fGUYnzfDJj5mU8hfwlXvkcjGmt+0R
> nMBBMoFwFBQ1OMqjaHeBAwCaO4xrEV1Tdvhye7tV0FM/SkSKBTI1z5lQ1PJksEUp
> ZGP6jAHRdtvBDMpxy7n1z6y4XLu+rqnMYsjhn6cAdrj8QS5Q5KPf2DVVlbMVSMYf
> LQSQxZr9S7Za9ktt+n5HWlSpFRTPYjk+8cjbqon0bFhHaGNLg93KI4Usd0mZXKjk
> TMQhA2bCwf3fYPFCdBEK
> =U0me
> -----END PGP SIGNATURE-----
>
>
>     ------------------------------
>
>
>
> *This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited. E-mails are susceptible
> to alteration. Our company shall not be liable for the message if altered,
> changed or falsified. If you are not the intended recipient of this
> message, please delete it and notify the sender. Although all reasonable
> efforts have been made to keep this transmission free from viruses, the
> sender will not be liable for damages caused by a transmitted virus.*
>
>
>   ------------------------------
> This message and any attachments are intended solely for the addressees
> and may contain confidential information. Any unauthorized use or
> disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for
> the message if altered, changed or falsified. If you are not the intended
> recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
>