Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones

2007-07-13 Thread Thomas Watson
We will bring this topic up for discussion at next week's architecture call. Personally I want to use option #2 but if we are the only team doing this then it will look pretty inconsistent with the rest of the eclipse teams. Tom BJ Hargrave/Austin/[EMAIL PROTECTED] Sent by: [EMAIL

Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones

2007-07-12 Thread Jeff McAffer
i thought we were all already doing #2... Jeff Thomas Watson [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/11/2007 01:42 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To equinox-dev@eclipse.org cc Subject [equinox-dev] What to do with 3.3.1 candidate bugs

[equinox-dev] What to do with 3.3.1 candidate bugs and milestones

2007-07-11 Thread Thomas Watson
Each major release the same thing happens. We start fixing bugs in HEAD for the next major release but find a few fixes that we would like to also release into a maintenance release. Then we have to decide what to do with the status of the original bug report which was used to release the

Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones

2007-07-11 Thread BJ Hargrave
Given bugzilla provides a clone this bug link, I think option #2 is the best choice. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] office: +1 386 848 1781 mobile: +1 386 848 3788 Thomas Watson/Austin/[EMAIL PROTECTED] Sent

Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones

2007-07-11 Thread Pascal Rapicault
2) Thomas Watson [EMAIL PROTECTED] com