Re: [HTTPS-Everywhere] Draft specification for file used to check for ruleset updates

2014-06-11 Thread Maxim Nazarenko
On 10 June 2014 18:39, Red wrote: > > > On 2014-06-10, 7:05 AM, Maxim Nazarenko wrote: > >I suspect we might use machine-readable date format (like MMDD) to keep the corresponding code cleaner, since it is mostly internal anyway. > > Yan has been talking about using subversions of the extensio

Re: [HTTPS-Everywhere] Draft specification for file used to check for ruleset updates

2014-06-11 Thread Maxim Nazarenko
On 10 June 2014 18:47, Red wrote: > The subject of the db_version field was discussed at length in last week's IRC meeting. The conclusion of the conversation was that it would be too much to expect developers to remember to bump the value of the preference in the extension every time such a chan

Re: [HTTPS-Everywhere] Draft specification for file used to check for ruleset updates

2014-06-11 Thread Red
On 2014-06-10, 6:27 PM, Yan Zhu wrote: > On 06/10/2014 01:40 PM, Jacob Hoffman-Andrews wrote: >> How about just sticking to the format we have now for update.json and >> going with the decision to serve multiple versions from different URLs >> depending on the release type? >> >> >> Th