note about latest upgrade guides being on master branch
Created by: bbodenmiller
Add note to upgrade guides to look for latest details on master branch as typically only the upgrade guides on the master branch are updated.
Merge request reports
Activity
Created by: TeatroIO
I've prepared a stage. Click to open.
By Administrator on 2014-09-21T23:49:00 (imported from GitLab project)
By Administrator on 2014-09-21T23:49:00 (imported from GitLab)
Created by: maxlazio
@bbodenmiller Won't this make things even more confusing especially that we mention at the top of the installation doc to switch branches?
By Administrator on 2014-09-22T09:04:06 (imported from GitLab project)
By Administrator on 2014-09-22T09:04:06 (imported from GitLab)
Created by: bbodenmiller
It could be somewhat confusing however nearly all changes to the upgrade guides are made to the
masterbranch. If this change isn't made every update to install guides really needs to be made to bothmasterand version specific branches. I think this note makes it more clear where you should look at the upgrade guides and the note in installation.md makes it more clear where to look at install guide.Maybe docs really need to be in a separate repo and/or a new installation.md should be created for every release so that
masteralways has latest documentation.By Administrator on 2014-09-22T09:11:28 (imported from GitLab project)
By Administrator on 2014-09-22T09:11:28 (imported from GitLab)
Created by: bbodenmiller
@dblessing rebased. Noticed this is also what omnibus repo is doing.
By Administrator on 2014-11-09T11:54:00 (imported from GitLab project)
By Administrator on 2014-11-09T11:54:00 (imported from GitLab)
Created by: jvanbaarsen
We can only accept a merge requests if all the tests are green, can you please make sure the tests of this merge requests are green? If the failing test has nothing do to with your merge request, you might want to rebase with master to see if that makes the tests green again.
By Administrator on 2014-12-13T20:23:50 (imported from GitLab project)
By Administrator on 2014-12-13T20:23:50 (imported from GitLab)
Created by: dblessing
Per policy, all merge requests must have passing tests, whether the failure pertains to the change or not. I restarted the build to see if it passes this time.
By Administrator on 2014-12-13T23:01:36 (imported from GitLab project)
By Administrator on 2014-12-13T23:01:36 (imported from GitLab)
Created by: dblessing
I agree with @maxlazio. The guides specifically instruct a user to change to the stable branch. Maybe this isn't a documentation issue but a process issue where we need to ensure any update guide changes are backported to the stable branch, too.
@bbodenmiller Do you have a specific example of changes made to master but not included in stable branch?
By Administrator on 2014-12-26T14:56:59 (imported from GitLab project)
By Administrator on 2014-12-26T14:56:59 (imported from GitLab)
Created by: dosire
@dblessing I think it is a good idea, these files are versioned with their filename, not by branch, we frequently forget to cherry-pick changes.
By Administrator on 2014-12-29T22:10:52 (imported from GitLab project)
By Administrator on 2014-12-29T22:10:52 (imported from GitLab)
Created by: dblessing
@bbodenmiller If you have time to rebase and include the most recent update guides I think we may be able to get this in for 7.8.
By Administrator on 2015-01-17T17:03:01 (imported from GitLab project)
By Administrator on 2015-01-17T17:03:01 (imported from GitLab)
Created by: jvanbaarsen
This merge request has been closed because a request for more information has not been reacted to for more than 2 weeks. If you respond and conform to the merge request guidelines in our contributing guidelines we will reopen this merge request.
By Administrator on 2015-02-05T19:36:38 (imported from GitLab project)
By Administrator on 2015-02-05T19:36:38 (imported from GitLab)
