[Sandy] The version 3.1 definition

[kiroukou]

Indeed, I understand your point.
we need to create a tag if not a branch.
This time I don't plan to create a branch for the 3.1 simply because I  
don't think there will be a 3.2 (in AS3).
So upgrading to 3.1.1 should be done using the trunk. and we should be  
able to move from version to versions using tags (that need to be  
created, I can't do that on my mac software).

I'm though that, as long as there's no compatibility change we can use  
the trunk documentation. Otherwise, I'm ok to create a specific folder  
on FTP to put documentation in, and change link on wiki.

Thomas Pfeiffer
kiroukou at gmail.com



Le 12 mars 09 à 21:26, petit at petitpub.com a écrit :

> Sorry if I bother you with this again.
>
> It is a good thing to have on line documentation, and here the user  
> has access to that http://www.flashsandy.org/support
>
> The link text says "API documentation for Sandy 3.1" but points to  
> the trunk version http://sandy.googlecode.com/svn/trunk/sandy/as3/trunk/docs/index.html
>
> This will only be a problem if the API changes at some point.
>
> One possible solution is to have a 3.1 branch with its own  
> documentation.
>
> Another would be to just create a 3.1 docs directory and link to that.
> Then just unzip the 3.1 docs release archive.
>
> Cheers!
> /Petit
>
> _______________________________________________
> Sandy mailing list
> Sandy at osflash.org
> http://osflash.org/mailman/listinfo/sandy_osflash.org