igra-devel [mailto:calligra-devel-boun...@kde.org] On Behalf Of
Dag
Sent: 12. november 2016 10:45
To: Calligra Suite developers and users mailing list
Subject: Re: state of release and release plan
Boudewijn Rempt skrev den 2016-11-11 15:16:
> On Tue, 8 Nov 2016, Dag wrote:
>
>> Ok, seem
Boudewijn Rempt skrev den 2016-11-11 15:16:
On Tue, 8 Nov 2016, Dag wrote:
Ok, seems we have some sort of commitment from from Tomas, Camilla
(separate
mail) and me,
which means Sheets, Words and Plan along with the shapes and filters
we find
is working.
But, I am totally blank on release w
On Tue, 8 Nov 2016, Dag wrote:
> Ok, seems we have some sort of commitment from from Tomas, Camilla (separate
> mail) and me,
> which means Sheets, Words and Plan along with the shapes and filters we find
> is working.
>
> But, I am totally blank on release work, so who will possibly step up to
>
Ok, seems we have some sort of commitment from from Tomas, Camilla
(separate mail) and me,
which means Sheets, Words and Plan along with the shapes and filters we
find is working.
But, I am totally blank on release work, so who will possibly step up to
handle that?
Tomas Mecir skrev den 2016
On 27 October 2016 at 13:11, Friedrich W. H. Kossebau
wrote:
> Hi Dag & all,
>
> Am Mittwoch, 26. Oktober 2016, 14:03:12 CEST schrieb Dag:
> > Hi
> > Another month came and went, and not much happened...
> > I'm actually a little afraid of releasing because we might attract some
> > users.
> > We
Hi Dag & all,
Am Mittwoch, 26. Oktober 2016, 14:03:12 CEST schrieb Dag:
> Hi
> Another month came and went, and not much happened...
> I'm actually a little afraid of releasing because we might attract some
> users.
> Well, to be more precise, that there will be nobody to support those
> users.
I
2016-10-26 14:03 GMT+02:00 Dag :
> I would support plan of course, but what about words and sheets?
> Camila and Tomas; what are you able to commit to, are there others?
Varies. Bit more busy the last few months, will be better soonish. But
still interested, ya. Sheets is in a decent shape, some t
On 26 October 2016 at 14:03, Dag wrote:
> Hi
> Another month came and went, and not much happened...
> I'm actually a little afraid of releasing because we might attract some
> users.
> Well, to be more precise, that there will be nobody to support those users.
> An example; a user posed a questi
Hi
Another month came and went, and not much happened...
I'm actually a little afraid of releasing because we might attract some
users.
Well, to be more precise, that there will be nobody to support those
users.
An example; a user posed a question about words on the forum close to 2
months ago,
Kreport has dropped kross for qjsengine, as part of being wrong, so it
would be preferable to convert python to js
On Sat, 2 Jul 2016, 19:37 Dag, wrote:
> Preliminary input for Plan. Note that I have not even open all views
> much less tried much functionality, so there may be (a lot) more...
>
Hi,
Am Samstag, 2. Juli 2016, 08:17:40 CEST schrieb Camilla Boemann:
> I think it's time we get a release out. We are stuck with not much work
> going on so inspired by Dag's return let's do a push to get ready.
>
> I think we should cut down on the number of applications so we have
> something
Pau Garcia i Quiles skrev den 2016-08-02 17:17:
On Sat, Jul 2, 2016 at 8:37 PM, Dag wrote:
Kross/python: Scripting is used for some functionallity so python
support is needed. (or else convert to javascript)
I would really prefer JavaScript (QJsEngine), as Kross does not work
on Windows.
On 2 August 2016 at 17:17, Pau Garcia i Quiles wrote:
>
>
> On Sat, Jul 2, 2016 at 8:37 PM, Dag wrote:
>
>>
>>
>> Kross/python: Scripting is used for some functionallity so python support
>> is needed. (or else convert to javascript)
>>
>
> I would really prefer JavaScript (QJsEngine), as Kross d
On Sat, Jul 2, 2016 at 8:37 PM, Dag wrote:
>
> Kross/python: Scripting is used for some functionallity so python support
> is needed. (or else convert to javascript)
>
>
I would really prefer JavaScript (QJsEngine), as Kross does not work on
Windows.
Also, if a Plan user wants to implement some
Ping...
Any news, or are most still on vacation?
As for Plan, I think I should be able to have something beta like early
september.
(Have a week vacation in there, but still.)
Dag
Camilla Boemann skrev den 2016-07-02 08:17:
Hi
I think it's time we get a release out. We are stuck with not muc
On 2 July 2016 at 08:17, Camilla Boemann wrote:
>
> Hi
>
> I think it's time we get a release out. We are stuck with not much work going
> on so inspired by Dag's return let's do a push to get ready.
>
> I think we should cut down on the number of applications so we have something
> manageble left
Looking at that I'd say only time and currency are real blockers - the others
are lost functionality but nothing that produces wrong output
RDF support is lost in words, but that shouldn't stop the release
On Saturday 02 July 2016 20:37:17 Dag wrote:
> Preliminary input for Plan. Note that I hav
Preliminary input for Plan. Note that I have not even open all views
much less tried much functionality, so there may be (a lot) more...
Also, I'm on vacation 2 last weeks of july and 3. week of august, so
expecting to be release ready in 1 month would be a bit optimistic ;)
That said, this is w
No big blockers on Sheets. There's a lot of "would be nice"s and "this
should work better"s, but all apps have that, I imagine.
2016-07-02 8:17 GMT+02:00 Camilla Boemann :
> Hi
>
> I think it's time we get a release out. We are stuck with not much work going
> on so inspired by Dag's return let's
Hi
I think it's time we get a release out. We are stuck with not much work going
on so inspired by Dag's return let's do a push to get ready.
I think we should cut down on the number of applications so we have something
manageble left. It's tough but the alternative is that Calligra dies
compl
Am Montag, 7. September 2015, 18:55:56 schrieb Jaroslaw Staniek:
> Hi,
> How many releases would you see for the 2.9 series?
> Is it possible to deduce already?
>
> And is October 7 for 2.9.8 a good fit for you?
For the things I oversee (Okular plugins, Plan, thumbnailer) I currently do
not plan
I'd say, once a month until 3.x is good enough for end users. The first week of
every month would be good for me.
On Mon, 7 Sep 2015, Jaroslaw Staniek wrote:
Hi,
How many releases would you see for the 2.9 series?
Is it possible to deduce already?
And is October 7 for 2.9.8 a good fit for yo
Hi,
How many releases would you see for the 2.9 series?
Is it possible to deduce already?
And is October 7 for 2.9.8 a good fit for you?
--
regards, Jaroslaw Staniek
KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software de
On Sunday 07 December 2014 Dec 21:17:53 Cyrille Berger wrote:
> On 2014-11-25 13:50, Cyrille Berger wrote:
> >
> > So I would suggest:
> >
> > * branch to 2.9 at beta 1
> > * freeze master, make it follow branch/2.9, we might even ask sysadmin
> > to restrict pushing to master to calligra git adm
On 8 December 2014 at 16:32, Cyrille Berger wrote:
> On 2014-12-07 16:41, Jaroslaw Staniek wrote:
>>
>> +1
>>
>> PS: What would be the date for 2.9.0 stable?
>
>
> My estimate is third week of january.
OK
>
>> One big patch removing qt3support deps in Kexi - in tableview - is not
>> yet put for
On 2014-12-07 16:41, Jaroslaw Staniek wrote:
+1
PS: What would be the date for 2.9.0 stable?
My estimate is third week of january.
One big patch removing qt3support deps in Kexi - in tableview - is not
yet put for review. It mostly works; no idea how long it would take to
include it in 2.9 b
+1
PS: What would be the date for 2.9.0 stable?
One big patch removing qt3support deps in Kexi - in tableview - is not
yet put for review. It mostly works; no idea how long it would take to
include it in 2.9 but I wouldn't like to have such big change mixed
with Qt5 port...
On 7 December 2014 at
On 2014-11-25 13:50, Cyrille Berger wrote:
So I would suggest:
* branch to 2.9 at beta 1
* freeze master, make it follow branch/2.9, we might even ask sysadmin
to restrict pushing to master to calligra git admins (that would be
Boudewijn and me)
* do the port in a separate branch
So what is the
Is 2.8.7 considered as tagged yet? If not how many hours left? I am
asking because I have uncommited one thing or two...
On 20 November 2014 at 17:34, Cyrille Berger wrote:
> Hi,
>
> I have updated the wiki page with tentative schedules for 2.8.7 and 2.9:
>
> https://community.kde.org/Calligra/Sc
On 2014-11-24 10:02, Friedrich W. H. Kossebau wrote:
So to get the port done as quickly and clean as possible, I would vote
for a
complete freeze of master, until the port is done (which would be
roughly a
month I hope). And if master is frozen anyway, the port could also be
directly
done ther
On 24 November 2014 at 10:02, Friedrich W. H. Kossebau wrote:
> Am Montag, 24. November 2014, 00:50:18 schrieb Jaroslaw Staniek:
>> How about keeping the "master always stable" motto and porting in a branch?
>> Cherry picking the results once they are stable?
>
> "Master always stable" is a good p
On Mon, 24 Nov 2014, Friedrich W. H. Kossebau wrote:
Am Montag, 24. November 2014, 00:50:18 schrieb Jaroslaw Staniek:
How about keeping the "master always stable" motto and porting in a branch?
Cherry picking the results once they are stable?
"Master always stable" is a good point, and I su
Am Montag, 24. November 2014, 00:50:18 schrieb Jaroslaw Staniek:
> How about keeping the "master always stable" motto and porting in a branch?
> Cherry picking the results once they are stable?
"Master always stable" is a good point, and I subscribe to that.
But: I would argue that with the port
How about keeping the "master always stable" motto and porting in a branch?
Cherry picking the results once they are stable?
On 24 November 2014 at 00:41, Friedrich W. H. Kossebau wrote:
> Am Sonntag, 23. November 2014, 23:05:02 schrieb Jaroslaw Staniek:
>> On 23 November 2014 at 22:14, Friedrich
Am Sonntag, 23. November 2014, 23:05:02 schrieb Jaroslaw Staniek:
> On 23 November 2014 at 22:14, Friedrich W. H. Kossebau
wrote:
> > So, anyone opposing delaying the branching until the port will start?
>
> Honestly, I think technical means wouldn't stop everyone from working
> of features inst
On 23 November 2014 at 22:14, Friedrich W. H. Kossebau wrote:
> Am Donnerstag, 20. November 2014, 17:34:59 schrieb Cyrille Berger:
>> I have updated the wiki page with tentative schedules for 2.8.7 and 2.9:
>>
>> https://community.kde.org/Calligra/Schedules/2.9/Release_Plan
>> https://community.k
Am Donnerstag, 20. November 2014, 17:34:59 schrieb Cyrille Berger:
> Hi,
>
> I have updated the wiki page with tentative schedules for 2.8.7 and 2.9:
>
> https://community.kde.org/Calligra/Schedules/2.9/Release_Plan
> https://community.kde.org/Calligra/Schedules/2.8/Release_Plan
Question: does i
Hi,
I have updated the wiki page with tentative schedules for 2.8.7 and 2.9:
https://community.kde.org/Calligra/Schedules/2.9/Release_Plan
https://community.kde.org/Calligra/Schedules/2.8/Release_Plan
--
Cyrille Berger Skott
___
calligra-devel mailin
On Saturday 12 October 2013 Oct 10:32:03 Cyrille Berger wrote:
> Hi,
>
> Here is a suggested release plan for 2.8:
>
> Beta1
> Tag and branching 22nd November
> Release 26th November
> Beta2
> Tag 14th December
> Release 17th December
>
Fine with me! I would
Hi,
Here is a suggested release plan for 2.8:
Beta1
Tag and branching 22nd November
Release 26th November
Beta2
Tag 14th December
Release 17th December
Also there does not seem to be much activity in branch 2.7, so I
suggested to move 2.7.5
to:
Tag 22nd November
Release 26th November
On Saturday, August 10, 2013 06:39:10 Cyrille Berger Skott wrote:
> On Friday 09 August 2013 18:10:16 Inge Wallin wrote:
> > I tried to look at the release plan for 2.7 to prepare
>
> for the bugfix
>
> > announcements but there wasn't any[1].
> >
> >
On Friday 09 August 2013 18:10:16 Inge Wallin wrote:
> I tried to look at the release plan for 2.7 to prepare
for the bugfix
> announcements but there wasn't any[1].
>
> Cyrille, can you make a proposed release plan?
done.
> [1]
http://community.kde.org/Calligra/Schedul
I tried to look at the release plan for 2.7 to prepare for the bugfix
announcements but there wasn't any[1].
Cyrille, can you make a proposed release plan?
[1] http://community.kde.org/Calligra/Schedules/2.7/Release_Plan___
calligra-devel ma
On Friday 24 February 2012 18:08:37 Cyrille Berger Skott wrote:
> Here is my suggestion:
>
> * merge the branch ASAP, like this week-end
> * tag RC/branch on Friday 2nd
>
> That way it give use a small week to fully tests the changes before the RC.
It has my support
__
Here is my suggestion:
* merge the branch ASAP, like this week-end
* tag RC/branch on Friday 2nd
That way it give use a small week to fully tests the changes before the RC.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
On Thursday 23 February 2012 11:57:56 Elvis Stansvik wrote:
> 2012/2/23 C. Boemann :
> > Hi all
> >
> > So the minisprint on undo in Words is over and we had success. I'm
> > requesting merge of our branch but more on that below.
> >
> > Assuming we merge within a day or two, I propose we create
On 23 February 2012 10:27, C. Boemann wrote:
> Hi all
>
> So the minisprint on undo in Words is over and we had success. I'm requesting
> merge of our branch but more on that below.
>
> Assuming we merge within a day or two, I propose we create a release branch
> one of the next days. And on next
On Thursday, February 23, 2012 10:27:38 C. Boemann wrote:
> Hi all
>
> So the minisprint on undo in Words is over and we had success. I'm
> requesting merge of our branch but more on that below.
Good to hear.
> Assuming we merge within a day or two, I propose we create a release branch
> one of
2012/2/23 C. Boemann :
> Hi all
>
> So the minisprint on undo in Words is over and we had success. I'm requesting
> merge of our branch but more on that below.
>
> Assuming we merge within a day or two, I propose we create a release branch
> one of the next days. And on next friday we tag an RC fro
2012/2/23 Pierre Stirnweiss :
> When I checked out the branch yesterday evening, the KoTextEditor_format.cpp
> file was missing. This also meant that I couldn't test the trick for the
> insertTable method. It wouldn't compile.
It was a small miss by boemann. It's been added now.
Elvis
>
> Pierre
yes i commited the missing file late last night
On Thursday 23 February 2012 10:48:55 Pierre Stirnweiss wrote:
> When I checked out the branch yesterday evening, the
> KoTextEditor_format.cpp file was missing. This also meant that I couldn't
> test the trick for the insertTable method. It wouldn't
When I checked out the branch yesterday evening, the
KoTextEditor_format.cpp file was missing. This also meant that I couldn't
test the trick for the insertTable method. It wouldn't compile.
Pierre
On Thu, Feb 23, 2012 at 10:27 AM, C. Boemann wrote:
> Hi all
>
> So the minisprint on undo in Wor
Hi all
So the minisprint on undo in Words is over and we had success. I'm requesting
merge of our branch but more on that below.
Assuming we merge within a day or two, I propose we create a release branch
one of the next days. And on next friday we tag an RC from that release
branch. Then 3 we
Since boemann mentioned on IRC that there might be a need for an other beta.
This will obviously affect the RC1 and branching.
On Friday 27 Jan 2012, Cyrille Berger Skott wrote:
> Hi,
>
> Here is the suggested release plan for RC1:
>
> February 17 tag
> February 22 Release
Friday 27 Jan 2012, Cyrille Berger Skott wrote:
> > Hi,
> >
> > Here is the suggested release plan for RC1:
> >
> > February 17 tag
> > February 22 Release
> >
> > Final release, possibely, 3 weeks after that.
Sounds good to me
__
And I forgot an important point, the question of when to branch.
I am suggesting we do that on February 10, and that patches in the "2.4
branch" get reviewed, until the final release.
On Friday 27 Jan 2012, Cyrille Berger Skott wrote:
> Hi,
>
> Here is the suggested r
Hi,
Here is the suggested release plan for RC1:
February 17 tag
February 22 Release
Final release, possibely, 3 weeks after that.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo
On Saturday 12 February 2011, Alfredo Beaumont wrote:
> Larunbata 12 Otsaila 2011(e)an, Boudewijn Rempt(e)k idatzi zuen:
> > On Saturday 12 February 2011, Cyrille Berger Skott wrote:
> > > Hi,
> > >
> > > I have updated our release plan:
> > >
>
Larunbata 12 Otsaila 2011(e)an, Boudewijn Rempt(e)k idatzi zuen:
> On Saturday 12 February 2011, Cyrille Berger Skott wrote:
> > Hi,
> >
> > I have updated our release plan:
> >
> > http://community.kde.org/Calligra/Schedules/2.4/Release_Plan
> >
> >
On Saturday 12 February 2011, Cyrille Berger Skott wrote:
> Hi,
>
> I have updated our release plan:
>
> http://community.kde.org/Calligra/Schedules/2.4/Release_Plan
>
> Since we want to label our snapshot "stable", what should we do with failing
> unit test
Hi,
I have updated our release plan:
http://community.kde.org/Calligra/Schedules/2.4/Release_Plan
Since we want to label our snapshot "stable", what should we do with failing
unit tests ? Apart from whipping developers until they fix the issues :D
--
Cyrille Be
On Thu, Jan 13, 2011 at 2:51 PM, Inge Wallin wrote:
> On Thursday, January 13, 2011 14:15:01 Cyrille Berger Skott wrote:
> > On Thursday 13 January 2011, Tomas Mecir wrote:
> > > As a disclaimer, I'm not active in Calligra development currently, so
> > > my opinion may not be entirely relevant, b
On Thursday 13 January 2011 14:51:32 Inge Wallin wrote:
> On Thursday, January 13, 2011 14:15:01 Cyrille Berger Skott wrote:
> > On Thursday 13 January 2011, Tomas Mecir wrote:
> > > As a disclaimer, I'm not active in Calligra development currently, so
> > > my opinion may not be entirely relevant,
On Thursday, January 13, 2011 14:15:01 Cyrille Berger Skott wrote:
> On Thursday 13 January 2011, Tomas Mecir wrote:
> > As a disclaimer, I'm not active in Calligra development currently, so
> > my opinion may not be entirely relevant, but hopefully it will be
> > useful anyway.
> >
> > Wouldn't i
> As a disclaimer, I'm not active in Calligra development currently, so
> my opinion may not be entirely relevant, but hopefully it will be
> useful anyway.
>
> Wouldn't it be better to (at least for the initial release) use a
> different development scheme with an alpha/beta version being released
As a disclaimer, I'm not active in Calligra development currently, so
my opinion may not be entirely relevant, but hopefully it will be
useful anyway.
Wouldn't it be better to (at least for the initial release) use a
different development scheme with an alpha/beta version being released
every mont
On Thursday, January 13, 2011 10:57:10 Cyrille Berger Skott wrote:
> On Thursday 13 January 2011, Inge Wallin wrote:
> > Now, if we instead prolong the initial release phase to, say, 7 months
> > and by doing that make sure that the release is in fact good enough
> > then the user gets a usable Ca
On Thursday, January 13, 2011 10:12:26 Cyrille Berger Skott wrote:
> On Thursday 13 January 2011, Inge Wallin wrote:
> > What we have to keep in mind is that a quick release that is not good
> > enough is actually a delay. It's a delay until Calligra is relevant and
> > it's a delay until people
On Wednesday, January 12, 2011 16:41:55 Cyrille Berger Skott wrote:
> Hi,
>
> Time to work on a release schedule for the first calligra release, aka 2.4
> (and not 1.0 :) ).
>
> If we were to strictly follow our schedule, we would have schedule that
> looks like this: (with year+1, ie 2010->2011)
Recently I'm busy with my final exams and didn't commit to calligra. I
can come back at 18th, I prefer more extra time so that I can make
Flow at least usable for basic operations in 2.4.
On Thu, Jan 13, 2011 at 5:37 AM, Cyrille Berger Skott
wrote:
> On Wednesday 12 January 2011, C. Boemann wrote
On 12 January 2011 20:32, Boudewijn Rempt wrote:
> On Wednesday 12 January 2011, C. Boemann wrote:
>> On Wednesday 12 January 2011 20:09:59 Boudewijn Rempt wrote:
>> > On Wednesday 12 January 2011, Cyrille Berger Skott wrote:
>> > > Hi,
>> > >
>> > > Time to work on a release schedule for the firs
On Wednesday 12 January 2011 20:41:27 Boudewijn Rempt wrote:
> On Wednesday 12 January 2011, C. Boemann wrote:
> > On Wednesday 12 January 2011 20:32:04 Boudewijn Rempt wrote:
> > > We could go with a really long and relaxed beta period :-)
> >
> > could work, with a bit of enhanced publicity
>
>
On Wednesday 12 January 2011, C. Boemann wrote:
> On Wednesday 12 January 2011 20:32:04 Boudewijn Rempt wrote:
> > We could go with a really long and relaxed beta period :-)
> could work, with a bit of enhanced publicity
Another option could be to go to a fast & furious two month schedule to sho
On Wednesday 12 January 2011 20:32:04 Boudewijn Rempt wrote:
> On Wednesday 12 January 2011, C. Boemann wrote:
> > On Wednesday 12 January 2011 20:09:59 Boudewijn Rempt wrote:
> > > On Wednesday 12 January 2011, Cyrille Berger Skott wrote:
> > > > Hi,
> > > >
> > > > Time to work on a release sche
On Wednesday 12 January 2011, C. Boemann wrote:
> On Wednesday 12 January 2011 20:09:59 Boudewijn Rempt wrote:
> > On Wednesday 12 January 2011, Cyrille Berger Skott wrote:
> > > Hi,
> > >
> > > Time to work on a release schedule for the first calligra release, aka
> > > 2.4 (and not 1.0 :) ).
> >
On Wednesday 12 January 2011 20:09:59 Boudewijn Rempt wrote:
> On Wednesday 12 January 2011, Cyrille Berger Skott wrote:
> > Hi,
> >
> > Time to work on a release schedule for the first calligra release, aka
> > 2.4 (and not 1.0 :) ).
> >
> > If we were to strictly follow our schedule, we would h
On Wednesday 12 January 2011, Jaroslaw Staniek wrote:
> On 12 January 2011 20:09, Boudewijn Rempt wrote:
> > On Wednesday 12 January 2011, Cyrille Berger Skott wrote:
> >> Hi,
> >>
> >> Time to work on a release schedule for the first calligra release, aka 2.4
> >> (and not 1.0 :) ).
> >>
> >> If
On 12 January 2011 20:09, Boudewijn Rempt wrote:
> On Wednesday 12 January 2011, Cyrille Berger Skott wrote:
>> Hi,
>>
>> Time to work on a release schedule for the first calligra release, aka 2.4
>> (and not 1.0 :) ).
>>
>> If we were to strictly follow our schedule, we would have schedule that l
On Wednesday 12 January 2011, Cyrille Berger Skott wrote:
> Hi,
>
> Time to work on a release schedule for the first calligra release, aka 2.4
> (and not 1.0 :) ).
>
> If we were to strictly follow our schedule, we would have schedule that looks
> like this: (with year+1, ie 2010->2011)
>
> ht
On Wednesday 12 January 2011 16:41:55 Cyrille Berger Skott wrote:
> Hi,
>
> Time to work on a release schedule for the first calligra release, aka 2.4
> (and not 1.0 :) ).
>
> If we were to strictly follow our schedule, we would have schedule that
> looks like this: (with year+1, ie 2010->2011)
>
80 matches
Mail list logo
