[
https://issues.apache.org/jira/browse/S4-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthieu Morel updated S4-39:
-----------------------------
Description:
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
was:
Git repo is now available ( INFRA-4266 )
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
> 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
>
> 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
