some love for jgitflow-maven-plugin

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Answered
    • None
    • Component/s: None
    • None

      Hi,

      I'm opening this issue in know that this is not the project dealing with the 'jgitflow-maven-plugin', still I feel the need to get some attraction by Atlassian for this issue and have not found a place where this kind of question would fit:

      The 'jgitflow-maven-plugin' is hosted on Bitbucket by Atlassian [1}. Unfortunate it has not have any activity by an Atlassian employee since 2015. At that time some PRs have been merged, but a release has never been done with the last changes.

      Checking for support questions regarding jgitflow on the Atlassian site [2], shows that even though new questions come in, none has been answered since 2014.

      It seems Atlassian has lost interest on this tool/library - that's fair, no big deal. But the incoming PRs [3] also show that the community is still interested in it.

      Therefore I ask you to forward this issue to anyone within Atlassian who might be interested to find a solution and help the community to move forward with 'jgitflow'. Please think about opening/transferring the repo to the community so someone else could do at least a release with the latest changes/fixes not released yet.

      /Domi

      ...sorry for the misplacement! 

      [1] https://bitbucket.org/atlassian/jgit-flow

      [2] https://community.atlassian.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&q=jgitflow

      [3] https://bitbucket.org/atlassian/jgit-flow/pull-requests/ 

       

      p.s. yes I can do a private release, that's what we did - but I know others have the same issue and help is not hard to provide.

       

            Assignee:
            Unassigned
            Reporter:
            Dominik Bartholdi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: