Currently, 13 issues are open for milestone "SMW 3.0.0" [1]. How about adding a new tag "blocker" and mark those issues that are really mandatory to be solved before the next release. All others could go to 3.0.1 or 3.1?
[1] https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22SMW+3.0.0%22 Am 13.09.2018 um 11:20 schrieb Jeroen De Dauw: > Hey, > > I am rather unhappy that the volunteer nature of the work keeps being brought > up as a reply to the release process not being good. Yes, you cannot > reasonably demand that a volunteer invests more of their time, or that they > spend it in a certain way. The issue here is a poor release process, which in > my view is quite orthogonal. > > There are also many stakeholders beyond James that are affected, and they are > not irrelevant. Most noticeably the users of the software, which are not > getting access to long developed features. There are also the other people > that contribute to the software. Speaking for myself, I am not enthusiastic > at all to contribute to a project if it is not clear my improvements will see > the light of day in a reasonable time frame, and things I previously > contributed have been sitting in the dark for over a year. Such a situation > is also not appealing to potential contributors. > > Some time ago I started work on adding visual editing to the Maps extension, > to be released as version 6.0. At some point I ran out of time having gotten > only part of the way there. As there was already useful functionality added, > I decided to just release that rather than potentially keeping it unavailable > for months. So the users win. And contributors to Maps know that their > contributions are likely to be released within a week or two. > > The same could have been done for SMW 3.0 long ago. Instead, new features > have kept being added to the milestone. > > Now if James does not want to spend time on doing a release that is his > decision. Should it also be his decision to block any release form happening > because he is the primary contributor, even if that throws all other > stakeholders under the buss? I don't think so. And yes, that is what is > happening. I have offered spending time on doing a 3.0 release in the past, > always getting a "you can't do this and don't rush me" type of reply. > > Cheers > > -- > Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw > Software Crafter | Speaker | Student | Strategist | Contributor to Wikimedia > and Open Source > ~=[,,_,,]:3 > > > > > _______________________________________________ > Semediawiki-devel mailing list > Semediawiki-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > -- ________________________________________________ semantic::core go! Free Enterprise Class MediaWiki Distribution https://semantic.wiki/de/core _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
