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

README files still applicable? #31

Closed
kwaegema opened this issue Sep 30, 2015 · 4 comments
Closed

README files still applicable? #31

kwaegema opened this issue Sep 30, 2015 · 4 comments
Assignees

Comments

@kwaegema
Copy link
Member

Is the README file of the repo still of value?
There is also a README.dev in the etc folder, with instructions to install a dev broker, but the link is broken

@ned21
Copy link
Contributor

ned21 commented Mar 22, 2017

Is this fixed by #36?

@ned21
Copy link
Contributor

ned21 commented Mar 23, 2017

  • etc/README.dev refers to internal MS stuff
  • need a document which describes how patches get accepted and the reason for each branch. e.g. never merge to upstream since that is reserved for the upstream authors.
  • Changes in Fix Aquilon README #36 need to go to the correct place

@urbonegi
Copy link

urbonegi commented Sep 29, 2017

README inconsistencies fixed by removing all the contents and adding a link to the Quattor website.

@ned21
Copy link
Contributor

ned21 commented Oct 26, 2017

Doc on how to contribute is: http://www.quattor.org/aquilon/00-install.html#contributing

urbonegi pushed a commit that referenced this issue May 14, 2018
Create new configuration file that overrides MS specific tool locations
and other specific configuration for tests and application run.
Add new methods to Config class to allow overriding and managing config
easier.
Refactor code to remove now unneccessary checks before geting a boolean
config option.
Update README.dev to represent project structure changes and not
reference MS.

Addresses issues raised by community:
#49
#31

Addresses Issue: Jira/AQUILON-4496

Change-Id: I9df99f9fb3efe617307f2715d47d59e755c84987
Reviewed-By: Raphael Beamonte <Raphael.Beamonte@morganstanley.com>
@urbonegi urbonegi reopened this May 21, 2018
XaF pushed a commit that referenced this issue Nov 21, 2018
…aster/by_topic/hlmpp to master

* commit 'ec93677f516594d7df79253e21b06c4a42bd8d6d':
  dbwrappers: change_management: allow to validate Personality
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants