The first big problem here is the lack of answer. I am asking to developers
how we can process to avoid another blocking situation.
I will try to add information and not to rephrase.
I want people to let me know how do they do to know there is something
urgent to do on Koha dev.
I do not see the point to sign-off and QA trivial string patches when
blockers are in the queue for weeks (no need to tell me everybody does what
do they want, I still agree with that).
If you are a developer and you want to help, what do you do? Where do you
do? How to you prioritize your work? Are you all picking bugs randomly in
We need to all agree on a "place to go" to know what need to be done. I
On Wed, 9 Aug 2017 at 10:30 Marcel de Rooy <m.de.r...@rijksmuseum.nl> wrote:
> > As written in it, *without an agreement we will find all together, no
> new enhancements are going *
> *> to be pushed*.
> I am not sure which 'agreement' you are seeking here. The time for a
> critical bug to become part of master, just depends on involvement of
> people and the publicity made for it via IRC and mailing lists. If it takes
> more time, nobody should complain, because we can all participate.
> But the approach of vetoing enhancements is imo contraproductive and will
> only scare people away. So I just hope that you change your mind about that
> course. We cannot force people to participate.
> If you are not pushing enhancements btw, it does not make much sense to QA
> them too. Same for testing or signing them off. Note if we pile up
> everything in PQA, we will have a lot of rebasing and we will create some
> new bugs in that process.
> Koha-devel mailing list
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
Koha-devel mailing list
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/