Skip to content

Commit

Permalink
Revert "update"
Browse files Browse the repository at this point in the history
This reverts commit ad99dca.
  • Loading branch information
Lu Nguyen committed Oct 30, 2019
1 parent ad99dca commit ead2790
Show file tree
Hide file tree
Showing 5,066 changed files with 564,185 additions and 0 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
682 changes: 682 additions & 0 deletions .drone.yml

Large diffs are not rendered by default.

17 changes: 17 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Set the default behavior, in case people don't have core.autocrlf set.
* text=auto

# Explicitly declare text files you want to always be normalized and converted
# to native line endings on checkout.
*.php text eol=lf
*.html text eol=lf
*.js text eol=lf
*.xml text eol=lf
*.ini text eol=lf

# Denote all files that are truly binary and should not be modified.
*.png binary
*.jpg binary
*.gif binary
*.bak binary
*.mwb binary
80 changes: 80 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
# OSX
.DS_Store
._*
.Spotlight-V100
.Trashes

# Windows
Thumbs.db
Desktop.ini

# PHPStorm
.idea/

# Sublime Text
*.sublime*

# Eclipse
.buildpath
.project
.settings

# Temp files
*.tmp
*.bak
*.swp
*~.nib
*~

# Ignore mergetool files
*.orig

# Phing build script
build.properties
phing-latest.phar

# Gulp Build script
gulp-config.json
npm-debug.log
node_modules/

