Since you intend this for major releases only, I can't see why it would be a terrible problem, but there still may need to be some cleanup at the last minute. Little trifles and such.
On 2/25/15, Silver Lion <[email protected]> wrote: > That's going to be a problem because I never know exactly how my office > hours work pend out... That's why I asked for a little more time for > preparation... Honestly speaking I hate to knitt everything with a hot > needle (german saying for doing everything very short before it's going > to be too late ;) ) > > But why don't we check the workflows after 15.04 has been released? then > we've got a little more time to re-configure if necessary. > > Cheers > Silver > > Am 26.02.2015 um 00:29 schrieb Walter Lapchynski: >> Well here's the problem I face: I cannot know any sooner than Tuesday >> before release (Thursday) what the state of the images are. In fact, >> sometimes (14.04.2) I don't even know until day of release!!!! >> >> I could try to make sure testing is done on dailies a week before, but >> I still won't be able to say anything definite because there's lots of >> opportunity for changes while we wait. The images are frozen come >> Tuesday. >> >> At least for non-release milestones, that's the case. Beyond that, it >> shouldn't be too difficult. >> >> I hope you can understand. >> >> >> On Wed, Feb 25, 2015 at 2:52 PM, Silver Lion <[email protected]> >> wrote: >>> Good evening folks, >>> >>> Finally I was able to fullfill wxl's request to get my task-list (seen >>> here >>> below as text version) onto the wiki => >>> https://wiki.ubuntu.com/silverlion/PressTemplate >>> >>> I'll also be working on a draft for an offline version for the >>> announcement >>> of 15.04. >>> >>> I'd like QA & Wiki / Docs to consider this list (link see above) as >>> effective as of now. >>> >>> @Wiki & Docs: Please copy this link above to the appropriate places and >>> have >>> the mentioned pages in the wiki ready for me asap. >>> >>> @wxl: I'd appreciate it if you could update the questionaire not only >>> one >>> day prior to release. We (aka comms) need to have time to prepare >>> everything >>> so _1 Week_ prior to release everything must be ready for us in order to >>> look professional. >>> >>> Thanks in advance to everybody for your attention ;) >>> >>> Silver >>> >>> Am 05.02.2015 um 01:13 schrieb Gustavo Silva: >>>> >>>> If this goes through, please let me know by the end of the week and >>>> I'll >>>> assign my share of tasks to the team and will take care of that asap. >>>> >>>> In my opinion, it is a +1 for this. >>>> >>>> 2015-02-04 23:08 GMT+00:00 Silver Lion <[email protected]>: >>>> >>>>> Hey there folks! >>>>> I've been asked by wxl and phillw to put together a draft for what's >>>>> needed in my personal opinion to prepare a proper Public-Relations of >>>>> Lubuntu. >>>>> >>>>> First of all: in Public-Relations it's crucial to be “the first” on >>>>> the >>>>> market. Meaning: The earlier we start putting our announcement >>>>> together >>>>> the sooner we're on the screens of online media and other interested >>>>> parties like LoCos. >>>>> >>>>> That's why we should start very early in the process to gather >>>>> informations etc. >>>>> Because the earlier we start, the less we've got to do on release >>>>> day... >>>>> >>>>> I've prepared a list and divided it in 5 chapters. In each “chapter” >>>>> I've written some questions to give you in overview what might be >>>>> interesting and necessary for me to prepare the statement at the end. >>>>> >>>>> ##################################################################### >>>>> 1. Feature – Definition – Freeze >>>>> (a) What's going to be new in the upcoming release? >>>>> (b) What kind of updates are we doing? >>>>> (c) Are we changing anything special? (for example: change of the DE → >>>>> LXQt?) >>>>> (d) Are we planning anything special like a contest for wallpapers >>>>> etc.? >>>>> (e) What will be our main goal for this release? >>>>> 2. Feature-Freeze >>>>> (a) “Half-Time”-Report: How are things going? Anything unexpected >>>>> during >>>>> the latest period? >>>>> (b) The Updates we planned to include: Are they all going to come? If >>>>> not → Why not?! >>>>> 3. Final Beta Freeze (1 Month PRIOR to Release Day!!!) >>>>> (a) Statement by Release-Manager & Head of Dev: Did everything go as >>>>> expected? >>>>> (b) Did we have to skip any planned things from #1? >>>>> (c) What's the latest “news” about the release? >>>>> (d) What can users expect from this release we're talking about? >>>>> >>>>> 4. One Week before Release >>>>> (a) Prepare wiki-page for online and offline press-statement¹ >>>>> (b) copy prepared announcement into wiki-area (which need to be >>>>> prepared >>>>> by wiki team!) >>>>> (c) upload PDF for LoCos and other interested parties to download >>>>> >>>>> 5. At Release Day >>>>> (a) Let prepared wiki-page (from task 4a) go “live” >>>>> (b) link to it via social media (Twitter, Facebook Page, Facebook >>>>> Group, >>>>> G+ Community) >>>>> >>>>> ####################################################################### >>>>> >>>>> Please let me know if anything else is needed your you've got any >>>>> further questions on that subject. >>>>> >>>>> Regards, >>>>> Silver! >>>>> >>>>> -- >>>>> Mailing list: https://launchpad.net/~lubuntu-admins >>>>> Post to : [email protected] >>>>> Unsubscribe : https://launchpad.net/~lubuntu-admins >>>>> More help : https://help.launchpad.net/ListHelp >>>>> >>>> >>>> >>>> >>> >> >> >> > -- Mailing list: https://launchpad.net/~lubuntu-admins Post to : [email protected] Unsubscribe : https://launchpad.net/~lubuntu-admins More help : https://help.launchpad.net/ListHelp
