Re: Recent branching of CURRENT
On Saturday 13 October 2007 02:22:31 Per olof Ljungmark wrote: Mel wrote: On Saturday 13 October 2007 01:15:45 Kris Kennaway wrote: Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? Those are just names, don't worry too much about it. RELENG_7 will be the start of a new -STABLE branch once it is released. That is actually what I'm worried about. It means drivers are less likely to be MFC'd to RELENG_6 from 7.0-RELEASE onwards - I was hoping that wouldn't happen till 7.1. It's called progress. This is normal. If you need a driver that is happening in 7- only, then upgrade to 7. RELENG_6 will turn into a supported fix branch or whatever the name is and RELENG_7 is where the action takes place, just like it has been going on for quite some time (please correct me if I'm wrong). Well, 6.0-RELEASE was still on -current. I consider that a good thing, because many people won't go near a new release till it's got at least one -RELEASE and that's when the nasty bugs come out to play ;). Also, as of this writing, x11/nvidia-driver is *still* on compat5x, so those new video interfaces nvidia wanted can't have been tested enough in the real world. It would be nice to have that driver in the ports so people (like me) can test those :). -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
On Sat, Oct 13, 2007 at 04:20:49PM +0200, Mel wrote: On Saturday 13 October 2007 02:22:31 Per olof Ljungmark wrote: Mel wrote: On Saturday 13 October 2007 01:15:45 Kris Kennaway wrote: Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? Those are just names, don't worry too much about it. RELENG_7 will be the start of a new -STABLE branch once it is released. That is actually what I'm worried about. It means drivers are less likely to be MFC'd to RELENG_6 from 7.0-RELEASE onwards - I was hoping that wouldn't happen till 7.1. It's called progress. This is normal. If you need a driver that is happening in 7- only, then upgrade to 7. RELENG_6 will turn into a supported fix branch or whatever the name is and RELENG_7 is where the action takes place, just like it has been going on for quite some time (please correct me if I'm wrong). Well, 6.0-RELEASE was still on -current. No, it wasn't. 6.0-RELEASE was the first release from the 6-STABLE branch. 4.0-RELEASE was also considered a -STABLE release. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. It seems it was not announced anywhere just word of mouth kind of thing ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? I would assume we have one current still (8-) and a pile of -STABLE (2.2-, 3-, 4-, 5-, 6- and now 7-). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
On Sat, Oct 13, 2007 at 12:52:00AM +0200, Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? RELENG_7 was forked in preperation for the upcoming 7.0 release. That meant -CURRENT could be unfrozen so that new features can be added. (And since the current -CURRENT will eventually lead up to an 8.0 release it is now called 8-CURRENT rather than 7-CURRENT.) Personally I would not consider RELENG_7 to be a real 'stable' branch until after 7.0 has been officially released (or at least not until the RELENG_7_0 release branch has been created and RELENG_7 been unfrozen.) I.o.w. do we 2 current or 2 stable branches now? We have many more than 2 stable branches: RELENG_6. RELENG_4, RELENG_3, RELENG_5, RELENG_2_2, etc. Most of them are no longer in active development, but you never know when some committer sees fit to backport something to an older branch. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? Those are just names, don't worry too much about it. RELENG_7 will be the start of a new -STABLE branch once it is released. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
Kris Kennaway wrote: Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? Those are just names, don't worry too much about it. RELENG_7 will be the start of a new -STABLE branch once it is released. Mmmm... forgot we've got PRERELEASE too, sorry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
On Saturday 13 October 2007 01:15:45 Kris Kennaway wrote: Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? Those are just names, don't worry too much about it. RELENG_7 will be the start of a new -STABLE branch once it is released. That is actually what I'm worried about. It means drivers are less likely to be MFC'd to RELENG_6 from 7.0-RELEASE onwards - I was hoping that wouldn't happen till 7.1. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent branching of CURRENT
Mel wrote: On Saturday 13 October 2007 01:15:45 Kris Kennaway wrote: Mel wrote: On Friday 12 October 2007 23:15:32 Kris Kennaway wrote: Per olof Ljungmark wrote: Hi, Just out of curiosity, why did I fail to notice the branching of RELENG_7 and 8-CURRENT? I'm subscribed to -stable, -current and -announce. Because it's an administrative change that is just a normal part of the release engineering process. i.e. 7.0 is not released etc. And RELENG_7 is not considered the 'stable' branch yet, but 8-CURRENT is just forked for development of entirely new features? I.o.w. do we 2 current or 2 stable branches now? Those are just names, don't worry too much about it. RELENG_7 will be the start of a new -STABLE branch once it is released. That is actually what I'm worried about. It means drivers are less likely to be MFC'd to RELENG_6 from 7.0-RELEASE onwards - I was hoping that wouldn't happen till 7.1. It's called progress. This is normal. If you need a driver that is happening in 7- only, then upgrade to 7. RELENG_6 will turn into a supported fix branch or whatever the name is and RELENG_7 is where the action takes place, just like it has been going on for quite some time (please correct me if I'm wrong). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
