[ 
https://issues.apache.org/jira/browse/S4-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthieu Morel resolved S4-39.
------------------------------

    Resolution: Fixed

Task completed. 

0.3 was already released and not ASF compliant, so I did not include it.

h3. Current structure:

* *dev* branch contains the code for S4 0.4, which is an evolution of 0.3 with 
checkpointing + bugfixes. We still have a few things to add for checkpointing 
(taking into account feedback we got) as well as some documentation
** this code was imported from https://github.com/s4/s4 (master branch) and 
already contains package renaming and license headers (thanks Bruce!)
* *piper* branch contains the code for s4-piper,  imported from 
https://github.com/leoneu/s4-piper/ (master branch)

See a summary here: 
https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=summary

The importation preserves the complete git history.

bq. Note: there is currently no "master" branch in the incubator repository for 
S4.



h3. Access to the repository:

* as a committer: 
{code}git clone 
https://<user_name>@git-wip-us.apache.org/repos/asf/incubator-s4.git{code}
* as a user or contributor: 
{code}git clone http://git-wip-us.apache.org/repos/asf/incubator-s4.git{code}
* more information here: https://git-wip-us.apache.org/

{quote}
*Note*: For the moment, you'll probably get this warning: "remote HEAD refers 
to nonexistent ref, unable to checkout." which is due to the absence of a 
master branch for the moment. 

Don't panic! Simply do "git checkout dev" or "git checkout piper" to get one of 
the available branches. 
{quote}
                
> migrate code to Apache's git repository
> ---------------------------------------
>
>                 Key: S4-39
>                 URL: https://issues.apache.org/jira/browse/S4-39
>             Project: Apache S4
>          Issue Type: Task
>            Reporter: Matthieu Morel
>            Assignee: Matthieu Morel
>
> Git repo is now available ( INFRA-4226 ) 
> We'll need to push existing code to Apache's git repository and leave 
> Github's S4 repository as read-only (at least, stop writing to it). We also 
> need to do the same for S4-piper.
> * S4 0.3 will go to master branch
> * S4 0.4 will go to dev branch
> * S4-piper will go to "s4-piper" feature branch

--
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

        

Reply via email to