| +1 
On 17 Dec 2010, at 16:59, Dmitry Sklyut wrote: In that case how about 1.0.0.M01?
 0.9.0 means a lot of changes in the tests and manifests and plans. 
 I will set-up documentation project and this will keep version stable.  How about it? 
 Thanks _______________________________________________Dmitry On Fri, Dec 17, 2010 at 11:53 AM, Glyn Normington <gnormington@xxxxxxxxxx>  wrote:
 Hi Dmitry 
 Of course I forgot to mention the obvious. If we want to release snaps, snaps must go through a release review. 
 The alternative, if you simply want to get binaries out there, is to ship (don't use the 'r' word) a milestone such as 0.9.0.M01. 
On 17 Dec 2010, at 14:45, Dmitry Sklyut wrote: Agree.  Bad boy is to be versioned with 0.9.0.RELEASE until documentation comes online.
 I just really think it is time for snaps to have a binary release and not force users to build from sources. 
 _______________________________________________Hmmm...  What about 0.9.0.RELESE-BAD-BOY.  Would be a valid OSGi qualifier.  :) On Fri, Dec 17, 2010 at 9:40 AM, Glyn Normington <gnormington@xxxxxxxxxx>  wrote:
 Snaps is not production ready as it doesn't have any documentation, e.g. to describe the limitations. ;-) 
On 17 Dec 2010, at 14:39, Christopher Frost wrote: 
_______________________________________________
    Hi, 
    Well, seeing as it's still just a bad boy and not a bad man yet, how
    about 0.9.0.RELEASE
     
    Unless you feel he's production ready?
     
    Chris.
     
    On 17/12/2010 14:26, Dmitry Sklyut wrote:
     I am almost there.  Just wondering what version to
      release that bad boy with?
      
 1.0.0.RELEASE? 2.1.0.RELEASE? 
 Regards, 
        Dmitry
        
         On Thu, Dec 16, 2010 at 9:27 AM,
          Christopher Frost <frostc@xxxxxxxxxx> 
          wrote:
           
             Yes, this should be
              easy enough. 
              Your welcome to do this yourself Dmitry. Once you have
              stuck you ssh keys on the eclipse servers, git/build and
              build as the virgoBuild user. You will be able to do a
              release, the procedure for releasing a single repo is on
              the wiki, bottom of the build tab.
               
              I'm happy to do it as well though, raise a bug if you
              like.
               
              Chris.
               
                
                  
                  On 16/12/2010 08:35, Glyn Normington wrote:
                   
                    Hi Dmitry
Yes, tag away!
We have weaned ourselves off publishing to zodiac since non-SpringSource committers cannot be given our S3 keys. I'll leave it to Chris, our build meister, to discuss the remaining options...
Regards,
Glyn
On 15 Dec 2010, at 18:59, Dmitry Sklyut wrote:
 
                      Hi All,
Do you think it is time to take a snapshot of snaps and tag it as compatible with 2.1.0.RELEASE?
It would be great also if snaps got published to some maven/ivy repo.  Right now I can't find it in zodiac.
Building it from source is getting to be a bit cumbersome :)
Regards,
Dmitry
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
 _______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
_______________________________________________
 virgo-dev mailing list
 virgo-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/virgo-dev
 
 
virgo-dev mailing list
 virgo-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/virgo-dev
 
_______________________________________________
 virgo-dev mailing list
 virgo-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/virgo-dev
 
 
virgo-dev mailing list
 virgo-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/virgo-dev
 
_______________________________________________
 virgo-dev mailing list
 virgo-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/virgo-dev
 
 
virgo-dev mailing list
 virgo-dev@xxxxxxxxxxx
 https://dev.eclipse.org/mailman/listinfo/virgo-dev
 
 |