You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by to...@apache.org on 2013/11/27 01:07:58 UTC
[1/3] git commit: Update committer guide.
Updated Branches:
refs/heads/trunk c28e0f1ca -> 61ba09d70
Update committer guide.
Project: http://git-wip-us.apache.org/repos/asf/libcloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/libcloud/commit/1102b40d
Tree: http://git-wip-us.apache.org/repos/asf/libcloud/tree/1102b40d
Diff: http://git-wip-us.apache.org/repos/asf/libcloud/diff/1102b40d
Branch: refs/heads/trunk
Commit: 1102b40da88e3d1b76fefd7c309a2983f7219cbe
Parents: c28e0f1
Author: Tomaz Muraus <to...@apache.org>
Authored: Wed Nov 27 01:02:22 2013 +0100
Committer: Tomaz Muraus <to...@apache.org>
Committed: Wed Nov 27 01:02:22 2013 +0100
----------------------------------------------------------------------
docs/committer_guide.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/libcloud/blob/1102b40d/docs/committer_guide.rst
----------------------------------------------------------------------
diff --git a/docs/committer_guide.rst b/docs/committer_guide.rst
index ea96c03..3cc561d 100644
--- a/docs/committer_guide.rst
+++ b/docs/committer_guide.rst
@@ -92,8 +92,9 @@ are suitable to be uploaded for a release.
Apache mirrors, but they should be instantly available at
http://www.apache.org/dist/libcloud/.
-* If there is more than one older release in the repository, delete the
- oldest one. Old releases are automatically archived and available at
+* If there is more than one older release in the repository, delete rest of the
+ old release and only leave current and previous release there.
+ Old releases are automatically archived and available at
https://dist.apache.org/repos/dist/release/libcloud/.
4. Tagging a release
[2/3] git commit: docs: Update FAQ page.
Posted by to...@apache.org.
docs: Update FAQ page.
Project: http://git-wip-us.apache.org/repos/asf/libcloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/libcloud/commit/401cd52c
Tree: http://git-wip-us.apache.org/repos/asf/libcloud/tree/401cd52c
Diff: http://git-wip-us.apache.org/repos/asf/libcloud/diff/401cd52c
Branch: refs/heads/trunk
Commit: 401cd52c32144c12182b379f979adb918ae4bbba
Parents: 1102b40
Author: Tomaz Muraus <to...@apache.org>
Authored: Wed Nov 27 01:06:42 2013 +0100
Committer: Tomaz Muraus <to...@apache.org>
Committed: Wed Nov 27 01:06:42 2013 +0100
----------------------------------------------------------------------
docs/faq.rst | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/libcloud/blob/401cd52c/docs/faq.rst
----------------------------------------------------------------------
diff --git a/docs/faq.rst b/docs/faq.rst
index 1be0d24..734fd8d 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -72,15 +72,15 @@ following criteria:
3. It's possible to build a common API on top of services provided by different
services
-Last point is the most important one, because Libcloud acts as a lowest common
-denominator and can be used with many different providers.
-Sometimes it doesn't make sense to build a common Libcloud API even if multiple
-providers offer a similar service. Usually the case is that the APIs are vastly
-different and there aren't enough common points which would allow us to build a
-cross-provider API which would still provide enough benefit to the end user.
-
-If the API matches the criteria mentioned above you should send a proposal to
-our :ref:`mailing list <mailing-list>` where we can discuss it further. Ideally proposal should also
-contain a prototype of a driver for at least two different providers. This
-help with making sure that API you designed is not biased against a single
-provider.
+Libcloud can be used with many different providers and acts as a lowest common
+denominator which makes the last point most important one. Sometimes it doesn't
+make sense to build a common Libcloud API even if multiple providers offer a
+similar service. Usually the case is that the APIs are vastly different and
+there aren't enough common points which would allow us to build a
+cross-provider API which would still provide enough value to the end user.
+
+If the API matches the criteria defined above, you should send a proposal to
+our :ref:`mailing list <mailing-list>` where we can discuss it further.
+Ideally, the proposal should also contain a prototype of a driver for at least
+two different providers. This helps us make sure that the API you have designed
+is not biased towards a single provider.
[3/3] git commit: docs: Update committer guide.
Posted by to...@apache.org.
docs: Update committer guide.
Project: http://git-wip-us.apache.org/repos/asf/libcloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/libcloud/commit/61ba09d7
Tree: http://git-wip-us.apache.org/repos/asf/libcloud/tree/61ba09d7
Diff: http://git-wip-us.apache.org/repos/asf/libcloud/diff/61ba09d7
Branch: refs/heads/trunk
Commit: 61ba09d70566c44a09be649c85d290e0fe3f2911
Parents: 401cd52
Author: Tomaz Muraus <to...@apache.org>
Authored: Wed Nov 27 01:07:38 2013 +0100
Committer: Tomaz Muraus <to...@apache.org>
Committed: Wed Nov 27 01:07:38 2013 +0100
----------------------------------------------------------------------
docs/committer_guide.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/libcloud/blob/61ba09d7/docs/committer_guide.rst
----------------------------------------------------------------------
diff --git a/docs/committer_guide.rst b/docs/committer_guide.rst
index 3cc561d..660dd6c 100644
--- a/docs/committer_guide.rst
+++ b/docs/committer_guide.rst
@@ -92,9 +92,9 @@ are suitable to be uploaded for a release.
Apache mirrors, but they should be instantly available at
http://www.apache.org/dist/libcloud/.
-* If there is more than one older release in the repository, delete rest of the
- old release and only leave current and previous release there.
- Old releases are automatically archived and available at
+* If there is more than one old release in the repository, delete rest of the
+ old release and only leave current and previous release there. Old releases
+ are automatically archived and available at
https://dist.apache.org/repos/dist/release/libcloud/.
4. Tagging a release