On Sun, 11 Jul 2010 19:38:24 +0200 Christoph Zwerschke <[email protected]> wrote: > Am 11.07.2010 18:49 schrieb D'Arcy J.M. Cain: > > This is up. I had asked if we should put the Trac site on the web page > > but didn't see any response. > > Really? The URLs that I had currently do not work, nor does the SVN > checkout address. Did you relocate them again? And yes, there should be > links to the Trac and the SVN checkout address on the homepage.
It is still http://trac.pygresql.org:8000/trac. Problem was that I had to change the name of the PyGreSQL user as it conflicted with the mailing list and I forgot to restart the trac server. Check it now. As for SVN, the URI on the page works for me. What do you get? The web interface works as well. > But I agree with you and Paul that we shouldn't drop support for Py > 2.4/2.5 for quite a while, so we will have to make separate releases for > these anyway. We could use versioning schemes like these: > > Approach 1 or 2: > > 4.x versions for Py 2.3/2.4 to 2.7 only > 5.x versions for both Py 2.6/2.7 and Py 3 (same codebase) > (maybe 6.x or later versions for Py 3 only) That seems like a good approach. It's almost like Approach 3 except that it includes 2.6 and 2.7 in the new code branch. Should we drop 2.3 support in 4.1 anyway? I personally don't have a test environmemnt for it any more. Does anyone else? Would 4.x become a bugfix only branch? > Approach 3: > > 4.x versions for Py 2.3/2.4 to 2.7 only > 5.x and later versions for Py 3 only Doable as well but it means leaving 2.6 and 2.7 users behind on any new features. How much of an issue would that be? Do we have any major new features in the works right now? -- D'Arcy J.M. Cain PyGreSQL Development Group http://www.PyGreSQL.org _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
