On Wed, Oct 12, 2011 at 6:03 AM, Shmuel Fomberg <[email protected]>wrote:
> Hi all.
Hey Shmuel! :)
> You may or may not work, but now I work for Six Apart, on Movable Type.
> Now, there is the company, but also the a community, that maintain a fork
> (called Open Melody) of the previous major version.
>
Congrats! I love Six Apart!
> Sometimes that people submit a pull request, with useful patches. and that
> is good.
> but on the other side, in the company we have release cycles.
> (planning-implementing-testing-release)
> it means that when a patch comes, it probably won't enter to the upcoming
> release, and we can not even tell when it will added to the product until it
> actually marked in some release for inclusion.
>
I think that's a problem everyone have. I wouldn't even consider it a
"problem" per se, maybe more of an "issue".
> so practically the submitter is getting a "thank for your patch. it will
> be integrated sometime in the future" massage, and I think that this is very
> discouraging for them.
>
I disagree. I think being able to reply to the author quickly, and thanking
them for their patch is awesome, and very few places (outside the
Perl-realm) actually do it. Good job!
> but I don't know how to fix that.
>
The problem, IMHO, is that your release cycles are long, very very long. Our
typical release cycle (for a very big app) is every two weeks and I would
like to bring it down to once a week. Still, once every 3 months is
seriously long.
My opinion is that you should bring it down to once a month at least. I
think that's what needs fixing.
And ideas?
>
I would also suggest that you tell the user when it will be pushed ("your
patch has been incorporated and will be released in the next version!" or
"your patch has been incorporated and will be released in the next version,
due in 3 months!") to give them a time-frame of when they can expect their
contribution.
You could also set up a twitter, blog, whatever, and notify there that you
have incorporated a contribution by Whoever. That also will give them public
credit, and they will probably be less anxious about when it will be
released.
Another idea would be to make it publicly known when a new release is
coming. People being informed about your release cycle will have less
expectations about seeing their contributions in the next few days because
they know it's in and will only be out in 2-3 months. It would be "common
knowledge".
_______________________________________________
Perl mailing list
[email protected]
http://mail.perl.org.il/mailman/listinfo/perl
