Masterview devel - Jun 2006 - creating masterview release tag, latest won''t work properly for script/plugin install

Jeff - that''s fine, i wasn''t wild about
''latest'' anyway.
 
Please note the other tag I just installed in the repository so that
there''s
a clear record of release configurations: masterview-0.1.5 to archive the
config of the last build you did.
 
When we release a new build, I''ld like the procedure and repos tagging
to
be:
 
(1) prereq: ensure that lib/masterview_version.rb is in synch with the
package number on the release build artifacts - something''s a bit out
of
whack in the current tags/masterview config - last release was 0.1.5, but I
see 0.1.4 out there in the code, so not quite sure whether that''s a
correct
config.  If our current build process doesn''t automatically ensure that
the
-version.rb is in synch with the build number then we need to fix something.
 
[ignore this comment if that''s already the case and the repos tag is
just
funky because we''re sorting out how to get it set up properly]
 
(2) repository entry ''tags/masterview-M.N.X'' gets copied from
the trunk in
synch with publication of the packaged release files (gems and zips) onto
the rubyforge project site.  Believe this can/should be automated with rake
task that become part of our build process.
 
(3) repository entry ''tags/masterview'' is reset to the new
stable build
release (delete, then make copy of new release build tag...)
 
~ Deb

  _____  

From: masterview-commits-bounces at rubyforge.org
[mailto:masterview-commits-bounces at rubyforge.org] On Behalf Of Jeff
Barczewski
Sent: Wednesday, June 07, 2006 5:35 AM
To: masterview-commits at rubyforge.org
Subject: Re: [Masterview-commits] [68] tags/masterview/: creating
masterviewrelease tag,latest won''t work properly for script/plugin
install
(it puts thefile in vendor/plugins/latest rather than masterview)


I found out that 

script/plugin install svn://rubyforge.org/var/svn/masterview/tags/latesst
installs in vendor/plugins/latest so we need to actually create a tag called
masterview instead of latest. 

Once I get done updating the urls on the web to this I will get rid of the
latest tag. 

Jeff

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060607/23229720/attachment.htm

Sounds good. Yes the current build process will use the version out of
mastervie_version.rb to build, so I always update it whenvever I want to do
a new build.

On 6/7/06, Deb Lewis <djlewis at acm.org> wrote:
>
>  Jeff - that''s fine, i wasn''t wild about
''latest'' anyway.
>
> Please note the other tag I just installed in the repository so that
> there''s a clear record of release configurations: masterview-0.1.5
to
> archive the config of the last build you did.
>
> When we release a new build, I''ld like the procedure and repos
tagging
> to be:
>
> (1) prereq: ensure that lib/masterview_version.rb is in synch with the
> package number on the release build artifacts - something''s a bit
out of
> whack in the current tags/masterview config - last release was 0.1.5, but
> I see 0.1.4 out there in the code, so not quite sure whether
that''s a
> correct config.  If our current build process doesn''t
automatically ensure
> that the -version.rb is in synch with the build number then we need to fix
> something.
>
> [ignore this comment if that''s already the case and the repos tag
is just
> funky because we''re sorting out how to get it set up properly]
>
> (2) repository entry ''tags/masterview-M.N.X'' gets copied
from the trunk in
> synch with publication of the packaged release files (gems and zips) onto
> the rubyforge project site.  Believe this can/should be automated with rake
> task that become part of our build process.
>
> (3) repository entry ''tags/masterview'' is reset to the
new stable build
> release (delete, then make copy of new release build tag...)
>
> ~ Deb
>
>  ------------------------------
> *From:* masterview-commits-bounces at rubyforge.org [mailto:
> masterview-commits-bounces at rubyforge.org] *On Behalf Of *Jeff Barczewski
> *Sent:* Wednesday, June 07, 2006 5:35 AM
> *To:* masterview-commits at rubyforge.org
> *Subject:* Re: [Masterview-commits] [68] tags/masterview/: creating
> masterviewrelease tag,latest won''t work properly for script/plugin
install
> (it puts thefile in vendor/plugins/latest rather than masterview)
>
> I found out that
>
> script/plugin install svn://rubyforge.org/var/svn/masterview/tags/latesst
> installs in vendor/plugins/latest so we need to actually create a tag
called
> masterview instead of latest.
>
> Once I get done updating the urls on the web to this I will get rid of the
> latest tag.
>
> Jeff
>
> _______________________________________________
> Masterview-devel mailing list
> Masterview-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060607/1c5783e9/attachment.htm