> >> I suppose once the iteration is done and patches merged > >> in next, raising a red flag on some changes will be too > >> late, is that right (at least for this iteration)? > > > > The patches are being merged into next before the end of the iterations, > > so I think that commenting on them once they hit next is perfectly > > reasonable (and would be rather welcome, in my opinion), especially if > > you notice anything -1 worthy. > > Very exciting stuff. Is there any reason to keep the "next" branch and the > CI systems off the public face? I'd think it'd be easy to post all commits > on next to -dev and/or provide CI results as well (at least summarized) > this would both keep the community in the loop and demonstrate your > XP-prowess ;-)
I may be mistaken but I think the current next branch is available to anyone via github. At least, I seem to have been able to pull it without using my Puppet Labs holographic ID card or giving a blood sample or anything. -- M ----------------------------------------------------------- When in trouble or in doubt, run in circles, scream and shout. -- 1920's parody of the maritime general prudential rule ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
