> 2011/1/27 Nicolás Alvarez :
>> Please, help review the repositories before migration! Unlike KDE
>> software,
>> here we won't have point releases to fix bugs later :)
>
>
> I have quite a few commits in kdebase-workspace with the commit message:
>
> SVN_SILENT:
> Do blahblah
>
> and
>
> GUI:
>
2011/1/27 Nicolás Alvarez :
> Please, help review the repositories before migration! Unlike KDE software,
> here we won't have point releases to fix bugs later :)
I have quite a few commits in kdebase-workspace with the commit message:
SVN_SILENT:
Do blahblah
and
GUI:
do blah blah
Since git
Hi,
> - bonus points if you add a link to further information, such as a blog entry
I also had this in mind. I personally find it hard to really describe
and promote a feature in the normal "Description" column.
What do you think about adding a "Blog" column to the feature plan in
order to encou
Ian Monroe wrote:
> For up to one week if someone finds a major problem in the history a
> re-push will be considered. After that we'll just live with it.
>
> ...but far better would be for any problem to be found now. Please
> note that the repo names are not the final ones (they will be konsole,
On Thursday, January 27, 2011 12:05:34 Nikos Chantziaras wrote:
> On 01/27/2011 12:18 PM, Sebastian Kügler wrote:
> > In order to create good release notes for the next release (yes, we're
> > early), we need a good overview of new features and improvements.
>
> I'm just a user, but how about focu
Hi all,
In order to create good release notes for the next release (yes, we're early),
we need a good overview of new features and improvements. Traditionally, we
keep a list on techbase, which we then base the release notes on.
That list can be found at:
http://techbase.kde.org/Schedules/KDE4/
