Re: [Javagit-devel] Releasing Alpha Build

[Ross S. <ros...@ny...>]

I'll also write some sample code using the high-level API, and pass  
it along later tonight.

I can post to Digg & reddit once we're live.

Verson 0.1.0 seems right.  We're more functional than a 0.0.1, but  
not as stable as a 0.5.


On Aug 3, 2008, at 6:31 PM, James Linder wrote:

> Hi All,
>
> We are close to ready for cutting the alpha release.  Here are the
> final things I see that we need before we can cut the build.  Is there
> anything else we should be getting in before cutting the release?
>
> 1.  Code samples for the website.  Anirhuda is working on them and
> should have some examples ready shortly.
>
> 2.  Writing up release notes.  I am working on this now.  I'll be
> committing them to the repository soon.
>
> 3.  Fixes for some final comments about bug 2031803.  This is not a
> show stopper, but it would be great to get these changes in before
> releasing.
>
> 4. Writing text for a release notice.  I am working on this too.  I'll
> post it to the list for feedback shortly.
>
>
> Once we've got these squared away, assuming there are no other
> outstanding changes to make, I'll cut the release.  I am writing up
> the process I intend to use and will commit it to the repository in
> the trunk/docs directory.
>
> For posting the release to the world, I figured I would announce it
> via freshmeat.net, ac...@cs..., fun...@li...,
> gi...@vg... and the JavaGit website.  Could someone else look
> into posting on programming.reddit, digg, your own blogs, any other
> git-specific sites, JRuby?
>
>
> Finally, I figured we would call it version 0.1.0.  Does anyone have
> thoughts or opinions on the version number to start at?
>
> Cheers,
>
> James
>
> On Sun, Aug 3, 2008 at 1:12 AM, James Linder  
> <jam...@gm...> wrote:
>> Hi All,
>>
>> Here is the status of the build so far as I see it.  Please respond
>> status updates.
>>
>> Still waiting on:
>>
>> - Cookbook-style code samples for the website.  Anirhuda, what is the
>> status of the code samples you are working on?
>>
>> - We've fixed some JavaDoc documentation holes.  Are there other ones
>> that we should be fixing before release?
>>
>> - Writing text for a release notice to post in publication of our  
>> release.
>>
>> - Writing up any release notes.
>>
>> - Figure out how to get JavaGit to show up as a project when  
>> searching
>> in Sourceforge for JavaGit
>>
>> - What other bugs are you all fixing that we should get into this
>> build?  Please go through the bugs and fix any you can.
>>
>>
>>
>> Done:
>>
>> - Ross's JavaGitConfiguration class and integration.
>>
>> - GitLog has been added.
>>
>> - Moved a good portion of our notes from the OSP class wiki to the
>> JavaGit.com website.
>>
>> - I added the suggested FAQ item from Andrew.  For the msysgit/cygwin
>> git problem seen by Paul, I think we can wait and see if other users
>> post about it before putting it up.
>>
>> Cheers,
>>
>> James
>>
>>
>> On Thu, Jul 31, 2008 at 6:51 AM, James Linder  
>> <jam...@gm...> wrote:
>>> Hi All,
>>>
>>> The current plan is to release an Alpha build on Sunday.  To hit  
>>> this
>>> goal, we need to do some prep work.  Following is a list of the
>>> highest priority tasks I see us needing to do before the  
>>> release.  If
>>> there are other things you think should be on this highest priority
>>> list, please respond with those items.
>>>
>>> 1. Add some code samples to the website.  Create a few pages with
>>> sample code for some basic ways to use the library preferably in a
>>> cookbook style set of pages.  A good example to follow is
>>> http://groovy.codehaus.org/Cookbook+Examples .  Add the main  
>>> cookbook
>>> page to the menu under the Documentation section.  The code for the
>>> website is now in the repository under "website".
>>>
>>> 2. Fix as many bugs as we can.  See what bugs apply to code you have
>>> written and fix them.  Please assign the bug to yourself before
>>> starting work on it so others know you are taking responsibility for
>>> it.
>>>
>>> 3.  We are waiting on Ross's GitConfig (?) class.
>>>
>>> 4.  Add to the FAQ;
>>>  - msysgit and cygwin+git conflict information as indicated by Paul.
>>>  - The troublueshooting note that Andrew sent to the javagit-users
>>> list on July 21.
>>>  - Anything else you can think of that is important.
>>>
>>> 5. Fix any javadoc documentation holes in the api.commands.Git*
>>> classes that we have.  Since these will be the primary documentation
>>> points for our users for the near future, it is critical that the
>>> javadocs be thorough and of high-quality.
>>>
>>> 6. Anirudha, add the ...api.commands.GitLog class.
>>>
>>> Cheers,
>>>
>>> James
>>>
>>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Javagit-devel mailing list
> Jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javagit-devel