Skip to content

Conversation

grexe
Copy link

@grexe grexe commented Jan 12, 2016

sorry, for simplicity's sake, I didn't create branches for the separate projects, if you're fine with it, please merge.

@ANierbeck
Copy link
Member

actually, no it's not ok.
first of all I don't think it's ok to commit a prepare release
second we demand to have jira issues for each commit, with associated jira issue number to the commit.
so actually I'd rather have an associated commit to each jira issue.
The corresponding Jira can be found here:
https://ops4j1.jira.com/projects/PAXTIPI/issues/PAXTIPI-36?filter=allopenissues
if you have some more questions, don't hesitate to ask at the ops4j googlegroups:
https://groups.google.com/forum/#!forum/ops4j
To release those modules you need to make sure you have an account at oss.sonatype.org and those modules are based on the latest pax-tipi master module (which is 1.3.0 right now)

regards, Achim

P.S. thanks for contributing :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants