On 10/2/12 3:42 AM, "Michael Schmalle" wrote:
>
> Looking through some of the JIRA bugs, I know some probably can't be
> fixed from experience, can I close them or do I have to create a
> dialog(comment) on the bug first to see if it would get any responses.
I would provide detail why it ca
On 10/2/12 5:43 AM, "Michael Schmalle" wrote:
> Yeah, that was for people saying I didn't do my homework. :)
>
> I'm just a bit confused as to what and where I am committing things
> with the patches branch there. It doesn't seem like people are
> committing to trunk.
Hopefully you have signe
Hi,
There was a vote[1] a while back and it was decided to go with this:
http://nvie.com/posts/a-successful-git-branching-model/
With the addition of cherry picking from develop to trunk when making a
release. However we've not migrated to git yet so have to commit via SVN.
Basically all work n
On Tue, Oct 2, 2012 at 2:43 PM, Michael Schmalle
wrote:
> ...Maybe someday a committer in the know could put up a wiki page for
> committers asking these same questions...
Yeah, that's what I meant - if it's important (and this definitely
is), that info shouldn't be buried in emails.
-Bertrand
Yeah, that was for people saying I didn't do my homework. :)
I'm just a bit confused as to what and where I am committing things
with the patches branch there. It doesn't seem like people are
committing to trunk.
I'm not exactly understanding the mustella tests and "when you have to
write
On Tue, Oct 2, 2012 at 12:42 PM, Michael Schmalle
wrote:
> ...Could someone steer me to emails or something that says how a committer is
> supposed to take a JIRA task, fix it in their local code base and where to
> commit that code
I don't have that info, but if it's buried in emails that's
Hi,
I apologize for this but, I have looked in quite a few places and
missed the whole release cycle with 4.8.
Could someone steer me to emails or something that says how a
committer is supposed to take a JIRA task, fix it in their local code
base and where to commit that code.
I see th
