Re: [development] Suggestion for people releasing new modules and themes into CVS
On 9/16/2006 2:35:50 PM, Chris Johnson (chris@tinpixel.com) wrote:
Khalid B wrote:
Another problem is that we often don't know if the next release will be an x+1.0 or x.y+1, so we can't say "ported for 5.0" before Dries makes that decision. This is another case where code names for future releases will help.
That is probably the single best argument I've seen for code naming releases before they are released -- so we can refer to them easily and accurately in documentation of all kinds (project pages, CVS comments, postings, etc.).
It's been named 5.0 for a while and is far from released. I'm not a dev, so maybe I'm off base here, but I don't see a big need to have a definite name before the code freeze... Michelle
On 9/18/06, Michelle Cox <mcox@charter.net> wrote:
On 9/16/2006 2:35:50 PM, Chris Johnson (chris@tinpixel.com) wrote:
Khalid B wrote:
Another problem is that we often don't know if the next release will be an x+1.0 or x.y+1, so we can't say "ported for 5.0" before Dries makes that decision. This is another case where code names for future releases will help.
That is probably the single best argument I've seen for code naming releases before they are released -- so we can refer to them easily and accurately in documentation of all kinds (project pages, CVS comments, postings, etc.).
It's been named 5.0 for a while and is far from released. I'm not a dev, so maybe I'm off base here, but I don't see a big need to have a definite name before the code freeze...
Before it was named, it is known as HEAD (technically, trunk, but that is the name that is used). It was commonly referred to as 4.8/5.0, and the naming happens when all the features are in, and a code freeze happens. At that time Dries decides if it is x.y+1 or x+1.0. However, during the development cycle (from the time the previous release is branched, until that final naming, we use HEAD, and that is a moving target by definition. If someone writes a piece of documentation or refers to the next release as "HEAD" there is no way to know whick release this ended up in. So, what I am advocating is neutral, non-geek code names (flowers, plants, fish, ...etc.) for the upcoming branch. If we say the next release is red rose, or anglefish, then we have a point of reference until it is named 5.1 or whatever. This should really be a separate thread, but ...
On Monday 18 September 2006 09:14, Michelle Cox wrote:
That is probably the single best argument I've seen for code naming releases before they are released -- so we can refer to them easily and accurately in documentation of all kinds (project pages, CVS comments, postings, etc.).
It's been named 5.0 for a while and is far from released. I'm not a dev, so maybe I'm off base here, but I don't see a big need to have a definite name before the code freeze...
Michelle
The first I heard of the next version after 4.7 being called 5.0 was when Dries marked it as such at the freeze. That was 18 days ago. He may have discussed it with others before that, but it wasn't a big to-do on the list like 4.7 was. Until this month it's been "yeah, that next version". I'm all for a cute code name scheme, but I said my piece on that back in March. :-) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Larry Garfield wrote:
I'm all for a cute code name scheme, but I said my piece on that back in March. :-)
Not cute, descriptive. We can pick colors for all I care. Or to be more Drupal-centric, we can pick Dutch words and misspell them. Just so we have some way to refer to versions that are currently in progress that is still meaningful when reading the message 6 months later.
On Monday 18 September 2006 19:26, Earl Miles wrote:
Larry Garfield wrote:
I'm all for a cute code name scheme, but I said my piece on that back in March. :-)
Not cute, descriptive. We can pick colors for all I care. Or to be more Drupal-centric, we can pick Dutch words and misspell them. Just so we have some way to refer to versions that are currently in progress that is still meaningful when reading the message 6 months later.
Not descriptive as much as arbitrary. It's a human-readable label to refer to something. It probably shouldn't be descriptive of the version it's referencing, as that leads to confusion. Cat names, river names, city names, birds, animals that no one has ever heard of (what the hell is an eft and what's edgy about it?), etc. are all perfectly good naming schemes because they don't try to describe, just label. We describe based on that label. :-) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Larry reads my mind over email ... Not cute, nor descriptive. A code name is just that: a code name. It should not have any hidden meaning, nor be too geeky (so it does not put off the suits), nor political, ...etc. The name should really mean nothing. I we want it to mean something then 5.0 is as good as a code name. Saying "sunflower", "damselfly" or "salamander" is enough (yeah, I had done biology in past lives, but whatever ...) It just means "the next release" with a fixed point of reference in time that everyone can tie into ... On 9/18/06, Larry Garfield <larry@garfieldtech.com> wrote:
On Monday 18 September 2006 19:26, Earl Miles wrote:
Larry Garfield wrote:
I'm all for a cute code name scheme, but I said my piece on that back in March. :-)
Not cute, descriptive. We can pick colors for all I care. Or to be more Drupal-centric, we can pick Dutch words and misspell them. Just so we have some way to refer to versions that are currently in progress that is still meaningful when reading the message 6 months later.
Not descriptive as much as arbitrary. It's a human-readable label to refer to something. It probably shouldn't be descriptive of the version it's referencing, as that leads to confusion. Cat names, river names, city names, birds, animals that no one has ever heard of (what the hell is an eft and what's edgy about it?), etc. are all perfectly good naming schemes because they don't try to describe, just label. We describe based on that label. :-)
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012
"If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
On 9/18/06, Khalid B <kb@2bits.com> wrote:
It just means "the next release" with a fixed point of reference in time that everyone can tie into ...
Much as I agree on this - doesn't it really boil down to Dries' personal preference? Someone else could announce a name and we could all start using it. Until Dries likes it, though, it isn't really official though, right? I feel like there are plenty of arguments in favor of this, and one important one in opposition: http://lists.drupal.org/pipermail/development/2006-May/015505.html +++++++++++++++++++ On 30 Apr 2006, at 19:54, Larry Garfield wrote:
As for codenames, the 4.7/5.0 question is why they exist. :-) I'm game.
How about we call it 'development version'? That is by far the most accessible term for outsiders. Think about it. Code names are a developer-ism. +++++++++++++++++++ Unconed - I pasted that here for you in you offline mode - enjoy! Greg -- Greg Knaddison | Growing Venture Solutions Denver, CO | http://growingventuresolutions.com Technology Solutions for Communities, Individuals, and Small Businesses
On 9/18/06, Greg Knaddison - GVS <Greg@growingventuresolutions.com> wrote:
On 9/18/06, Khalid B <kb@2bits.com> wrote:
It just means "the next release" with a fixed point of reference in time that everyone can tie into ...
Much as I agree on this - doesn't it really boil down to Dries' personal preference? Someone else could announce a name and we could all start using it. Until Dries likes it, though, it isn't really official though, right?
Until Dries (and core committers) use it, it has no backing. If I declare Salma as the next release, and then webchick does one of her nice developer documentation pages using Salma, then Robert declares Cello as the next version, and Kieran does another page with Cello as the reference, then it is not a fixed label anymore. (OT: This is Salma http://baheyeldin.com/click/738/1) So, there needs to be agreement on the use of the name. Whether it is by the benevolent-dictator-for-life, or democratically, or by concensus, I really don't care at this point. We have to first see value in what I am proposing (having a code name) and then squabble about how we select one.
I feel like there are plenty of arguments in favor of this, and one important one in opposition:
http://lists.drupal.org/pipermail/development/2006-May/015505.html
+++++++++++++++++++ On 30 Apr 2006, at 19:54, Larry Garfield wrote:
As for codenames, the 4.7/5.0 question is why they exist. :-) I'm game.
How about we call it 'development version'? That is by far the most accessible term for outsiders. Think about it. Code names are a developer-ism. +++++++++++++++++++
Not an option. "Development version" is a term that will be reused hence a shifting target like trunk or HEAD or CVS or the "next version". A code name never gets used more than once.
Greg Knaddison - GVS wrote:
+++++++++++++++++++ On 30 Apr 2006, at 19:54, Larry Garfield wrote: How about we call it 'development version'? That is by far the most accessible term for outsiders. Think about it. Code names are a developer-ism. +++++++++++++++++++
Because 'developer version' today is not the same 'developer version' in 1 year. The whole point is so that when someone references 'butterfly' and, some amount of time later, someone is reading something that references 'butterfly' *it is still the same butterfly*. Confusion is eased. This is especially true since we have a large and constant influx of new developers who are already facing an overload of information.
I want code names, it's cool :p Joomla <http://www.joomla.org/content/blogcategory/32/66/> uses sun* for code names, which I don't like. After enough releases they'll out of suns... Animal names is a good idea IMO.
FWIW I haven't been following everything said on this thread, but to me the big advantage to code names is helping my d*mned memory. I wish that Drupal were the only software I worked with - life would be much better. As it is, my clients are constantly asking which version of what I'm using - whether for their project or just for general computer questions. It's easier to remember "Debian Sarge" latest update, then it is to remember 4.7.3. Also, it is a lot easier to rally behind "Drupal Conquistador" than it is to get people excited about number. Its good from a PR point. "Hey Everyone! We're having an all night Pizza and Beer bug hunt for Drupal Conquistador!" "Hey Everyone! We're having an all night Pizza and Beer bug hunt for Drupal 5.0 Beta 2!" People don't need to be devs to help test things, and this would help them get involved I think. --Sam
participants (7)
-
Earl Miles -
Greg Knaddison - GVS -
Johan Forngren -
Khalid B -
Larry Garfield -
Michelle Cox -
Sam Tresler