From konversation-devel Tue Sep 22 19:32:33 2020 From: Eike Hein Date: Tue, 22 Sep 2020 19:32:33 +0000 To: konversation-devel Subject: Re: Getting Konversation releases rolling again (offering myself as release manager) Message-Id: <75CA849D-FC0C-4353-9C10-DF676E6F3296 () kde ! org> X-MARC-Message: https://marc.info/?l=konversation-devel&m=160080316809757 MIME-Version: 1 Content-Type: multipart/mixed; boundary="------1LOE5YMHWHIK5U4ZYWYMUKW1WPO9UK" ------1LOE5YMHWHIK5U4ZYWYMUKW1WPO9UK Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Friedrich, Sorry for the late reply :) My feedback is positive as well=2E Thank you f= or the offer, I would also gladly accept=2E As far as I know master should be reeleasable=2E The Qt Quick branch may h= ave a few fixes I should look into porting back to master, but nothing that= should block a release=2E The Qt Quick branch is otherwise somewhat outdated vs=2E master so I would= say ignore it for now=2E Some of the work done in there is still quite dec= ent and worth dusting off some day, although it also needs porting to newer= Kirigami components which since have become available=2E Who knows, maybe the new activity you incite will cause us to become activ= e again in turn! Cheers, Eike On September 20, 2020 1:12:04 PM GMT+02:00, "Friedrich W=2E H=2E Kossebau"= wrote: >Thanks for replies, Peter & Bernd=2E So far only positive feedback :), >thus am=20 >slowly starting to prepare my work=2E >Still waiting for reply from Eike though as well, given he has been at >least=20 >release manager before :) > >Am Donnerstag, 17=2E September 2020, 18:22:31 CEST schrieb Friedrich W=2E >H=2E=20 >Kossebau: >> My rough plan would be this: >> 1=2E Get some 1=2E7=2E6 out ASAP to have all the translation updates (a= nd >few >> fixes) finally arrive at users >> 2=2E Prepare master branch to be ready for branch & release >> 3=2E Propose Konversation for inclusion in Release Service for 20=2E12 >> 4=2E Make sure Konversation is fully integrated in Release Service >cycle >> 5 Profit and pull out again after first RS releases :) > >Today started to use self-built Konversation from latest 1=2E7 branch >(using=20 >German translation catalog), to dog-feed myself what I hope we can >release=20 >soonish as 1=2E7=2E6=2E Not being someone using all bells & whistles of w= hat >can be=20 >done with IRC, but at least I cover my daily plain use cases for >testing=2E > >What branches/version/packages is everyone else using? > >So unless there are objections (and once Eike has also replied) I would >see to=20 >target > Monday, September 28th, >as 1=2E7=2E6 release date=2E Sounds good? > >And have that as last release from that branch, unless grave bugs are=20 >reported, especially regressions that have made it into the codebase in >the 2=20 >years since 1=2E7=2E5=2E > >The next days I will see to make sure the release is done in the >tradition of=20 >the previous releases, like updating & adding an entry to=20 >konversation=2Ekde=2Eorg=2E >To start, who is in charge of that website? Would I be the one to add >the new=20 >info there? If so, who could give me access?=20 > >Cheers >Friedrich --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E ------1LOE5YMHWHIK5U4ZYWYMUKW1WPO9UK Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Friedrich,

Sorry for the late reply :) M= y feedback is positive as well=2E Thank you for the offer, I would also gla= dly accept=2E

As far as I know master should be reeleasable=2E The Q= t Quick branch may have a few fixes I should look into porting back to mast= er, but nothing that should block a release=2E

The Qt Quick branch i= s otherwise somewhat outdated vs=2E master so I would say ignore it for now= =2E Some of the work done in there is still quite decent and worth dusting = off some day, although it also needs porting to newer Kirigami components w= hich since have become available=2E

Who knows, maybe the new activit= y you incite will cause us to become active again in turn!

Cheer= s,
Eike

On September 20, 2020 1:12:04 = PM GMT+02:00, "Friedrich W=2E H=2E Kossebau" <kossebau@kde=2Eorg> wro= te:

Thanks for replies, Peter & Bernd=2E So far only=
 positive feedback :), thus am 
slowly starting to prepare my work=2EStill waiting for reply from Eike though as well, given he has been at lea=
st 
release manager before :)

Am Donnerstag, 17=2E September 2020=
, 18:22:31 CEST schrieb Friedrich W=2E H=2E 
Kossebau:
My rough plan would be this:
1=2E Get=
 some 1=2E7=2E6 out ASAP to have all the translation updates (and few
fi=
xes) finally arrive at users
2=2E Prepare master branch to be ready for =
branch & release
3=2E Propose Konversation for inclusion in Release =
Service for 20=2E12
4=2E Make sure Konversation is fully integrated in R=
elease Service cycle
5  Profit and pull out again after first RS release=
s :)

Today started to use self-built Konversation from =
latest 1=2E7 branch (using 
German translation catalog), to dog-feed mys=
elf what I hope we can release 
soonish as 1=2E7=2E6=2E Not being someon=
e using all bells & whistles of what can be 
done with IRC, but at l=
east I cover my daily plain use cases for testing=2E

What branches/v=
ersion/packages is everyone else using?

So unless there are objectio=
ns (and once Eike has also replied) I would see to 
target
    Monday=
, September 28th,
as 1=2E7=2E6 release date=2E Sounds good?

And h=
ave that as last release from that branch, unless grave bugs are 
report=
ed, especially regressions that have made it into the codebase in the 2 years since 1=2E7=2E5=2E

The next days I will see to make sure the =
release is done in the tradition of 
the previous releases, like updatin=
g & adding an entry to 
konversation=2Ekde=2Eorg=2E
To start, who=
 is in charge of that website? Would I be the one to add the new 
info t=
here? If so, who could give me access? 

Cheers
Friedrich

<=
br>

--
Sent from my Android device with K-9= Mail=2E Please excuse my brevity=2E ------1LOE5YMHWHIK5U4ZYWYMUKW1WPO9UK--