I can also help to setup travis-ci generation of tarballs, rpms, etc
and have it upload betas automaticly.
It is wonderful that you can do the above. Thank you very much!
I will start playing with this again today. travis does not deploy
during pull requests that is fine.
I have a personal aws s3 i will use for this.
https://gist.github.com/jrossi/a7934a436fef3811f97e
Clicking the above link gives me the summary of Pull Requests.
Where to go in order to see the python code?
The gist is two files you have to scroll to the very bottem. I will
submit a pull-request and put them in contrib so we can build upon them.
# Code management of bug fixes #############################
During alpha, beta, and RC I propose that we make sure that all fixes go
into master then are cherry picked from master to the release repo. This
will make sure that all changes are always in master and make sure that
the repos don't become divergent.
This is certainly one model to work, i.e., Master ---checy-pick---> release
repo.
Would you consider another model, i.e., Fix on release repo. ---merge
back---> Master ?
Which one is easier?
work in master then back port. This is how a lot do it nowa days:
*bsd, linux kernel, redhat, etc. The reason is pulling a fix forward in
time is harder to do and you take a chance of have to repeat fixes if
you don't pull them forward to master quicklty .
pull request ->
(ossec/ossec-hids#master) ->
cherry-pick ->
(ossec/ossec-hids-2.8#master)
But i will help out eather way and we can try one and find out it does
not work for us we can correct during the next release cycle.
hub is the tool that make this sooooo simple hub.github.com
Good to have the tool.
--
---
You received this message because you are subscribed to the Google Groups
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
