[JBoss JIRA] (JBIDE-24397) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [build-sites]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24397?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-24397.
------------------------------
Resolution: Rejected
Closing - nothing to do.
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [build-sites]
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-24397
> URL: https://issues.jboss.org/browse/JBIDE-24397
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: updatesite
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [build-sites]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-build-sites at https://github.com/jbosstools/jbosstools-build-sites
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "8a0ffd" is the last common ancestor of master and jbosstools-4.4.x
> 8a0ffd is 7 commits ago in branch jbosstools-4.4.x
> 8a0ffd is 6 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: JBIDE-24240-EBZ-511793-add-org.eclipse.wst.common.modulecore-patch-feature-to-JBT-Abridged-category-CoreTools-and-WebTools-too https://github.com/jbosstools/jbosstools-build-sites/commit/a1fd4ed0f5a95...
> ** possible match: https://github.com/jbosstools/jbosstools-build-sites/commit/fefbbbf29ca0c...
> *** Inspect the difference between the two patches: http://sprunge.us/iaPA
> * missing: bump-master-to-4.5.0 https://github.com/jbosstools/jbosstools-build-sites/commit/d1fd2abdaf3e0...
> * missing: JBIDE-23960-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-build-sites/commit/d859d58008d12...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for build-sites task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24397) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [build-sites]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24397?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24397:
------------------------------------
Maintenance was prolly done in 2 commits but in master I squashed and merged them.
So your tool is getting confused because the "possible match" doesn't work when it's 1 commit matching a combined pair of commits in the other branch.
When you look for a matching commit across the branches, could you look not at the single commits but at the diff between N and N-1, then also N-2?
Or a concrete example:
* https://github.com/jbosstools/jbosstools-build-sites/commits/jbosstools-4...
** https://github.com/jbosstools/jbosstools-build-sites/commit/f545b2bae44c9...
** https://github.com/jbosstools/jbosstools-build-sites/commit/fefbbbf29ca0c...
vs.
* https://github.com/jbosstools/jbosstools-build-sites/commits/master
** https://github.com/jbosstools/jbosstools-build-sites/commit/a1fd4ed0f5a95...
Or compare these:
https://github.com/jbosstools/jbosstools-build-sites/compare/a18246ec97cc...
vs.
https://github.com/jbosstools/jbosstools-build-sites/commit/a1fd4ed0f5a95...
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [build-sites]
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-24397
> URL: https://issues.jboss.org/browse/JBIDE-24397
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: updatesite
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [build-sites]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-build-sites at https://github.com/jbosstools/jbosstools-build-sites
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "8a0ffd" is the last common ancestor of master and jbosstools-4.4.x
> 8a0ffd is 7 commits ago in branch jbosstools-4.4.x
> 8a0ffd is 6 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: JBIDE-24240-EBZ-511793-add-org.eclipse.wst.common.modulecore-patch-feature-to-JBT-Abridged-category-CoreTools-and-WebTools-too https://github.com/jbosstools/jbosstools-build-sites/commit/a1fd4ed0f5a95...
> ** possible match: https://github.com/jbosstools/jbosstools-build-sites/commit/fefbbbf29ca0c...
> *** Inspect the difference between the two patches: http://sprunge.us/iaPA
> * missing: bump-master-to-4.5.0 https://github.com/jbosstools/jbosstools-build-sites/commit/d1fd2abdaf3e0...
> * missing: JBIDE-23960-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-build-sites/commit/d859d58008d12...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for build-sites task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4328) Move 'Detection is in progress' indicator in the middle of the screen and make it easy to see
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBDS-4328?page=com.atlassian.jira.plugin.... ]
Catherine Robson commented on JBDS-4328:
----------------------------------------
Looks good - can you increase the opacity of the white background behind it a bit more? Probably 80 or 90% opacity is what you would want here - the text is too hard to read otherwise.
> Move 'Detection is in progress' indicator in the middle of the screen and make it easy to see
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4328
> URL: https://issues.jboss.org/browse/JBDS-4328
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.4.0.AM2, 10.4.0.GA
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: ui
> Attachments: detection-spinner.png
>
>
> With scrolling in place it is not easy to notice that detection is in progress. It should be always in the middle of the windows, it should be bigger and easy to see.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24408) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24408?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24408:
--------------------------------
Fix Version/s: 4.4.4.Final
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-24408
> URL: https://issues.jboss.org/browse/JBIDE-24408
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives, jmx, server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [Server]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-server at https://github.com/jbosstools/jbosstools-server
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "e4ea00" is the last common ancestor of master and jbosstools-4.4.x
> e4ea00 is 37 commits ago in branch jbosstools-4.4.x
> e4ea00 is 34 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: JBIDE-23869-consume-jolokia-snapshot-with-our-classcast-fix https://github.com/jbosstools/jbosstools-server/commit/a4b6166f61da59e22a...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/a910e333f88ba38c5e...
> *** Inspect the difference between the two patches: http://sprunge.us/QJDU
> * missing: JBIDE-24233-force-connections-for-wf8-and-above-to-use-http-remoting-protocol https://github.com/jbosstools/jbosstools-server/commit/b18d91e68861956074...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/b5e4c0d194f5103ee0...
> *** Inspect the difference between the two patches: http://sprunge.us/YhRR
> * missing: JBIDE-24138-fix-test-case-for-oxygen-api-changes https://github.com/jbosstools/jbosstools-server/commit/569d7acdd38b64af5d...
> * missing: JBIDE-24138-Implement-QueryMBeans-for-JolokiaMBeanServerConnection https://github.com/jbosstools/jbosstools-server/commit/cb974c9f9791a32a77...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/2c02ace0653c097733...
> *** Inspect the difference between the two patches: http://sprunge.us/XUZe
> * missing: Bump-root-pom-so-update-site-appears-correct https://github.com/jbosstools/jbosstools-server/commit/f2848a0506a76b1fe8...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/3dd7251c190dce7a6a...
> *** Inspect the difference between the two patches: http://sprunge.us/SRMR
> * missing: JBIDE-22717-Remvoe-Event-Log https://github.com/jbosstools/jbosstools-server/commit/d82e9f9b649b4cca27...
> * missing: Failing-Unit-Tests-secure-storage-related-MASTER-ONLY https://github.com/jbosstools/jbosstools-server/commit/d84d2b1278ea946659...
> * missing: JBIDE-24043-upversion-master https://github.com/jbosstools/jbosstools-server/commit/e3a065a0ea76caae92...
> * missing: JBIDE-24029-JBIDE-24031 https://github.com/jbosstools/jbosstools-server/commit/778cc2dc271e5fef9b...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/82d51ba3185088bc21...
> *** Inspect the difference between the two patches: http://sprunge.us/RMNB
> * missing: JBIDE-23956-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-server/commit/442b33bc7e241b7e96...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24408) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24408?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-24408.
-------------------------------
Resolution: Done
Shockingly, this is all 100% clean. I'm actually amazed by that.
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Server]
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-24408
> URL: https://issues.jboss.org/browse/JBIDE-24408
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives, jmx, server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [Server]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-server at https://github.com/jbosstools/jbosstools-server
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "e4ea00" is the last common ancestor of master and jbosstools-4.4.x
> e4ea00 is 37 commits ago in branch jbosstools-4.4.x
> e4ea00 is 34 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: JBIDE-23869-consume-jolokia-snapshot-with-our-classcast-fix https://github.com/jbosstools/jbosstools-server/commit/a4b6166f61da59e22a...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/a910e333f88ba38c5e...
> *** Inspect the difference between the two patches: http://sprunge.us/QJDU
> * missing: JBIDE-24233-force-connections-for-wf8-and-above-to-use-http-remoting-protocol https://github.com/jbosstools/jbosstools-server/commit/b18d91e68861956074...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/b5e4c0d194f5103ee0...
> *** Inspect the difference between the two patches: http://sprunge.us/YhRR
> * missing: JBIDE-24138-fix-test-case-for-oxygen-api-changes https://github.com/jbosstools/jbosstools-server/commit/569d7acdd38b64af5d...
> * missing: JBIDE-24138-Implement-QueryMBeans-for-JolokiaMBeanServerConnection https://github.com/jbosstools/jbosstools-server/commit/cb974c9f9791a32a77...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/2c02ace0653c097733...
> *** Inspect the difference between the two patches: http://sprunge.us/XUZe
> * missing: Bump-root-pom-so-update-site-appears-correct https://github.com/jbosstools/jbosstools-server/commit/f2848a0506a76b1fe8...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/3dd7251c190dce7a6a...
> *** Inspect the difference between the two patches: http://sprunge.us/SRMR
> * missing: JBIDE-22717-Remvoe-Event-Log https://github.com/jbosstools/jbosstools-server/commit/d82e9f9b649b4cca27...
> * missing: Failing-Unit-Tests-secure-storage-related-MASTER-ONLY https://github.com/jbosstools/jbosstools-server/commit/d84d2b1278ea946659...
> * missing: JBIDE-24043-upversion-master https://github.com/jbosstools/jbosstools-server/commit/e3a065a0ea76caae92...
> * missing: JBIDE-24029-JBIDE-24031 https://github.com/jbosstools/jbosstools-server/commit/778cc2dc271e5fef9b...
> ** possible match: https://github.com/jbosstools/jbosstools-server/commit/82d51ba3185088bc21...
> *** Inspect the difference between the two patches: http://sprunge.us/RMNB
> * missing: JBIDE-23956-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-server/commit/442b33bc7e241b7e96...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Server task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24394) For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Central]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24394?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-24394.
-------------------------------
Resolution: Done
These all seem 100% ok.
> For JBIDE 4.4.4.Final: Find Missing Commits From master for jbosstools-4.4.x [Central]
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-24394
> URL: https://issues.jboss.org/browse/JBIDE-24394
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Jeff MAURY
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [Central]: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x.
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied.
> If there are no commits listed below, please close (do not resolve) this issue.
> Otherwise:
> 1) Click on each link below.
> 2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
> 3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match.
> 4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in.
> 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
> 6) When all complete, please close (do not resolve) this issue.
>
> Folder: jbosstools-central at https://github.com/jbosstools/jbosstools-central
> Searching for commits present in master and missing from jbosstools-4.4.x
> Commit hash "27a46b" is the last common ancestor of master and jbosstools-4.4.x
> 27a46b is 6 commits ago in branch jbosstools-4.4.x
> 27a46b is 8 commits ago in branch master
> Commits missing from jbosstools-4.4.x that are in master:
> * missing: bump-maven-examples-and-central-from-x.y.3-to-x.y.100-to-fix-build-breakages-in-master-branch-seriously-is-no-one-test-building-locally-w.t.f https://github.com/jbosstools/jbosstools-central/commit/d5ce47d7e02ded9d5...
> * missing: features-too-because-4.4.x-branch-has-2.1.4-and-1.8.4-bump-master-to-2.1.100-and-1.8.100 https://github.com/jbosstools/jbosstools-central/commit/1b6f259eee3d6733b...
> * missing: because-4.4.x-branch-has-2.1.4-and-1.8.4-bump-master-to-2.1.100-and-1.8.100 https://github.com/jbosstools/jbosstools-central/commit/df726ac172345423b...
> * missing: JBIDE-24133-org.jboss.tools.runtime.reddeer.-396 https://github.com/jbosstools/jbosstools-central/commit/6a40e1fa413dbc8a6...
> * missing: JBIDE-23948-comment-bump-up-to-parent-pom-version-4.5.0.AM1-SNAPSHOT-close https://github.com/jbosstools/jbosstools-central/commit/1e09f6561099ec443...
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Central task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months