Re: [discussion] NFR and Bug updates that are released singly
On 12/7/2014 3:59 AM, Dave Liquorice wrote: Ultimatey it's the sort of thing that ought to be completely automagic. Starting from when yum spots a new update being available or perhaps better part of a script that makes the update available. I see that there might be scripts about that already do some of these functions. Exactly. I was doing this the hard way at http://wellsi.homeip.net/rnotes/sme9/9bugreport.html (currently empty) which tracked RPMs and Bugs generating release notes along the way. I'll try to get the above link useful again at least for a few months until it can be deprecated. Now that all the architecture is all on koozali servers and there is effort being put into infrastructure I see that the release process should be fully automated apart from the Go/NoGo decision which would be taken by the release manager. As I am limited in what I can do now, I would like to help setting this up at least in terms of detailing what was done and providing the scripts that I had in as much as they are useful. Dave I am sure that the community would love your help as you described in your post - it seems very do-able. Ian ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/
Re: [discussion] NFR and Bug updates that are released singly
Indeed, hats off! FYI: This page http://wiki.contribs.org/SME_Server_recent_fixes Show a list of SME core packages issues that: 1. have been confirmed and are being worked on 2. Have been fixed and closed both depending on status and resolution and since release of the latest ISO The red line(s) are bugs set with a urgency for the bug is service effecting or dangerous. (This can only be set by a bug Marshall). Once I get the queries right that is :-) And once it is right, you can refer to the page in announcements if you like. HTH -HF On 12/05/2014 09:44 PM, Terry Fage wrote: Hi First off, kudos to you Daniel your response efforts would do a paramedic proud. Question. NFRs like Bug 8717 and 8718 and bug fixes in the pipeline for pop3 TLS and others like 8714, once verified will hit the mirrors asap. Do I do a individual release announcement for each update as it is processed or say do one that covers the half dozen or so that will be done over a couple of days. I can see that some have an urgency that users would appreciate having a heads up on a fix on the way. Perhaps just a note in that particular Bug or forum post with the Changelog note.. What is the consensus? ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/ ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/
Re: [discussion] NFR and Bug updates that are released singly
Thanks HF will certainly use that link. I am more concerned with an update that is released that fixes a particular issue, like the Thunderbird one now. The package will be released as soon as it is verified, it may not be a formal verification as such. So does a release announcement need to be made for that single update OR is a simple changelog note in the Bug or forum a more appropriate response and obviousle more directed. Daniel has certainly hit the ground running :-) ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/
Re: [discussion] NFR and Bug updates that are released singly
historically, Ian would announce each and every updated e-smith-*/smeserver-* RPM on the ML. On 12/05/2014 10:13 PM, Terry Fage wrote: Thanks HF will certainly use that link. I am more concerned with an update that is released that fixes a particular issue, like the Thunderbird one now. The package will be released as soon as it is verified, it may not be a formal verification as such. So does a release announcement need to be made for that single update OR is a simple changelog note in the Bug or forum a more appropriate response and obviousle more directed. Daniel has certainly hit the ground running :-) ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/ ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/
Re: [discussion] NFR and Bug updates that are released singly
On 6/12/2014 8:20 AM, Hsing-Foo Wang wrote: historically, Ian would announce each and every updated e-smith-*/smeserver-* RPM on the ML. OK then I need to keep that same SOP. I can also see the value in posting something to the forums, far more watch it than the MLs ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/
Re: [discussion] NFR and Bug updates that are released singly
I used to that as well at one time. There was no feedback if it was worthwhile so I stopped when I became too busy. There were no comments about not having it in the forum. I used to send one email for all the upstream updates - i.e. the ones that you get anyway from upstream. Then for each package that a dev produces I would send one. I'll look at getting the scripts out soon. Ian -Original Message- From: discussion-boun...@lists.contribs.org [mailto:discussion-boun...@lists.contribs.org] On Behalf Of Terry Fage Sent: Friday, December 5, 2014 5:19 PM To: discussion@lists.contribs.org Subject: Re: [discussion] NFR and Bug updates that are released singly On 6/12/2014 8:20 AM, Hsing-Foo Wang wrote: historically, Ian would announce each and every updated e-smith-*/smeserver-* RPM on the ML. OK then I need to keep that same SOP. I can also see the value in posting something to the forums, far more watch it than the MLs ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/ ___ Discussion about project organisation and overall direction To unsubscribe, e-mail discussion-unsubscr...@lists.contribs.org Searchable archive at http://lists.contribs.org/mailman/public/discussion/
