On Mon, Jun 30, 2014 at 7:21 AM, Pierre Ossman wrote:
> 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
>
The source for the builds has been coming from the github repo since last
week. I suggest leaving them where they are for now, since the URL makes
no reference to sourceforge.
>
> - "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?
>
I'm certain that I've seen README's on SF download pages that redirect
people to github, etc. I'll see if I can locate an example.
-brian
------------------------------------------------------------------------------
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
