API freeze for 2.2?

Jelmer Vernooij jelmer at samba.org
Fri Jun 4 12:58:44 BST 2010


Hi Martin,

On Fri, 2010-06-04 at 18:38 +1000, Martin Pool wrote:
> We're scheduled to do 2.2b4 on the 1st of July (4 weeks from now) and
> 2.2rc1 on the 23rd of July (3 weeks after that.)  2.2rc1 will be our
> feature freeze for 2.2: at that point we will branch off from trunk
> and people will only be able to land safe bug fixes into 2.2.  This
> aligns 2.2 with Ubuntu Maverick's release schedule (plus a safety
> margin), and for everybody else it makes sure we'll get a stable
> supported new series out on a regular schedule.
> 
> We will do 2.2final as soon after 2.2rc1 as we're comfortable with the
> state of the candidate, ideally with zero code changes.
> 
> The absolute latest we can put code into Maverick is the 30th of
> September <https://wiki.ubuntu.com/MaverickReleaseSchedule>, and in
> fact changes proposed in late September would be pretty unlikely to
> get in.  But we would have basically all of August to do additional
> 2.2.x bugfix releases off that series.
> 
> I was wondering the other day if we should perhaps do an API freeze
> before the feature freeze, to give plugin developers a bit more time
> before we do 2.2rc1.  For instance, we could say we will not let API
> changes in after 2.2b4 at the start of July: any plugins that work
> with 2.2b4 will work with 2.2rc1, 2.2.0, and 2.2.x.  Or perhaps this
> is unnecessary and it's enough to just make use of the window post rc1
> during which we make installers and land changes to Maverick?
That seems reasonable.

I'd like to get the colocated branch UI support into 2.2 if at all
possible, but I'm not sure if I'll have enough spare time to get it finished 
before July.

> (Another, orthogonal proposal: perhaps given that we aim for and
> generally achieve zero post-rc changes, perhaps we should skip the rc,
> just do a source freeze for 2.2.0, and then do a .1 if problems are
> discovered?)
I think that's a good idea. 

Cheers,

Jelmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20100604/f45a8231/attachment.pgp 


More information about the bazaar mailing list