<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br>Jachym: thanks for the comments. Yes, I think WMS 1.3.0 and deeper WFS 2.0 would certainly result in OWSLib 1.0.0. I will send out another thread for github and OSGeo mailing list migration.<br><br><div><div id="SkyDrivePlaceholder"></div>> Date: Sun, 17 Jun 2012 21:46:38 +0200<br>> From: jachym.cepicky@gmail.com<br>> To: tomkralidis@hotmail.com<br>> CC: owslib-devel@lists.sourceforge.net<br>> Subject: Re: [owslib-devel] moving towards next release<br>> <br>> Hi,<br>> <br>> I generally thing owslib 1.0.0 means something like "all used OGC<br>> standards are supported". This implies to me e.g. wms 1.3.0 as "must<br>> have" feature. WFS 2.0 will be hard work...<br>> <br>> Even I agree, we should focus on the 1.0.0 release, I think, at least<br>> one or two 0.X release will be needed - we shall not focus at the "when<br>> everything is done" milestone and ..... never finish it (problem of<br>> PyWPS nowadays). So, let's continue in current way: once some standard<br>> or it's version is implemented, we can put another minor version out.<br>> When everything is there, there is time to call it "1.0" version.<br>> <br>> GIT: Since we not have clearly defined release, I would support to cut<br>> it now and move to github and then, Kyles fork can be merged back easy.<br>> <br>> Just my 0.02<br>> <br>> Jachym<br>> <br>> Dne 15.6.2012 19:04, Tom Kralidis napsal(a):<br>> > <br>> > <br>> > All: in thinking about the next release of OWSLib, I think it's time<br>> > that the next release is cut as 1.0.0 per<br>> > https://twitter.com/howardbutler/status/213624529031925760. A number<br>> > of items would be included, including (but not limited to):<br>> > <br>> > - github migration: move the SCM from svn to github. This would<br>> > include porting tickets from svn trac to github issues - migrate<br>> > mailing list and web presence to OSGeo infrastructure: this can set<br>> > us up (in the long term) as an OSGeo Labs project<br>> > (http://wiki.osgeo.org/wiki/OSGeo_Labs), as well as wein us off the<br>> > sf.net infrastructure - WFS 2.0.0 support/improvements (Jachym) -<br>> > Kyle's improvements (SOS, SensorML, tests, etc.) at<br>> > https://owslib.svn.sourceforge.net/svnroot/owslib/branches/kyle-github/<br>> > . I'm starting to wonder whether moving to github *before* Kyle<br>> > patches svn would alleviate some of the pain of integrating this<br>> > great work<br>> > <br>> > Nice to have: - WMS 1.3.0 support - increased harmonization of<br>> > interfaces<br>> > <br>> > Comments/ideas? Other items?<br>> > <br>> > ..Tom<br>> > <br>> > <br>> > <br>> > <br>> > <br>> > ------------------------------------------------------------------------------<br>> ><br>> > <br>> Live Security Virtual Conference<br>> > Exclusive live event will cover all the ways today's security and <br>> > threat landscape has changed and how IT managers can respond.<br>> > Discussions will include endpoint security, mobile security and the<br>> > latest in malware threats.<br>> > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/<br>> > <br>> > <br>> > <br>> > _______________________________________________ owslib-devel mailing<br>> > list owslib-devel@lists.sourceforge.net <br>> > https://lists.sourceforge.net/lists/listinfo/owslib-devel<br>> <br>> -- <br>> Jachym Cepicky<br>> Help Service - Remote Sensing s.r.o.<br>> jachym.cepicky@gmail.com<br>> HS-RS: jachym@hsrs.cz http://bnhelp.cz<br>> http://les-ejk.cz<br>> <br></div> </div></body>
</html>