Sweet. So, have we decided on using the branching model that Leo proposed, and the workflow that Matthieu proposed? If so, the S4 v 0.3 will go to the master, and s4-piper/master will go to dev branches, right?
Thanks Karthik On Sat, Dec 31, 2011 at 12:09 PM, Leo Neumeyer <[email protected]>wrote: > We have Git. > > > ---------- Forwarded message ---------- > From: Joe Schaefer (Commented) (JIRA) <[email protected]> > Date: Sun, Dec 25, 2011 at 6:10 AM > Subject: [jira] [Commented] (INFRA-4226) Create Git repo for the S4 Project > To: [email protected] > > > > [ > https://issues.apache.org/jira/browse/INFRA-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175828#comment-13175828 > ] > > Joe Schaefer commented on INFRA-4226: > ------------------------------------- > > I gave you an empty repo to start with: > > https://git-wip-us.apache.org/repos/asf/incubator-s4.git > > I hope that is sufficient. > > > Create Git repo for the S4 Project > > ---------------------------------- > > > > Key: INFRA-4226 > > URL: https://issues.apache.org/jira/browse/INFRA-4226 > > Project: Infrastructure > > Issue Type: Task > > Security Level: public(Regular issues) > > Components: Git > > Reporter: Leo Neumeyer > > > > The S4 project has been selected to migrate to the experimental Git > repository. We recently joined the incubator and the code is currently > hosted in GitHub. Please let us know how to proceed. > > The S4 project volunteer to help with the Git task is Ajay Kalangi ( > [email protected]). He is not a committer yet so he doesn't have > an apache.org email address. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > > > -- > > Leo Neumeyer (@leoneu) >
