B
- although option A sounds better but ...
> (A) Deprecate DOM parser then release 0.9
What shall deprecation exactly mean? Move/swap classes?
SiteMapParser -> SiteMapParserDOM @Deprecated
SiteMapParserSAX -> SiteMapParser
SiteMapParserSAX extends the DOM-based SiteMapParser, we can hardly deprecate SiteMapParser.
I've checked whether SiteMapParser and SiteMapParserSAX are in sync and
opened #180 (normalize the RSS pubDate). Flagged as "milestone 0.9":
should get into the release for both A and B.
> Visit this group at https://groups.google.com/group/crawler-commons.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "crawler-commons" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crawler-commons+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/crawler-commons.
For more options, visit https://groups.google.com/d/optout.
On Oct 18, 2017, at 2:24 AM, Julien Nioche <lists.dig...@gmail.com> wrote:Hi,We don't have any open issues flagged for 0.9 and we have recently added some nice improvements, which I think we should release ASAP.There is a discussion in #177 about removing the DOM based sitemap parsing, we could do that in 0.9 or deprecate it for now and postpone its removal.Please vote between:(A) Deprecate DOM parser then release 0.9(B) Remove DOM parser then release 0.9(C) Don't release 0.9 yet - please explain whyThanks!Julien
--
You received this message because you are subscribed to the Google Groups "crawler-commons" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crawler-commons+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/crawler-commons.
For more options, visit https://groups.google.com/d/optout.