Hello Colin, I just have to say upfront, I am a low level developer on the Adium Code so if I jump on any toes, please let me know.
I believe that when we discussed the time based releases this was great but we were unsure if we could make this happen. The problem is that we get developers who are super busy at one time (can't work on adium) and not busy at others (can work on adium). For myself, seeing time based releases might speed up getting tickets figured out, but on the other hand we might never meet them. If we work on a document like the above one that would be amazing to do, and watching that document would be good to see where Mozilla takes their release cycle. If I am not right, Robby did come up with a time base release cycle, and I really liked that idea. >From what I understand of 1.5 has been around along time. The only thing that I would like to know is how far we are at 64 bit? If we are far in that, would we need to wait for other tickets to be fixed? My thoughts are that we get the regression and major tickets figured out. This will really speed up the process of getting 1.5 out, and we can set a date after 1.4 is out. If we are talking about the 1.6 branch merging with the 1.5 branch I am okay with this. If there is a 10.6 branch, then I would say I am clueless about this. As for outrage, I know from my end there would be none for me. Thanks, Shawn On Sun, Mar 20, 2011 at 11:29 PM, Colin Barrett <co...@springsandstruts.com>wrote: > Well did have that huge discussion about doing something like this a while > back, and supposedly implemented a similar time based plan (that we didn't > stick to). > > So I figured this could be "relevant to our interests" as they say... > > -Colin > > On Mar 20, 2011, at 7:20 PM, Christopher Forsythe wrote: > > > Is this something you're proposing adium do? How do you think it should > look for Adium? > > > > Chris > > > > On Fri, Mar 18, 2011 at 11:12 PM, Colin Barrett < > co...@springsandstruts.com> wrote: > > This is just a draft, and not finalized yet, but it's worth a look > http://people.mozilla.com/~sayrer/2011/temp/process.html Obviously a 6 > week cadence isn't something we can support, but it's worth watching how > this transition ends up playing out, I think. > > > > What is our current status with respect to releasing 1.5? Have we reached > consensus on the 10.6 issue? If someone merged in the 10.6 branch on Monday > afternoon, how outraged would the thread be? ;) > > > > -Colin > > > > >
