life sign & RFC

[Pau Garcia i Quiles]

Hi,

Great to have you back. I've been off too and will still be for a while :-(

Plan looks good to me.

Regarding, TortoiseGit, it is not as bad as you think. Two months ago
I migrated a corporate project with ~100 developers from ClearCase to
git. Most of them are using TortoiseGit (some use the Visual Studio
Source Provider for Git) and they are quite happy about it. It also
helped that I wrote about 50 pages of documentation, including
screenshots.

Lastly, personally I would like to see emerge out of KDE, maybe
gitorious, github, Assembla... ( http://www.elpauer.org/?p=687 )


BTW, CoApp is reaching a somewhat usable status.


On Fri, Jun 3, 2011 at 1:03 AM, Patrick Spendrin <ps_ml at gmx.de> wrote:
> Hi everybody,
>
> after some months of break, I am back online again working on KDE on
> Windows though with a lot less time.
>
> There are two things that are probably most interesting in the coming
> months:
> 1) a KDE 4.6 binary release
> 2) the emerge git transition
>
> The main question is of course in what order these should be done:
> doing the release first, and switching to git later or switching to git
> first and doing the release shortly after it.
>
> I personally prefer to have the git transition first, and do the release
> after that, since we can benefit from the things we can change with this
> transition:
>
> my plan looks like this:
> - do a last emerge branch/tagging so that people can use that version if
> they want
> - do the transition
> - move/remove stuff in emerge:
> remove kde-4.X categories and only keep kde category
>
> rationals:
> we normally don't use the splitting between the kde-4.X release
> categories and the kde category. this also doesn't work because e.g.
> win32libs do change in between and we can't guarantee for binary
> compatibility of our 3rdparty projects anyway (examples that occurred
> until now are jpeg6/7/8, png 1.2vs.1.4 and of course Qt). So instead I
> want to have one branch per release, e.g. one 4.6 branch which will be
> split away from the master branch somewhen around the time the branches
> are set up for KDE itself.
> Since Tortoisegit is not half as good as Tortoisesvn I also want to
> promote a different way to setup emerge: Beginning with a zip package
> (which might include python & emerge (& git)) you can install emerge
> somewhere, and start emerge with 'emerge --update emerge' which would
> then update itself to the most recent version. Ralf did some work on
> that already (until now only in the svn version, but I am sure we can
> easily adapt that to git) so I don't think this becomes a big problem.
>
> So what do you think?
>
> regards,
> Patrick who became father of a qt boy in february...
> _______________________________________________
> Kde-windows mailing list
> Kde-windows at kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
>



-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)