Please take look at this hot social networking site where you can import videos, upload pics, start a group, upload music, advertise for free, list events, and many more: http://socialnetworking.wowjen.com/
On Tue, Nov 11, 2008 at 5:19 PM, vanweerd <[EMAIL PROTECTED]> wrote: > > Hi All, > > I'm trying to understand the deployment model for using Insoshi. > > I see "Rails21" for a tag, but I don't see any means to identify a > release point for deployment. I assume Rails21 is the start point of > Rails21 compliance, but that is only for reference and that I want to > work of the master, which is really the ongoing stable release branch. > > I would guess that work would be done of edge or master depending on > your goals (pure development or adding features for a live site). i.e. > I can assume more stability on master. For a site, I could see > branching master, developing on that, keeping edge current with the > main insoshi repository, and merging from my master branch to my > tracking edge branch, and then pushing to my fork and issuing a pull > request. Though I suppose this could get awkard over time if I stay on > an older branch of the master branch on the main repository. > > I hope this is making sense. I am building a live site, and want to > develop against stable branches, yet still be in a good position to > submit code back. > > Does the above make sense? > > Also, will Insoshi being changing it's release process once it's > further developed? > > Thanks, > Nick > > > --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