# Composer
composer.lock
vendor/*
tests/vendor/*
**/vendor/*

# Bower
bower_components/

# Test related files
tests/system/servers/configdef.php
tests/system/webdriver/tests/logs/
codecept.phar
tests/*/*Tester.php
selenium.log
tests/_output
tests/joomla-cms
tests/cache
tests/RoboFile.ini
selenium-server-standalone.jar
tests/_support/_generated/*
tests/releases/*
tests/acceptance.suite.yml

# Ignore redSHOP config
component/admin/config/config.php

# Never ignore
!.gitignore
!index.html
!index.php

# Releases folder
releases/*

# Checksum MD5 Files
checksum.md5
checksum.md5.json
component/admin/assets/checksum.md5
component/admin/assets/checksum.md5.json
5 changes: 5 additions & 0 deletions .scrutinizer.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# .scrutinizer.yml
build:
environment:
php:
version: 7.1 # Common versions: 5.4, 5.5, 5.6, 7.0, 7.1, or hhvm
339 changes: 339 additions & 0 deletions LICENSE.txt

Large diffs are not rendered by default.

160 changes: 160 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,160 @@
redSHOP 2.x
==========

[![Build Status](https://travis-ci.com/redCOMPONENT-COM/redSHOP.svg?token=exSzjzLhFrzHef99DDg1&branch=develop)](https://travis-ci.com/redCOMPONENT-COM/redSHOP) [![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/redCOMPONENT-COM/redSHOP/badges/quality-score.png?b=develop&s=f945d89ef335953761803d0e0f0e37d5fecf0b62)](https://scrutinizer-ci.com/g/redCOMPONENT-COM/redSHOP/?branch=develop)

## Requirement
PHP Version: **>= 5.6**

## Documentation

https://github.com/redCOMPONENT-COM/documentation

## DB Change

There are an MySQL Workbench DB Model file in src/db/redshop.mwb. When need some changes in DB structure:

- Use MySQL Workbench open this `src/db/redshop.mwb` file.
- Add some necessary changes in MySQL Workbench
- Go to File > Export > Forward Engineer SQL Create Script...
- Choose path for output script file (admin/sql/mysql/install.sql)
- Check on 2 option *Generate DROP Statements Before Each CREATE Statement* and *Omit Schema Qulifier in Object Names*.
- Open generated install.sql file and remove the comments from MySQL Workbench
- In install.sql, remove this line at top:

> SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES';
- In install.sql, remove this line at bottom:

> SET SQL_MODE=@OLD_SQL_MODE;
## Release process for redSHOP
Please follow the next steps in order to release a new version of redSHOP.

- Execute component_packager.xml PHING file to generate the main component package (includes 1 module and 2 plugins).

## Using Gulp build system

Before you can run any Gulp command you need to:

- download and install NodeJS https://nodejs.org/download/
- install npm: `sudo npm install`
- install Gulp: `npm install --save gulp-install`
- install joomla-gulp-release: `sudo npm install --save-dev joomla-gulp-release`

### Following tasks and switches are available:
#### Setup gulp config file. Copy and rename `gulp-config.sample.json` file into `gulp-config.json`

> Version and other information can be set in `gulp-config.json` file.
#### To Release `component` and create `.zip` file

> Use this command to release component. Version and other information can be set in `gulp-config.json` file.
gulp release:component

#### To Release `modules` and create `.zip` file

gulp release:modules

#### To Release `plugins` and create `.zip` file

gulp release:plugins

#### To Release `packages` and create `.zip` file

gulp release:packages

_or_

gulp release:packages --folder ./individual_package_dir


This command is to release the extensions.

gulp release:extensions


This command will read the base directory and create zip files for each of the folder.

#### === Switches ===
Pass an argument to choose different folder

--folder {source direcory} Default: "./plugins"

Pass an argument to change suffix for extension

--suffix {text of suffix} Default: "plg_"

#### Example Usage:

gulp release:extensions --folder ./modules --suffix ext_


### Languages & translation
- Move the language files to the translations repository: https://github.com/redCOMPONENT-COM/translations/tree/master/redSHOP/source
- Check in 24hours that Transifex was able to get the new translation strings adding them to the .ini resource files

### Extensions
#### Plugins
- Check if any plugin has been changed in this last release:

> $ git log --oneline --after={2013-04-18} --no-merges --name-only | grep 'plugins\/.*' | cut -d/ -f2,3 | sort | uniq
_Or Compare across versions_

> git log --oneline 1.4/dev19...develop --no-merges --name-only | grep 'plugins\/.*' | cut -d/ -f2,3 | sort | uniq > /var/www/packages/plugins.log
- if plungins have been modified:
- Update the release number in their manifest .xml file with the same release number as the component. For example if we are releasing redSHOP 1.3 and plugin plg_default_shipping has been updated during 1.2 - 1.3 period, then you should set the plugin version to 1.3 here: https://github.com/redCOMPONENT-COM/redSHOP-1.2/blob/master/plugins/redshop_shipping/default_shipping/default_shipping.xml#L4 or leave it as it is if it has not been touch.
- execute the plugins_packager.xml PHING file and upload the new release to redCOMPONENT.com

Note: to match the plugins with it's compatible core version see https://github.com/redCOMPONENT-COM/redSHOP/pull/1548

#### Modules
- Check if any module has been changed in this last release:

> $ git log --oneline --after={2013-04-18} --no-merges --name-only | grep 'modules\/.*' | cut -d/ -f2,3 | sort | uniq
_Or Compare across versions_

> git log --oneline 1.4/dev19...develop --no-merges --name-only | grep 'modules\/.*' | cut -d/ -f2,3 | sort | uniq > /var/www/packages/modules.log
- if modules have been modified:
- Update the release number in their manifest .xml file in the same way you have done it with plugins https://github.com/redCOMPONENT-COM/redSHOP-1.2#plugins
- execute the modules_packager.xml PHING file and upload the new release to redCOMPONENT.com

### Test
- test the packages to ensure that everything works properly.
- share the package in the redSHOP testing chat, so others can do some testing.
- add fast fixes if issues has been identified during testing
- Generate the final packages and contact the Product Owner (Ole) and ask him to upload the packages to redCOMPOPNENT.com

### Update Changelog
- Create the Changelog list of commits:

> git log --oneline 1.4/dev25...develop --no-merges --format="* %s ( %h )" > /var/www/packages/changelog2.log
- Upload the list to http://wiki.redcomponent.com/index.php?title=redSHOP:Changelog


### Prepare software for next release
- Update component version number with next release number at https://github.com/redCOMPONENT-COM/redSHOP/blob/master/redshop.xml#L10
- Create an empty update .sql file at: https://github.com/redCOMPONENT-COM/redSHOP/tree/master/component/admin/sql/updates/mysql
- Merge development branch into Master (see successful git-branching model: http://nvie.com/posts/a-successful-git-branching-model/ )
- Create a release git TAG
- create the tag in local:

> $ git tag -a 1.3 -m "Version 1.3 Stable"
- Upload the tag to Github:

> $ git push --tags
- Check that tag has been created: https://github.com/redCOMPONENT-COM/redSHOP/tags
- Create the release: https://github.com/redCOMPONENT-COM/redSHOP/releases
- Add a description to the release with the changelog information that you generated in the previous step


# Testing
See: [testing redSHOP1](./tests/README.md)
Loading

0 comments on commit ead2790

Please sign in to comment.