hyper-model 0.99.6 → 1.0.alpha1

Sign up to get free protection for your applications and to get access to all the features.
@@ -1,21 +0,0 @@
1
- The MIT License (MIT)
2
-
3
- Copyright (c) 2016 Mitch VanDuyn
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in
13
- all copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
- THE SOFTWARE.
data/README.md DELETED
@@ -1,51 +0,0 @@
1
- <div class="githubhyperloopheader">
2
-
3
- <p align="center">
4
-
5
- <a href="http://ruby-hyperloop.org/" alt="Hyperloop" title="Hyperloop">
6
- <img width="350px" src="http://ruby-hyperloop.org/images/hyperloop-github-logo.png">
7
- </a>
8
-
9
- </p>
10
-
11
- <h2 align="center">The Complete Isomorphic Ruby Framework</h2>
12
-
13
- <br>
14
-
15
- <a href="http://ruby-hyperloop.org/" alt="Hyperloop" title="Hyperloop">
16
- <img src="http://ruby-hyperloop.org/images/githubhyperloopbadge.png">
17
- </a>
18
-
19
- <a href="https://gitter.im/ruby-hyperloop/chat" alt="Gitter chat" title="Gitter chat">
20
- <img src="http://ruby-hyperloop.org/images/githubgitterbadge.png">
21
- </a>
22
-
23
- [![Build Status](https://travis-ci.org/ruby-hyperloop/hyper-mesh.svg?branch=master)](https://travis-ci.org/ruby-hyperloop/hyper-mesh)
24
- [![Codeship Status for ruby-hyperloop/hyper-store](https://app.codeship.com/projects/4454c560-d4ea-0134-7c96-362b4886dd22/status?branch=master)](https://app.codeship.com/projects/202301)
25
- [![Gem Version](https://badge.fury.io/rb/hyper-mesh.svg)](https://badge.fury.io/rb/hyper-mesh)
26
-
27
- <p align="center">
28
- <img src="http://ruby-hyperloop.org/images/HyperModels.png" width="100" alt="Hyper-models">
29
- </p>
30
-
31
- </div>
32
-
33
- ## Hyper-Mesh GEM is part of Hyperloop GEMS family
34
-
35
- Hyper-Mesh GEM comes with the Hyperloop GEM.
36
-
37
- But if you want to install it separately, please install the [Hyper-model GEM](https://github.com/ruby-hyperloop/hyper-model).
38
-
39
- ## Community
40
-
41
- #### Getting Help
42
- Please **do not post** usage questions to GitHub Issues. For these types of questions use our [Gitter chatroom](https://gitter.im/ruby-hyperloop/chat) or [StackOverflow](http://stackoverflow.com/questions/tagged/hyperloop).
43
-
44
- #### Submitting Bugs and Enhancements
45
- [GitHub Issues](https://github.com/ruby-hyperloop/hyperloop/issues) is for suggesting enhancements and reporting bugs. Before submiting a bug make sure you do the following:
46
- * Check out our [contributing guide](https://github.com/ruby-hyperloop/hyperloop/blob/master/CONTRIBUTING.md) for info on our release cycle.
47
-
48
- ## License
49
-
50
- Hyperloop is released under the [MIT License](http://www.opensource.org/licenses/MIT).
51
-
@@ -1,9 +0,0 @@
1
-
2
- For example assuming you are releasing fix to 0.8.18
3
-
4
- 1. Checkout 0-8-stable
5
- 2. Update tests, fix the bug and commit the changes.
6
- 3. Build & Release to RubyGems (Remember the version in version.rb should already be 0.8.19)
7
- 4. Create a tag 'v0.8.19' pointing to that commit.
8
- 5. Bump the version in 0-8-stable to 0.8.20 so it will be ready for the next patch level release.
9
- 6. Commit the version bump, and do a `git push --tags` so the new tag goes up