> 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! > > # Use the Pull Requests Not the Commits #################### > > To create the release notes I would use the Pull Requests themselves. > They reflect a complete idea that is merged into master. Their are also > all kinds of tools to help out with this. I started writing one in > python but I will let someone else take over. Here is the code: > https://gist.github.com/jrossi/a7934a436fef3811f97e > > This has two files the python code to make the markdown release notes > from github pull requests. It's far from complete but should make > release note generation easy. If we want to control what goes into the > release notes. Just use pull request tags or milestones or what ever. > > Clicking the above link gives me the summary of Pull Requests. Where to go in order to see the python code? > # 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? > > 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.
