Difference between revisions of "DPS909 and OSD600 Fall 2010 0.1 Release"

From CDOT Wiki
Jump to: navigation, search
Line 53: Line 53:
* '''Project URL:''' ''[[Comicbook-js]]''
* '''Project URL:''' ''[[Comicbook-js]]''
* '''0.1 Blog Post''': ''[http://brianl20.blogspot.com/2010/10/comic-book-release-01.html 0.1 Release]''
* '''0.1 Blog Post''': ''[http://brianl20.blogspot.com/2010/10/comic-book-release-01.html 0.1 Release]''
* '''Source Code''': ''[http://github.com/blaw1/osd600]''
* '''Source Code''': ''[http://github.com/blaw1/osd600 Github Repo]''

Revision as of 17:39, 22 October 2010


Your 0.1 release is the first point at which you have a working release of your project. It often represents as much research as it does coding, but always includes a working first-version. Through the coming weeks and months, you will iterate on your 0.1 code and refine it, fix bugs, add new features, etc. The 0.2, 0.3, ... releases will see this first step grow into something more polished and full-featured.

Submission Instructions

In order to submit your release, you need to complete a number of steps:

  1. Release your code, either as a patch or commit on an existing project's repo, or start a new one
  2. Create and/or update a wiki page with technical details about your release. This will be your project's homepage, and should have links and info relevant to anyone wishing to use it or contribute
  3. Write a blog post announcing the release of your project's first milestone. If your code does something that can be demoed, make sure you include a live demo, screenshots, and perhaps a video on youtube if it is hard to setup and run. You should also include info about what is coming in 0.2.

After you have done the above steps, please add an entry below with relevant links. Here is a template you can use:

  • Name: <your name>
  • Project: <project name>
  • Project URL: <project url or wiki page>
  • 0.1 Blog Post: <link to your 0.1 release blog post>
  • Source Code: <link to a git repo, bug with patch, etc.>