Re: [tasklist] Branches - take 2

On Wed, 2003-03-12 at 09:29, Jesse Glick wrote:
> Tor Norbye wrote:
> > * the trunk should also be compileable and runnable with
> >   NetBeans 3.5.
> 
> Careful - if there are major refactorings in core during the 4.0 dev 
> cycle (as seems quite likely), the usual policy is to update any trunk 
> modules in at least the daily alpha NBM config which would no longer be 
> buildable without changes. This happened during the 3.5 dev cycle a few 
> times.

Agreed - my proposal is that we try to avoid using 4.0 APIs for as 
long as possible (until we change our mind) so we don't have to keep
two branches in sync.

For example, for a long time we did not update the tasklist modules
to stop using the 3.5-deprecated APIs, since we wanted the tasklist
trunk to be buildable and runnable with NetBeans 3.4.

Even after we had to give up (because we needed to use some new APIs),
we kept the changes to a minimum to keep the branches similar such that
merging would be easy.

This is what I'd like to see again, until it no longer becomes 
practical.

> If you want a 3.5-compatible codeline, I would recommend you have a 
> branch for this purpose. Whether you use the release35 branch or a 
> separate one rooted from its tip is your decision - tasklist/* are not 
> in the standard distribution so the feature freeze is optional for you, 
> I think.

Well, tasklist is on the beta update center now. I proposed on nbdiscuss
that tasklist is made part of NetBeans 3.5 beta, and did not hear any
objections. I was going to wait until tasklist has been on the beta 
update center for 3 weeks (as outlined in the module contributions page)
before asking for further inclusion.

However, Ian had some offline objections to this, so I'm
not sure what the plan is.  But at a minimum I would like the release35
branch to be stable anyway, such that it can be posted to the stable
update center if it's not made part of the standard release - and this
means letting the branch sit in isolation and only get bugfixes for a while,
since new development tends to cause regressions here and there.

-- Tor