I totally agree! I just dont see it happen. Its been almost 3 years since 
last release.

I don't feel comfortable with taking descisions on what PR:s to merge. How 
much testing to do before release. Setting coding standard...

Den måndag 1 juni 2015 kl. 06:17:13 UTC+2 skrev Richard Bywater:
>
> -1 for creating a forked version. If there is an issue with the existing 
> plugin I'd much rather see it being worked on to bring it up to standard 
> rather than creating a completely separate plugin which could lead to 
> confusion amongst users.
>
> My 2 cents...
> Richard
>
> On 10:30AM, Mon, 1/06/2015 Tomas Bjerre <tomas.b...@gmail.com 
> <javascript:>> wrote:
>
>> Plugin Name: Violations Reboot
>> My GitHub username: tomasbjerre
>> Existing repo: https://github.com/tomasbjerre/violations-reboot-plugin
>> Doc: https://github.com/tomasbjerre/violations-reboot-plugin
>>
>> This is very similar to Violations (
>> https://github.com/jenkinsci/violations-plugin). The Violations plugin 
>> has been poorly maintained lately. Alot of features, and bug fixes, in PR:s 
>> are left unmerged. Which is very sad since its a very nice plugin!
>>
>> What I have done here is:
>> * Fork Violations
>> * Added LICENSE, README and a coding standard (for Eclipse)
>> * Reformatted the code according to the coding standard (will make it 
>> much easier to merge PR:s in the future)
>>
>> I think the major reason why PR:s are not merged in Violations is because 
>> of the heavy testing job that should be carried out before a release. I, 
>> therefore, suggest releasing this (much more unstable) reboot so that 
>> existing users can continue using the stable Violations release while 
>> Reboot becomes more stable. I'd like to implement better automated testing 
>> and create releases after more or less every new feature.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/ba38fabe-ff19-4828-a737-d2320ea5681f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/ba38fabe-ff19-4828-a737-d2320ea5681f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/63f7a528-5548-412b-a885-5b8bb38ffc1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to