development workflow question

[David Schmitt]

Hi,


I'm looking into a problem related to PUP-1158. There's a patch that was
"merged" to master in December. Yet, the ticket is still in "Ready for
merge" and the patch is not yet in a current puppet release, while -- from
my limited reading -- it could have easily been incorporated into any 3.4.x
fixup release.

* How to proceed with this ticket?
* Is there any write-up of the new JIRA workflow for externals?

Regards, David

[Henrik Lindberg]

It is stuck in limbo - it should have been moved to "Ready for CI", and
marked with a release.

Please comment on the issue that will ping the people that worked on it.

- henrik

[Adrien Thebo]

It looks like the JIRA ticket wasn't updated to reflect the new status; I've changed that to 'Ready for Review' so the fix gets validated before it's released. (If anyone would be willing to validate the fix against master that would be great!) With respect to releasing the fix, the pull request was filed against the master branch and patch releases are based off of stable so it wouldn't be pulled in for a patch release as-is. If this is a show stopper of an issue then we can consider backporting it into the stable branch. However we're on track to release Puppet 3.5.0 at the end of February, so if it isn't a major blocker then it might just be easier to release it as part of 3.5.0.

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/ldd9h9%24cga%241%40ger.gmane.org.

For more options, visit https://groups.google.com/groups/opt_out.

--

Adrien Thebo | Puppet Labs

[Kylo Ginsberg]

It also wasn't in a sprint or assigned story points, so would have dropped off the planning radar. I just gave it a story point and assigned it to the sprint starting tomorrow. So we shouldn't forget!

Thanks for bringing this up!

Kylo

To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CALVJ9S%2BUm%3DXhi-Qj5BfFPRHQZzjVArREWJP3GfWJCBBvunUo7g%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

Kylo Ginsberg

ky...@puppetlabs.com

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14

[Andy Parker]

The jira workflow isn't too far off from what it was in Redmine. You can take a look at http://docs.puppetlabs.com/community/puppet_projects_workflow.html, which should explain it all. If it doesn't, just shout and we can try to fix it up. Or you can grab the puppet-docs repo and send a PR :) https://github.com/puppetlabs/puppet-docs/blob/master/source/community/puppet_projects_workflow.markdown

 

Regards, David

--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/bd51b7039450e326c5626af901b19407%40hosting.edv-bus.at.

For more options, visit https://groups.google.com/groups/opt_out.

--

Andrew Parker

an...@puppetlabs.com

Freenode: zaphod42

Twitter: @aparker42

Software Developer

[David Schmitt]

On 11.02.2014 22:40, Andy Parker wrote:
> On Tue, Feb 11, 2014 at 1:26 AM, David Schmitt <da...@dasz.at
> <mailto:da...@dasz.at>> wrote:
>
> Hi,
>
>
> I'm looking into a problem related to PUP-1158. There's a patch that was
> "merged" to master in December. Yet, the ticket is still in "Ready for
> merge" and the patch is not yet in a current puppet release, while
> -- from
> my limited reading -- it could have easily been incorporated into
> any 3.4.x
> fixup release.
>
> * How to proceed with this ticket?
> * Is there any write-up of the new JIRA workflow for externals?
>
>
> The jira workflow isn't too far off from what it was in Redmine. You can
> take a look at
> http://docs.puppetlabs.com/community/puppet_projects_workflow.html,
> which should explain it all. If it doesn't, just shout and we can try to
> fix it up.

That's what I was looking for. "puppet development workflow" didn't have
the right google-karma to find that for me.


Thanks everyone else on moving the ticket forwards. 3.5.0 is totally ok
for me, it's "only" a warning.


The last question is: how many other open tickets fall through the cracks?


Regards, David