On 02/07/2011 02:24 PM, Andrew Flegg wrote:
For example, Gitorious is _supposed_ to allow effective code review:
http://blog.gitorious.org/2009/11/06/awesome-code-review/
I added one section on "How to contribute" here:
http://wiki.maemo.org/Community_SSU/Development
It's just the first
On 02/07/2011 02:24 PM, Andrew Flegg wrote:
Surely these are solved and/or solvable? Your preference may be for
the ML, but I would suspect that's a personal preference.
For example, Gitorious is _supposed_ to allow effective code review:
http://blog.gitorious.org/2009/11/06/awesome-code-r
On Sun, Feb 6, 2011 at 19:37, Alberto Mardegan
wrote:
>
> Sorry, I didn't weight my words correctly: I didn't mean to write
> "critical" in the sense of "makes the phone unusable", I just meant
> something affecting many users. But the point is that with the current
> situation, much more dangerou
Hi Andrew,
2011/2/6 Andrew Flegg :
As to be expected, as this is a *testing* release to start defining
processes and get more involved.
Indeed. But I would stress that the more stable it is, the more people
will get involved with that.
The fact that I am a developer myself doesn't help me in t
On Sun, 6 Feb 2011, 15:51:50 GMT, Alberto Mardegan
wrote:
>
> Shortly after releasing the first community SSU, we already got a few
> bugs:
> https://bugs.maemo.org/buglist.cgi?query_format=advanced&product=Maemo%205%20Community%20SSU&classification=Extras
As to be expected, as this is a *test
(note: follow-up set to maemo-developers ML)
Hi all!
I think we all agree that we should try our best to deliver good
software updates and avoid at all costs breaking any existing features.
CURRENT SITUATION
=
Shortly after releasing the first community SSU, we already got
