Thanks :) On 28 February 2015 at 19:42, Gustavo Silva <[email protected]> wrote:
> Hi all, > > As I've mentioned, I didn't delete any content. I did change the wrong > page though. I copied > https://wiki.ubuntu.com/Lubuntu/Marketing/Press%20Releases to > https://help.ubuntu.com/community/Lubuntu/InternalComms/Communications. > > Anyway, everything should be in place now. > > 2015-02-28 4:02 GMT+00:00 Phill Whiteside <[email protected]>: > >> Hi Silver, >> >> that does make a bit more sense to me. As you know, the pre-post release >> area already exists for 'Final'. It has had a revamp recently, but both it >> and the Press Template need to also now allow for the fact we have point >> releases of our LTS's as and when they come up. >> >> As a template for both LTS point releases and our bi-annual releases with >> their milestones it reads really good to me. I think when QA / Comms / Wiki >> can bounce this around, Gustavo and my self can set up a structure better >> suited to handle the milestone releases for both lubuntu LTS and the >> lubuntu +1. >> >> My thinking is for planning, it would be >> >> LTS, LTS.01, LTS.02, LTS.03, LTS.04 This also then needs LTS+1, LTS+1.01 >> (I think there is a one year wrap over, after which LTS+1 becomes LTS) This >> would be based upon >> https://wiki.ubuntu.com/Lubuntu/Developers/PrePostReleaseTODO But would >> need a sub page for the LTS+1 As these are only every 4 cycles, we could >> reasonably use the release names (14.04, 16.04, 18.04 ....) >> >> For desktop release it would be as we have now at >> https://wiki.ubuntu.com/Lubuntu/Developers/PrePostReleaseTODO for final >> but with sub pages for the milestones of a1, a2, b1 and b2. >> >> These are my thoughts, it is a not actually a massive amount of work to >> create this structure and once done, the system is in place also ensure we >> still never delete pages, they just move from 'current' to older. >> >> So, there you have my thoughts on how the existing system can be fine >> tuned for what we have now instead of doing last minute creation / editing >> of pages. >> >> Thoughts, please :) >> >> Phill. >> >> >> >> >> >> >> >> On 28 February 2015 at 03:04, Silver Lion <[email protected]> wrote: >> >>> Good Morning, >>> >>> well to be honest with you... that wasn't a draft, that was the original >>> release information which now gone since you moved it. >>> >>> Please reverse this asap! >>> >>> I've been refering to https://wiki.ubuntu.com/silverlion/PressTemplate >>> which contains the internal informations for the QA-Department. >>> >>> Regards >>> Silver >>> >>> Am 28.02.2015 um 02:41 schrieb Gustavo Silva: >>> >>> Silverlion, >>>> >>>> I've created an internal mechanism for us to communicate & test >>>> statements. >>>> >>>> Please visit this link: >>>> https://help.ubuntu.com/community/Lubuntu/InternalComms/Communications >>>> >>>> I haven't created all "departments" because I don't know everyone's >>>> needs. >>>> However, feel free to create stuff and add content. I've moved over your >>>> draft to Communications section. >>>> >>>> Hope this helps - And let me know if does! >>>> >>>> 2015-02-26 0:08 GMT+00:00 Phill Whiteside <[email protected]>: >>>> >>>> Hi Folks, >>>>> >>>>> Regarding https://wiki.ubuntu.com/Lubuntu/Developers/ >>>>> PrePostReleaseTODO >>>>> >>>>> if you look, you will see that the two sets of release notes >>>>> https://wiki.ubuntu.com/Lubuntu/Announcement/15.04 >>>>> and >>>>> https://wiki.ubuntu.com/VividVervet/ReleaseNotes/Lubuntu >>>>> >>>>> They both have DRAFT stamped on them. They can be edited right up to >>>>> (and >>>>> some times after release). Part of the system is that when a new >>>>> release is >>>>> a 'go' the old pages get archived and the new ones moved in to their >>>>> place >>>>> as quickly as possible, there are a few pages to archive off and then >>>>> instate the new pre-prepared ones. >>>>> >>>>> If people on this chat can keep an eye on >>>>> https://wiki.ubuntu.com/Lubuntu/Developers/PrePostReleaseTODO >>>>> It is a central list of what we need to do most prior and post release. >>>>> Feel free to add in any 'announcement' stuff you want on there. I've >>>>> concentrated on wiki pages with Gustavo and have simply added in a >>>>> section >>>>> for announcing things. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> Phill. >>>>> >>>>> >>>>> On 25 February 2015 at 23:38, Walter Lapchynski <[email protected]> >>>>> wrote: >>>>> >>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> https://wiki.ubuntu.com/phillw >>>>> >>>>> >>>> >>>> >>>> >> >> >> -- >> https://wiki.ubuntu.com/phillw >> > > > > -- > Best Regards / Obrigado e com os melhores cumprimentos, > Gustavo Silva > > *Open Economics <http://openeconomics.net>, Work Group Coordinator* > *Phonebloks <https://phonebloks.com/en>, Partnership Manager* > > -- https://wiki.ubuntu.com/phillw
-- Mailing list: https://launchpad.net/~lubuntu-admins Post to : [email protected] Unsubscribe : https://launchpad.net/~lubuntu-admins More help : https://help.launchpad.net/ListHelp
