You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Aidan Skinner <ai...@apache.org> on 2008/08/22 11:32:09 UTC
Naming and version numbering (was Re: Problem with your latest commit)
On Thu, Aug 21, 2008 at 8:22 PM, Alan Conway <ac...@redhat.com> wrote:
> I haven't made the change in case it needs discussion - we can probably
> find some combo of characters that works if we absolutely must (maybe
> 0.3.incubatorM3 would work...) but I don't feel like farting around
> testing all the things that might break if we can just use a normal,
> sane numeric major.minor version like most of the software universe.
There's a legal reason for using incubating in the artifcat name[1],
so the tarfile will still have that in there, the spec itself should
be ok as 0.3 though. On graduation we'd need to change our names to
apache-qpid instead of qpid-
I do think we should also have a discussion about changing from
milestones to regular (kernel/apr style[2]) numbering for everything
though, s/M/0/ essentially. So perhaps apache-qpid-0.4.0 for the next
one maybe?
Messing with Obsoletes: and the like is probably best done sooner and
later from downstreams perspective.
- Aidan
[1] http://incubator.apache.org/guides/releasemanagement.html#naming
[2] http://apr.apache.org/versioning.html
--
Apache Qpid - World Domination through Advanced Message Queueing
http://cwiki.apache.org/qpid
"Nine-tenths of wisdom consists in being wise in time." - Theodore Roosevelt
Re: Naming and version numbering (was Re: Problem with your latest commit)
Posted by Aidan Skinner <ai...@apache.org>.
On Fri, Aug 22, 2008 at 4:47 PM, Alan Conway <ac...@redhat.com> wrote:
> On Fri, 2008-08-22 at 16:35 +0100, Aidan Skinner wrote:
>> On Fri, Aug 22, 2008 at 4:32 PM, Alan Conway <ac...@redhat.com> wrote:
>> > I think the right way to fix this is to change PACKAGE in configure.ac
>> > to qpid-incubating (or even apache-qpid-incubating) That will set the
>> > tarball name and won't break anything (that I can think of) except maybe
>> > downstream scripts that refer to the tarball by name (and they'll break
>> > anyway with the version change.)
>>
>> Excuse my autoconf ignorance here, what does PACKAGE do? I can't find
>> it in configure.ac just now. Does it only affect the tarballs?
>
>
> Aplogies, it's the 2nd arg in:
>
> AC_INIT([qpidc], [0.3], [qpid-dev@incubator.apache.org])
>
> The generated makefiles then get a variable PACKAGE=qpidc
>
> The only things it affects are:
> tarball name (and name of temp dir used to build the tarball)
> obsolete RPM spec file name, no longer in use.
Ah, ok. That makes sense now. :)
- Aidan
--
Apache Qpid - World Domination through Advanced Message Queueing
http://cwiki.apache.org/qpid
"Nine-tenths of wisdom consists in being wise in time." - Theodore Roosevelt
Re: Naming and version numbering (was Re: Problem with your latest
commit)
Posted by Alan Conway <ac...@redhat.com>.
On Fri, 2008-08-22 at 16:35 +0100, Aidan Skinner wrote:
> On Fri, Aug 22, 2008 at 4:32 PM, Alan Conway <ac...@redhat.com> wrote:
> > On Fri, 2008-08-22 at 10:32 +0100, Aidan Skinner wrote:
> >> On Thu, Aug 21, 2008 at 8:22 PM, Alan Conway <ac...@redhat.com> wrote:
> >>
> >> > I haven't made the change in case it needs discussion - we can probably
> >> > find some combo of characters that works if we absolutely must (maybe
> >> > 0.3.incubatorM3 would work...) but I don't feel like farting around
> >> > testing all the things that might break if we can just use a normal,
> >> > sane numeric major.minor version like most of the software universe.
> >>
> >> There's a legal reason for using incubating in the artifcat name[1],
> >> so the tarfile will still have that in there, the spec itself should
> >> be ok as 0.3 though. On graduation we'd need to change our names to
> >> apache-qpid instead of qpid-
> >
> > I think the right way to fix this is to change PACKAGE in configure.ac
> > to qpid-incubating (or even apache-qpid-incubating) That will set the
> > tarball name and won't break anything (that I can think of) except maybe
> > downstream scripts that refer to the tarball by name (and they'll break
> > anyway with the version change.)
>
> Excuse my autoconf ignorance here, what does PACKAGE do? I can't find
> it in configure.ac just now. Does it only affect the tarballs?
Aplogies, it's the 2nd arg in:
AC_INIT([qpidc], [0.3], [qpid-dev@incubator.apache.org])
The generated makefiles then get a variable PACKAGE=qpidc
The only things it affects are:
tarball name (and name of temp dir used to build the tarball)
obsolete RPM spec file name, no longer in use.
I think it's fairly safe to change - downstream scripts that refer to
the tarball name have to be changed anyway with the new version.
Re: Naming and version numbering (was Re: Problem with your latest commit)
Posted by Aidan Skinner <ai...@apache.org>.
On Fri, Aug 22, 2008 at 4:32 PM, Alan Conway <ac...@redhat.com> wrote:
> On Fri, 2008-08-22 at 10:32 +0100, Aidan Skinner wrote:
>> On Thu, Aug 21, 2008 at 8:22 PM, Alan Conway <ac...@redhat.com> wrote:
>>
>> > I haven't made the change in case it needs discussion - we can probably
>> > find some combo of characters that works if we absolutely must (maybe
>> > 0.3.incubatorM3 would work...) but I don't feel like farting around
>> > testing all the things that might break if we can just use a normal,
>> > sane numeric major.minor version like most of the software universe.
>>
>> There's a legal reason for using incubating in the artifcat name[1],
>> so the tarfile will still have that in there, the spec itself should
>> be ok as 0.3 though. On graduation we'd need to change our names to
>> apache-qpid instead of qpid-
>
> I think the right way to fix this is to change PACKAGE in configure.ac
> to qpid-incubating (or even apache-qpid-incubating) That will set the
> tarball name and won't break anything (that I can think of) except maybe
> downstream scripts that refer to the tarball by name (and they'll break
> anyway with the version change.)
Excuse my autoconf ignorance here, what does PACKAGE do? I can't find
it in configure.ac just now. Does it only affect the tarballs?
- Aidan
--
Apache Qpid - World Domination through Advanced Message Queueing
http://cwiki.apache.org/qpid
"Nine-tenths of wisdom consists in being wise in time." - Theodore Roosevelt
Re: Naming and version numbering (was Re: Problem with your latest
commit)
Posted by Alan Conway <ac...@redhat.com>.
On Fri, 2008-08-22 at 10:32 +0100, Aidan Skinner wrote:
> On Thu, Aug 21, 2008 at 8:22 PM, Alan Conway <ac...@redhat.com> wrote:
>
> > I haven't made the change in case it needs discussion - we can probably
> > find some combo of characters that works if we absolutely must (maybe
> > 0.3.incubatorM3 would work...) but I don't feel like farting around
> > testing all the things that might break if we can just use a normal,
> > sane numeric major.minor version like most of the software universe.
>
> There's a legal reason for using incubating in the artifcat name[1],
> so the tarfile will still have that in there, the spec itself should
> be ok as 0.3 though. On graduation we'd need to change our names to
> apache-qpid instead of qpid-
I think the right way to fix this is to change PACKAGE in configure.ac
to qpid-incubating (or even apache-qpid-incubating) That will set the
tarball name and won't break anything (that I can think of) except maybe
downstream scripts that refer to the tarball by name (and they'll break
anyway with the version change.)
> I do think we should also have a discussion about changing from
> milestones to regular (kernel/apr style[2]) numbering for everything
> though, s/M/0/ essentially. So perhaps apache-qpid-0.4.0 for the next
> one maybe?
+1
> Messing with Obsoletes: and the like is probably best done sooner and
> later from downstreams perspective.
+1
Re: Naming and version numbering (was Re: Problem with your latest
commit)
Posted by Alan Conway <ac...@redhat.com>.
On Fri, 2008-08-22 at 12:21 +0100, Aidan Skinner wrote:
> On Fri, Aug 22, 2008 at 12:11 PM, Daniel Kulp <da...@iona.com> wrote:
> > On Friday 22 August 2008 5:32:09 am Aidan Skinner wrote:
> >> On Thu, Aug 21, 2008 at 8:22 PM, Alan Conway <ac...@redhat.com> wrote:
>
> >> There's a legal reason for using incubating in the artifcat name[1],
> >> so the tarfile will still have that in there, the spec itself should
> >> be ok as 0.3 though. On graduation we'd need to change our names to
> >> apache-qpid instead of qpid-
> >>
> >
> > Why wait till graduation? You probably should do that now if you're going to
> > rebuild things (which you have to do for the java stuff at the minimum due to
> > the missing LICENSE/etc...)
>
> A name change like that is going to require a bit of coordination (eg.
> downstream packagers), and it's not something I want to arbitrarily do
> without a bit of discussion first. I also don't want to slip M3 for
> this.
>
AFAIK the only artifact affected by changing the configure.ac PACKAGE
(apart from the tarball name itself) is the name of the RPM .spec file.
That should never have been in the apache project in the first place and
Red Hat isn't using it anymore. I'll remove it to reduce confusion. So
there is probably no downstream impact to changing the name, but...
> Changing the name and version numbering scheme at the same time seems
> like the best bet to me as it leaves us with only one pain point.
It is prudent, so don't feel obliged to change it for M3 unless there's
a compelling reason to do so.
Re: Naming and version numbering (was Re: Problem with your latest commit)
Posted by Aidan Skinner <ai...@apache.org>.
On Fri, Aug 22, 2008 at 12:11 PM, Daniel Kulp <da...@iona.com> wrote:
> On Friday 22 August 2008 5:32:09 am Aidan Skinner wrote:
>> On Thu, Aug 21, 2008 at 8:22 PM, Alan Conway <ac...@redhat.com> wrote:
>> There's a legal reason for using incubating in the artifcat name[1],
>> so the tarfile will still have that in there, the spec itself should
>> be ok as 0.3 though. On graduation we'd need to change our names to
>> apache-qpid instead of qpid-
>>
>
> Why wait till graduation? You probably should do that now if you're going to
> rebuild things (which you have to do for the java stuff at the minimum due to
> the missing LICENSE/etc...)
A name change like that is going to require a bit of coordination (eg.
downstream packagers), and it's not something I want to arbitrarily do
without a bit of discussion first. I also don't want to slip M3 for
this.
Changing the name and version numbering scheme at the same time seems
like the best bet to me as it leaves us with only one pain point.
- Aidan
--
Apache Qpid - World Domination through Advanced Message Queueing
http://cwiki.apache.org/qpid
"Nine-tenths of wisdom consists in being wise in time." - Theodore Roosevelt
Re: Naming and version numbering (was Re: Problem with your latest commit)
Posted by Daniel Kulp <da...@iona.com>.
On Friday 22 August 2008 5:32:09 am Aidan Skinner wrote:
> On Thu, Aug 21, 2008 at 8:22 PM, Alan Conway <ac...@redhat.com> wrote:
> > I haven't made the change in case it needs discussion - we can probably
> > find some combo of characters that works if we absolutely must (maybe
> > 0.3.incubatorM3 would work...) but I don't feel like farting around
> > testing all the things that might break if we can just use a normal,
> > sane numeric major.minor version like most of the software universe.
>
> There's a legal reason for using incubating in the artifcat name[1],
> so the tarfile will still have that in there, the spec itself should
> be ok as 0.3 though. On graduation we'd need to change our names to
> apache-qpid instead of qpid-
>
Why wait till graduation? You probably should do that now if you're going to
rebuild things (which you have to do for the java stuff at the minimum due to
the missing LICENSE/etc...)
Dan
> I do think we should also have a discussion about changing from
> milestones to regular (kernel/apr style[2]) numbering for everything
> though, s/M/0/ essentially. So perhaps apache-qpid-0.4.0 for the next
> one maybe?
>
> Messing with Obsoletes: and the like is probably best done sooner and
> later from downstreams perspective.
>
> - Aidan
>
> [1] http://incubator.apache.org/guides/releasemanagement.html#naming
> [2] http://apr.apache.org/versioning.html
--
Daniel Kulp
daniel.kulp@iona.com
Principal Engineer
IONA Technologies