Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adjust internal documentation according to #7812 #11117

Closed
wants to merge 1 commit into from
Closed

Conversation

cebe
Copy link
Member

@cebe cebe commented Mar 15, 2016

adjust internal documentation according to #7812

Versioning was not up to date with what was proposed in the issue and I also included project organization.

This is WIP, so do not merge yet. I am planning to add more things on release automation soon.
We also need a branching/merging concept that allows for making bugfix-only releases.

@cebe cebe added this to the website and infrastructure milestone Mar 15, 2016
@cebe cebe force-pushed the auto-release branch 2 times, most recently from 15b72b9 to 1f5a2b8 Compare March 15, 2016 02:37
@cebe
Copy link
Member Author

cebe commented Mar 15, 2016

We also need a branching/merging concept that allows for making bugfix-only releases.

I tend to reject this idea and do normal patch releases as we are already doing but speed things up by making release more automated. Tagging on one branch is easy, separating bug and feature releases will require a lot of back and forth merging which is not easily handlealbe.

@yiisoft/core-developers opinions?

- [Yii2 View Code Style](view-code-style.md)


Dokumentation
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Dokumentation" -> "Documentation"

@SilverFire SilverFire added the type:docs Documentation label Mar 15, 2016
@SilverFire
Copy link
Member

👍

- Updating the Mime Type Magic file (`framework/helpers/mimeTypes.php`) from the Apache HTTPd repository.
Run `./build/build mime-type` to update the file.

All of the above commands are included in the [release process](). They may be run between releases but it is not necessary.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it to be developed later?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have completed the release command while doing the 2.0.8 release, will merge this soon.

@samdark
Copy link
Member

samdark commented Apr 30, 2016

👍

@cebe cebe closed this in a6b16db Jun 26, 2016
@cebe cebe deleted the auto-release branch June 27, 2016 01:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:docs Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants