Hi Ryan, Sorry to hear you are having trouble building the project. Can you share specific Maven failures to help us diagnose?
The versioning may be unusual, so let me try to clarify: 1.8.0 is the most recently released version of the software [1]. 1.7.1, 1.7.0, 1.6.0, etc. are previously released versions. The code at that point in time can be found by using the git tags (i.e. rel-1.8.0) [2]. If you have the git project cloned, you can switch to any tag or branch and build that specific release, or download the artifacts from the archive listing [3]. The releases aren’t supported indefinitely though, so we encourage users to upgrade when possible to the most recent versions. 1.9.0-SNAPSHOT is the current “master” version, as it allows development on the core codebase after 1.8.0 was released. 1.9.0 has not been released, nor even discussed for vote and release process [4] yet. In the coming weeks/months, that discussion will occur, and given community buy-in, that release will have a release candidate proposed, voted on, and hopefully released. We follow semantic versioning [5], so major, minor, and bug fix release numbers all have a specific meaning and context. The Jira ticket process is mostly manual. If a ticket has an “In Progress” status, someone has likely begun working on that issue. If it is not assigned to anyone, you can comment on the Jira asking if anyone has started or is currently working on it. Sometimes people start on an issue and then priorities change or they move to something else, so it’s fair to ask on anything you’re not sure of. If a PR is linked and the PR is recent, the user probably just didn’t update the Jira assignee. If the PR is stale (old, not rebased against master, has outstanding requests from reviewers that have not been addressed), you can also work on it, but a comment indicating that will help reduce duplication of efforts. If you have not already seen them, the Getting Started [6], Contributor Guide [7], and Developer Guide [8] documents are very helpful for new contributors. If anything in there is unclear, please feel free to reply here. If you can, offering improvements or clarity via a PR is even better — things change over time, and concretely documenting our process to help everyone is a big responsibility, but something we are committed to. Every time a new contributor tries to join, we get the best possible feedback on the current process. Hope this helps you get involved. [1] https://nifi.apache.org/download.html [2] https://github.com/apache/nifi/tree/rel/nifi-1.8.0 [3] https://archive.apache.org/dist/nifi/ [4] https://www.apache.org/legal/release-policy.html [5] https://semver.org/ [6] https://nifi.apache.org/docs/nifi-docs/html/getting-started.html [7] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide <https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide> [8] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jan 23, 2019, at 3:56 PM, Ryan Withers <[email protected]> wrote: > > To whom it may concern, > > So my goal is to begin making contributions to the nifi product. Right > now I'm just trying to build the product from source and having some > difficulty. > > I've listed out the branches associated with the following repository (git > clone https://git-wip-us.apache.org/repos/asf/nifi.git) > > I don't see any support branches related to 1.8.0 and it seems like the > master branch has already been bumped to 1.9.0. I recognize that if I > want to contribute a change it likely has to be done against 1.9.0 rather > than 1.8.0 but I've been having build issues against 1.9.0. However, I did > have a successful build against support/nifi-1.7.x. > > Once I have the appropriate version of the source compiling I plan to pick > an issue from your jira instance which I've been reading through. Then > perform a modification and walk through the pull request process. With > Jira I'm noticing there are some stories that say "in progress" or "patch > available" but none of them have an assignee. Is the transition between > these states driven by automation or are people manually updating the > stories in Jira? > > Thanks in advance, > > Ryan > > -- > Ryan Withers > Senior Software Developer / Analyst > > http://www.linkedin.com/in/ryanwithers
