You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Andrew McIntyre <mc...@gmail.com> on 2008/03/18 20:08:46 UTC

Re: [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by DyreTjeldvoll

On Tue, Mar 18, 2008 at 7:16 AM, Apache Wiki <wi...@apache.org> wrote:
>  +
>  +   /!\ '''Is this still necessary?'''
>  +
>  +   {{{cd tools/release
>  + ant bumplastdigit}}}
>  +
>  +   /!\ '''Commit the changed version number here?'''
>  +

I hadn't caught this question earlier in the previous diffs to the
release wiki page.

To answer this question, the process should be:

* update version to reflect proper version for release candidate,
check it in, run svn update, so that the version reported doesn't
contain an 'M' or a range

* build release candidate, RC then reflects a specific revision in Subversion

* bump the last digit, and commit the version again so that any
further changes to the branch are reflected as not being in the RC
version and sysinfo reports a version that is newer than the RC
version.

There is also a question on the page about running maintversion2props,
I'm pretty sure the build.xml in tools/release handles this, no? Dyre,
if you didn't need to run it separately, please remove the mention of
this tool from the page.

Thanks,
andrew

Re: [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by DyreTjeldvoll

Posted by Dy...@Sun.COM.
Dyre.Tjeldvoll@Sun.COM writes:

> Andrew McIntyre <mc...@gmail.com> writes:
>
>> On Tue, Mar 18, 2008 at 7:16 AM, Apache Wiki <wi...@apache.org> wrote:
>>>  +
>>>  +   /!\ '''Is this still necessary?'''
>>>  +
>>>  +   {{{cd tools/release
>>>  + ant bumplastdigit}}}
>>>  +
>>>  +   /!\ '''Commit the changed version number here?'''
>>>  +
>>
>> I hadn't caught this question earlier in the previous diffs to the
>> release wiki page.
>
> Well, I've put those comments in there more or less as reminders to
> myself, but thanks for looking at it. I was thinking about asking for a
> review of the changes later, perhaps after the release...
>
>> To answer this question, the process should be:
>>
>> * update version to reflect proper version for release candidate,
>> check it in, run svn update, so that the version reported doesn't
>> contain an 'M' or a range
>>
>> * build release candidate, RC then reflects a specific revision in Subversion
>>
>> * bump the last digit, and commit the version again so that any
>> further changes to the branch are reflected as not being in the RC
>> version and sysinfo reports a version that is newer than the RC
>> version.
>
> Thanks :)
>
>> There is also a question on the page about running maintversion2props,
>> I'm pretty sure the build.xml in tools/release handles this, no? 
>
> I think so. At least I noticed that if I deleted
> maintversion.properties before building the release artifacts, it seemed
> to reappear as part of the build process.

Confirmed that maint2props is run by the init target on which all the
relase targets depend.

-- 
dt

Re: [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by DyreTjeldvoll

Posted by Dy...@Sun.COM.
Andrew McIntyre <mc...@gmail.com> writes:

> On Tue, Mar 18, 2008 at 7:16 AM, Apache Wiki <wi...@apache.org> wrote:
>>  +
>>  +   /!\ '''Is this still necessary?'''
>>  +
>>  +   {{{cd tools/release
>>  + ant bumplastdigit}}}
>>  +
>>  +   /!\ '''Commit the changed version number here?'''
>>  +
>
> I hadn't caught this question earlier in the previous diffs to the
> release wiki page.

Well, I've put those comments in there more or less as reminders to
myself, but thanks for looking at it. I was thinking about asking for a
review of the changes later, perhaps after the release...

> To answer this question, the process should be:
>
> * update version to reflect proper version for release candidate,
> check it in, run svn update, so that the version reported doesn't
> contain an 'M' or a range
>
> * build release candidate, RC then reflects a specific revision in Subversion
>
> * bump the last digit, and commit the version again so that any
> further changes to the branch are reflected as not being in the RC
> version and sysinfo reports a version that is newer than the RC
> version.

Thanks :)

> There is also a question on the page about running maintversion2props,
> I'm pretty sure the build.xml in tools/release handles this, no? 

I think so. At least I noticed that if I deleted
maintversion.properties before building the release artifacts, it seemed
to reappear as part of the build process.

> Dyre, if you didn't need to run it separately, please remove the
> mention of this tool from the page.

Will do. Thanks.

-- 
dt