On Sun, Oct 25, 2009 at 8:30 AM, Fathi Boudra <fbou...@gmail.com> wrote:
> Hi,
> Since last release some bugs were fixed and the development has continued. > Could we have a release soon ?
> cheers,
> Fathi
Hi Fathi,
It would be nice to do a new release (we should release more often anyway ;) . At the moment Krusader-SVN contains some bug fixes and a few new features compared to Krusader-2.0.0 "Mars Pathfinder". http://websvn.kde.org/trunk/extragear/utils/krusader/ChangeLog?view=m... Though the new features should be tested with beta releases.
I'm not sure Jan is able to manage all this on his own yet. I hope that a few new developers will show up to share the workload. For the moment only Jan Lepper has joined us.
If somebody knows some developers who might be interested in developing Krusader don't hesitate them to let them know, the Krusader project needs them ! http://www.krusader.org/phpBB/viewtopic.php?t=2337
I generally think, that releasing a stable is not a good idea.
There is code freeze before the stable release which may take 1 month
(stabilizing + translations + ...).
Jan just joined the team, and I would let him play with the code before
starting the code freeze period.
A beta would be OK.
Anyway, I'll fix errors before releasing a new Krusader.
> On Sun, Oct 25, 2009 at 8:30 AM, Fathi Boudra <fbou...@gmail.com> wrote:
>> Hi,
>> Since last release some bugs were fixed and the development has continued.
>> Could we have a release soon ?
>> cheers,
>> Fathi
> Hi Fathi,
> It would be nice to do a new release (we should release more often anyway ;) .
> At the moment Krusader-SVN contains some bug fixes and a few new
> features compared to Krusader-2.0.0 "Mars Pathfinder".
> http://websvn.kde.org/trunk/extragear/utils/krusader/ChangeLog?view=m... > Though the new features should be tested with beta releases.
> I'm not sure Jan is able to manage all this on his own yet.
> I hope that a few new developers will show up to share the workload.
> For the moment only Jan Lepper has joined us.
> If somebody knows some developers who might be interested in
> developing Krusader don't hesitate them to let them know,
> the Krusader project needs them !
> http://www.krusader.org/phpBB/viewtopic.php?t=2337
Am Sonntag 25 Oktober 2009 11:23:22 schrieb Karai Csaba:
> Hi,
> I generally think, that releasing a stable is not a good idea.
> There is code freeze before the stable release which may take 1 month > (stabilizing + translations + ...). > Jan just joined the team, and I would let him play with the code before > starting the code freeze period.
> A beta would be OK.
> Anyway, I'll fix errors before releasing a new Krusader.
Hi,
we've released stable versions without a freeze period before. Are there any new experimental features compared to 2.0.0? If yes, then the next version should be a beta, if not, we can release a 2.0.1 without freeze.
The changes to the archive handling and the views could be considered experimental, but i'm not sure. Please let me know.
> Am Sonntag 25 Oktober 2009 11:23:22 schrieb Karai Csaba: >> Hi,
>> I generally think, that releasing a stable is not a good idea.
>> There is code freeze before the stable release which may take 1 month >> (stabilizing + translations + ...). >> Jan just joined the team, and I would let him play with the code before >> starting the code freeze period.
>> A beta would be OK.
>> Anyway, I'll fix errors before releasing a new Krusader.
> Hi,
> we've released stable versions without a freeze period before. Are there any > new experimental features compared to 2.0.0? If yes, then the next version > should be a beta, if not, we can release a 2.0.1 without freeze.
> The changes to the archive handling and the views could be considered > experimental, but i'm not sure. Please let me know.
On Sun, Oct 25, 2009 at 9:29 PM, Dirk Eschler <esch...@gmail.com> wrote:
> Am Sonntag 25 Oktober 2009 19:27:23 schrieb Karai Csaba: >> > we've released stable versions without a freeze period before. Are
>> there any
>> > new experimental features compared to 2.0.0?
>> Lister is new (with i18n change). Otherwise hundreds of lines were >> changed by migrating to the KDE4 repo.
>> The difference between 2.0.0 and 2.0.1 can be huge.
> Allright, in this case i'll prepare a beta.
> bye, > Dirk
Dirk,
If we release a 2.1.0-beta1, do we send out a translation call to the kde translations team or not? ( I think we should btw. ) In about two weeks most of the GUI languages will be translated I guess. I don't think we should yet translate the docs (the new features are not described yet anyway, the current Krusader docs are = version 2.0.0)
I can send a translation call to the kde translation teams if you want to.
On Sun, Oct 25, 2009 at 11:30 PM, Dirk Eschler <esch...@gmail.com> wrote:
> Am Sonntag 25 Oktober 2009 22:50:37 schrieb Frank Schoolmeesters: >> Dirk,
>> If we release a 2.1.0-beta1, do we send out a translation call to the >> kde translations team or not?
> Not for the first beta. See Csaba's first reply.
> bye, > Dirk
Hi,
I think the kde-10n teams will not be happy if you don't inform them about the beta1. They don't like a release that is not 100% translated (GUI-10n). A 14 days string freeze for beta1 release is not a problem I guess. After the beta1 release the strings can be changed again.
The 14 days will allow me to update the English documentation as well (I hope I will find some spare time todo it, but no promises).
btw. since the kde-10n teams will verify for the first time Krusader, they might even found some i10n problems in our source code.
> On Sun, Oct 25, 2009 at 11:30 PM, Dirk Eschler <esch...@gmail.com> wrote: > > Am Sonntag 25 Oktober 2009 22:50:37 schrieb Frank Schoolmeesters: > >> Dirk,
> >> If we release a 2.1.0-beta1, do we send out a translation call to the > >> kde translations team or not?
> > Not for the first beta. See Csaba's first reply.
> > bye, > > Dirk
> Hi,
> I think the kde-10n teams will not be happy if you don't inform them > about the beta1. > They don't like a release that is not 100% translated (GUI-10n). > A 14 days string freeze for beta1 release is not a problem I guess. > After the beta1 release the strings can be changed again.
> The 14 days will allow me to update the English documentation as well > (I hope I will find some spare time todo it, but no promises).
Well, there will be a string freeze before we release a stable, most likely with the second beta. I don't see how this is a problem.
We broke about every string freeze that took place with a first beta release, because bugs in new features often required string changes. I think that's worse.
> btw. since the kde-10n teams will verify for the first time Krusader, > they might even found some i10n problems in our source code.
That already happened during the migration from kdereview to extragear. There were plenty of commits.
On Mon, Oct 26, 2009 at 1:21 PM, Dirk Eschler <esch...@gmail.com> wrote:
> Am Montag 26 Oktober 2009 12:37:50 schrieb Frank Schoolmeesters: >> On Sun, Oct 25, 2009 at 11:30 PM, Dirk Eschler <esch...@gmail.com> wrote: >> > Am Sonntag 25 Oktober 2009 22:50:37 schrieb Frank Schoolmeesters: >> >> Dirk,
>> >> If we release a 2.1.0-beta1, do we send out a translation call to the >> >> kde translations team or not?
>> > Not for the first beta. See Csaba's first reply.
>> > bye, >> > Dirk
>> Hi,
>> I think the kde-10n teams will not be happy if you don't inform them >> about the beta1. >> They don't like a release that is not 100% translated (GUI-10n). >> A 14 days string freeze for beta1 release is not a problem I guess. >> After the beta1 release the strings can be changed again.
>> The 14 days will allow me to update the English documentation as well >> (I hope I will find some spare time todo it, but no promises).
> Well, there will be a string freeze before we release a stable, most likely > with the second beta. I don't see how this is a problem.
> We broke about every string freeze that took place with a first beta release, > because bugs in new features often required string changes. I think that's > worse.
>> btw. since the kde-10n teams will verify for the first time Krusader, >> they might even found some i10n problems in our source code.
> That already happened during the migration from kdereview to extragear. There > were plenty of commits.
> bye, > Dirk
If you prefer Krusader-2.1.0-beta1 without a "small temporary string freeze", ok for me. For me personally not having a small temporary string freeze is not a problem, but some users will probably not like that the beta1 GUI is not 100% translated. I don't mind that strings will get be broken again after the beta1.
I have updated the handbook, all new Krusader-2.1.0-beta1 features are documented now.
From my side you have a GO for a beta1 release.
btw. I personally only use the English version ;-)