On 7-4-2014 2:23, Martin Owens wrote:
> On Mon, 2014-04-07 at 00:25 +0200, Johan Engelen wrote:
>> Important point: you forgot Josh Andler as the release manager!!!
>> About
>> the dates, from your mail I take it that you didn't discuss with
>> Bryce
>> and Josh? I think it would have been better to do so first. It comes
>> across a bit rude to bypass them and put it on the website just like
>> that.
> It is deliberate but hesitant.

Being deliberately rude I think rarely has the desired effect, and in
any case does not create a friendly atmosphere people want to work and
spend time in.

>   Inkscape is ready to release and it was
> clear at LGM that Inkscape is well respected but many of our users came
> to me with their concerns about our release schedules.
>
> And so this page is basically a template with a good suggestion for
> timing with lots of space. We can update it if we feel the release needs
> even more time and it should reflect both the consensus of developers
> and the release manager.

Indeed it should, fixed that for you.

> I know I put myself in a vulnerable position by being bold, and rude

Please be considerate of others too.
I don't think anybody does /not/ want to release; we all want the
release sooner than later. To help speed things along, potentially
offending people is not so helpful. Instead, a list of current TODO
items has a higher chance of success I feel. I've added it to the page.


> in
> this case, but my hope is that I can ask for forgiveness. Although
> really the release is a technical matter and so is probably a discussion
> for developers with the release manager. I'd like to suggest we commit
> to this release in a firm and adventurous way.
>
> And sooner rather than later. :-)
>
>> (What does your role as "supervisor" mean?)
> The person who finds the release manager and pushes for firm schedules.
> I might as well put my name on the line for the job I'm already doing.
> Not sure about the name for the job though, any suggestions welcome.

I don't think we can add all related jobs to that page... The release
managers' names are useful for people to direct questions too. But who
would want to contact a guy who pushes the ones who are pushing, that he
should push the pushers?

>> For the New Features / bug fixes : I think you can scrap those and
>> point to the release notes instead. What is more interesting to put on
>> this page is links to open bugs, or focus points. So that we know what
>> to work on to move the release along.
> The page is public facing, not necessarily developer facing. For that
> the wiki is the primary vehicle. So bug fixes and new features are
> useful and should be edited to be more in line with what the public
> should see (translate into user-speak if possible).

This is exactly what our wiki's Release Notes page is.

> My hope is that this will show something is happening with the project to the outside world and give us a sense of our activity.
>
> Hope this works *cross fingers*
>
> Best Regards, Martin Owens


------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel