OK, I think these two can be merged into one discussion. SourceForge has moved to a new infrastructure with better trackers, etc. https://sourceforge.net/p/upgrade/
I'd like to upgrade after the 2.3.2 release -- ideally 9/15. For us, there's little downside. We maintain our webpages outside of SF, and don't have multiple Git repositories. The only item I see that we'd lose is the "SCM hooks" that mail openbabel-updates on commits. If there are no objections, I'll flip the upgrade for Open Babel on 9/15 -- after making the release official. On that subject, several people have pushed for a migration to Git. I think we should also do that -- we can create new hooks (and ways to track code changes through RSS, etc.). I'm open to timing for the Git migration. I'd suggest just after the release is tagged (i.e., the same weekend), but I'm open to suggestions. One benefit of doing this at the same time, is that the SF upgrade would already break the URLs for the SVN repositories: > Note that the URLs used to access your code repositories will change, and an > email will be sent to all project developers with the new URLs after the > upgrade is complete. I think we might as well take the jump -- GitHub, for example, offers SVN access to its Git repositories. -Geoff --- Prof. Geoffrey Hutchison Department of Chemistry University of Pittsburgh tel: (412) 648-0492 email: geo...@pitt.edu web: http://hutchison.chem.pitt.edu/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
