An error occurred fetching the project authors.
- 08 Jun, 2011 6 commits
-
-
Rafael Monnerat authored
This is not needed for now.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Łukasz Nowak authored
-
- 07 Jun, 2011 2 commits
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
- 06 Jun, 2011 8 commits
-
-
Rafael Monnerat authored
This is just a initial skel with code based on erp5 setup.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Sebastien Robin authored
-
Sebastien Robin authored
-
Sebastien Robin authored
-
Sebastien Robin authored
-
Sebastien Robin authored
-
- 04 Jun, 2011 2 commits
-
-
Sebastien Robin authored
-
Kazuhiko Shiozaki authored
-
- 03 Jun, 2011 3 commits
-
-
Sebastien Robin authored
-
Sebastien Robin authored
- a list of repositories to synchronize can be provided - the first repository is used for software - transfer project revision with string like [repo x]=[commit count x]-[hash x],[repo y]=[commit count y][hash y] - change related to new structure : recipe slapos.recipe.erp5testnode is inside slapos.cookbook egg - allow authentification setting for several repositories - drop support for svn
-
-
- 02 Jun, 2011 4 commits
-
-
Rafael Monnerat authored
Development Install the latest version directly from git repository. This will possible become the standard way to install cloudooo.
-
Rafael Monnerat authored
Reorganise cloudooo component and stack to reuse code instead duplicate it.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
- 01 Jun, 2011 10 commits
-
-
Kazuhiko Shiozaki authored
-
Cédric de Saint Martin authored
-
Nicolas Delaby authored
-
Nicolas Delaby authored
-
Nicolas Delaby authored
-
Łukasz Nowak authored
Follow the rules. Do not add new things into 'master' branch, but use slapos one. It was used to introduce slapos component, and as repository is about slapos, this place seems the best way to start explaining.
-
Łukasz Nowak authored
-
Łukasz Nowak authored
-
Łukasz Nowak authored
Thanks to using own python with own libraries, there will be library version conflicts, as lxml is built against own libz.
-
Łukasz Nowak authored
Thanks to using own python with own libraries, there will be library version conflicts, as lxml is built against own libz.
-
- 31 May, 2011 5 commits
-
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-