https://github.com/jenkins-infra/jenkins.io/pull/2734 .
Target publishing date is Jan 06. All suggestions and reviews will be 
appreciated, thanks!

On Tuesday, December 31, 2019 at 12:48:13 AM UTC+1, Oleg Nenashev wrote:
>
> Thanks Mark! I will make sure to incorporate it (or at least the most of 
> entries)
>
> Unfortunately I was unable to really focus on writing over the past week 
> due to personal stuff, and it is not ready for review. My blogpost queue 
> looks pretty bad, and not overcommitting is in my TODO list for the next 
> year. This New Year post, GSoC and Hacktoberfest report as the biggest 
> issue in my hall of shame. I will do my best to submit a PR for this NY 
> blogpost tomorrow
>
> Best regards,
> Oleg
>
>
> On Monday, December 30, 2019 at 3:58:35 PM UTC+1, Mark Waite wrote:
>>
>> Topics that I think should be mentioned include:
>>
>>    - Platform improvements in 2019
>>       - Java 11 support in Long Term Support releases March 2019 and 
>>       later (JEP-211 
>>       <https://github.com/jenkinsci/jep/blob/master/jep/211/README.adoc>)
>>       - Docker image added for CentOS, 
>>       - Experimental Docker image added for ARM, ppc64le, and s390x
>>    - Documentation improvements in 2019
>>       - Plugin documentation inside their GitHub repository can be 
>>       automatically published to plugins.jenkins.io
>>       -  Over 60 blog posts
>>       - Wiki exporter tool to speed the transition from the Wiki to 
>>       jenkins.io documentation
>>       - Social media connection improvements for jenkins.io 
>>       documentation (opengraph is great)
>>       - Search engine optimization improvements for plugins.jenkins.io
>>    - Development improvements in 2019
>>       - Release drafter automates and improves release note creation for 
>>       Jenkins and many plugins
>>       - Dependabot automates and improves dependency management for many 
>>       plugins
>>       - CI pipeline tests combinations of Jenkins versions, Java 8 and 
>>       Java 11, Windows and Linux
>>    
>> I'm happy to contribute phrasing on a Google Doc if you want to start one.
>>
>> On Tue, Dec 24, 2019 at 6:13 AM Oleg Nenashev <[email protected]> wrote:
>>
>>> Hi all,
>>>
>>> I am planning to work on the traditional Jenkins New Year Blogpost (2017 
>>> <https://jenkins.io/blog/2017/12/31/new-year/>, 2016 
>>> <https://jenkins.io/blog/2016/12/31/what-a-year/>). Unfortunately we 
>>> skipped 2018, but it would be great to recover this tradition.
>>>
>>> My plan is to include...
>>>
>>>    - Stats and Events, like in 2017
>>>    - Board and Officer elections
>>>    - Outreach programs: GSoC 2019, Outreachy, CommunityBridge, 
>>>    Hacktoberfest 2019
>>>    - Best ever contributor numbers in Oct 2019
>>>    - Summaries from SIGs and sub-projects in 2019: JCasC, Pipeline, K8s 
>>>    Operator, etc.
>>>    - Emoji support in Jenkins? :D
>>>
>>> If you would like to add your highlights, please make suggestions in 
>>> this thread. I can also create a Google Doc so that we can edit the 
>>> blogpost together.
>>>
>>> Best regards.,
>>> Oleg
>>>
>>>
>>>
>>>
>>>
>>> -- 
>>> 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 [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuPeZ0mnUbd0ZO2BUTXvW3xESEp3eLD%3Dk%2B99xy6QuzA%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuPeZ0mnUbd0ZO2BUTXvW3xESEp3eLD%3Dk%2B99xy6QuzA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> -- 
>> Thanks!
>> Mark Waite
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0600a31a-38fb-428e-bf8b-509bab540b3a%40googlegroups.com.

Reply via email to