I am more or less done with the migration, so it is time to consider a formal switch. What's left:
- Moving over relevant bug entries - Copy over at least the 1.3.1 release. - Decide what to do about nightly builds - "Shut down" the sourceforge page - Send out an annoucement Anyone got any experience of what's appropriate to with the old project page in a case like this? Putting some kind of notice and putting as much as possible in read-only state is the minimum effort I'd say. But should we do more? Actively break something to make sure people notice? Remove things? Rgds -- Pierre Ossman Software Development Cendio AB http://cendio.com Teknikringen 8 http://twitter.com/ThinLinc 583 30 Linköping http://facebook.com/ThinLinc Phone: +46-13-214600 http://plus.google.com/+CendioThinLinc A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
