search

hackforla / website

Hack for LA's website
https://www.hackforla.org
GNU General Public License v2.0
294 stars 723 forks source link

Setup version and release structure for HfLA website #97

Open ExperimentsInHonesty opened 5 years ago

ExperimentsInHonesty commented 5 years ago

Dependency

Overview:

Professionalize the HfLA website development environment by using appropriate versioning, setting milestones and releases.

resources:

examples:

https://github.com/CityOfLosAngeles/mobility-data-specification/releases

thekaveman commented 5 years ago

Ok, so for master I went back into the history and did my best to estimate some version tags, following the structure of semver.

This is easy to do, even retroactively. Just figure out the commit hash of where to apply the tag, make sure the branch containing that commit is checked out, and use the command:

git tag <tag name> <commit hash>

For example, the latest tag 1.5.0 was created using:

git tag 1.5.0 daa3e68a07bb92b9323441aa3efc67f844735085

(either the long or short commit hash will work).

With one or more tags created, send them to GitHub with:

git push --tags

With the tags pushed to GitHub, we can publish releases directly from the tags; a release has been created for each of the 1.x.0 versions (up to 1.5.0).

ExperimentsInHonesty commented 5 years ago

Issue moved from Prioritized Backlog in migrate 1.x to 2.0 to 2.x development because we are done versioning pre launch

thekaveman commented 5 years ago

Copying my comments from the duplicate #121:

Please see my comments in #120 regarding when/how tags/versions are created.

Note that just because a commit is merged into gh-pages, it does not necessarily mean you have to tag/release. It's OK to stack a few up. It's also OK (as you suggest here) to create e.g. a dev branch that collects all related PRs for a new tag/release until ready. This is typical in larger software projects, I don't know that we need the complexity on this site now - and without a staging/preview version, it isn't as useful. (That could be the next task, to setup previews using e.g. surge.sh or something).

abregorivas commented 5 years ago

Here are two links to surge to have a continues deployment for Jekyll. May be handy...

https://surge.sh/help/deploying-a-jekyll-project https://surge.sh/help/deploying-continuously-using-git-hooks

ExperimentsInHonesty commented 4 years ago

@cnk can we talk about this when you get some time. We used to do this and then we stopped: https://github.com/hackforla/website/releases

ExperimentsInHonesty commented 1 year ago

We are going to do a new version when the homepage launches . Saving this feature for major releases only