On Tue, 13 Sep 2011 14:50:46 +0200, Peter Meier wrote: > > > Is there any chance (after failing to get considered for 2.7.3) that the > > 3 patches of the network device code could be merged-in in time for 2.7.4? > > I have the feeling that a couple of pending (!) merges got lost to be in > 2.7.3. They also didn't get into the 2.7.4rc1. So I went along these > bugs/feature requests and marked the target version as 2.7.4 so they > show up as pending for that release. > > I hope you don't mind that action. All I like to do is that these > pending issues get the attention they deserve, before we end up with > another release. > If you think this have been a bad move and don't like it, then either > revert it or ask me to do it. But also please speak up of how we can > address the issue that various pending (!) merges got lost/forgotten. > > Maybe it's only my feeling, that things get lost. But as Brice, Dominic > Deal & Dean Wilson all also pointed to things that didn't yet get the > attention for the next release, I thought some action might not be that bad. > > Hope you don't mind. > > ~pete >
In general, the policy that we've been following in the Puppet Labs Development Team is that a ticket will get marked with the .x 'version', unless it is an agreed upon, known blocker for a particular release, or if the code to address the ticket has been merged. If it's one of the latter cases, then it will get marked with the 'next' version for the particular branch it should be/has been merged into. We've been handling it this way due to being on monthly, time based releases, rather than on feature based releases. These topic branches haven't exactly been lost/forgotten, but there have been various priorities that have prevented them from getting the attention that they deserve (being reviewed), though that doesn't really make much difference to the people that have submitted things for inclusion. I'm expecting this to change significantly in the near future (later this week, or early next at the latest) so that the topic branches can get more of the attention that they deserve. As far as whether the target versions on the tickets you adjusted should be changed, or not...I just recommend using your best judgement there. It looks like some of the tickets have since been released in an RC, or have been marked as needing changes. Adrien has been doing some polishing on #8491, and making sure that it won't adversely affect Puppet. Also I believe that Matthaus was going to take a look at #7114, and #1886. -- Jacob Helwig ,---- | Join us for PuppetConf, September 22nd and 23rd in Portland, OR | http://bit.ly/puppetconfsig `----
signature.asc
Description: Digital signature
