I see it the same way ... after all I thing the binary release would be 
identical down to the last 1 and 0

Just to note about what would have to be done in order to stage a new release:
- Drop the current staging repository
- Update the version back to 1.0.0 
- Commit that change
- Create a new Tag in GIT
- Deploy to a new Staging repository
- Cast a new Vote

All for getting a bit-identical version of the lib. If anyone insists on this, 
I'll do it.

I'll wait till tomorrow and if none objects, I'll close the staging repo and 
set it to release.
But I have to admit that I don't quite know what has to be done then. I write a 
Mail and send that to which lists? Do I have to copy the source-release.zip 
anywhere?

Chris

________________________________________
Von: Erik de Bruin <e...@ixsoftware.nl>
Gesendet: Samstag, 15. November 2014 05:40
An: dev@flex.apache.org
Betreff: Re: AW: [FlexJS] First successful build of a FlexJS application using 
Flexmojos

We just can't help ourselves. can we?

With 4 +1 and 2 +0 binding votes, we have a very valid release. Let's leave
it at that, so the other sub-projects can benefit from this release, and
not try to make a big deal of improvements that don't affect the utility of
this utility at all. If the tool can be improved upon, let's create a 1.1
with fixes and release that ...

EdB



On Fri, Nov 14, 2014 at 7:36 PM, OmPrakash Muppirala <bigosma...@gmail.com>
wrote:

> >
> > All it would take is create a new RC build and upload the artifacts to
> the
> > dist site.
> >
>
> I take that back.  I forgot we are releasing via maven.  Even so, I think
> we should make one more RC.
>
> Thanks,
> Om
>
>
> > On Fri, Nov 14, 2014 at 5:09 PM, Christofer Dutz <
> > christofer.d...@c-ware.de> wrote:
> >
> >> Well you were right ... it pushed my tag ... was sort of expecting that
> >> to happen automatically ... well ... you never stop learning :-)
> >>
> >> I doubt that it makes sense to release something just for releasing the
> >> changes to the release procedure, so if it's up to me, I don't need
> another
> >> release ;-)
> >>
> >> I was more thinking of using the lessons learned when releasing other
> >> parts.
> >>
> >> Chris
> >>
> >> ________________________________________
> >> Von: Alex Harui <aha...@adobe.com>
> >> Gesendet: Freitag, 14. November 2014 22:35
> >> An: dev@flex.apache.org
> >> Betreff: Re: AW: [FlexJS] First successful build of a FlexJS application
> >> using Flexmojos
> >>
> >> On 11/14/14, 1:13 PM, "Christofer Dutz" <christofer.d...@c-ware.de>
> >> wrote:
> >>
> >> >Hi,
> >> >
> >> >Actually I did create that tag ... wonder why it wasn't transferred to
> >> >the Apache Git ... do Tags not get pushed automatically?
> >>
> >> I think in Git you need to "push --tags”.
> >>
> >> >
> >> >I would suggest to release the staged ones and use the optimized pom
> for
> >> >the next release.
> >>
> >> OK, but is there going to be a next release?  I was hoping for
> >> one-and-done.
> >>
> >> -Alex
> >>
> >
> >
>



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Reply via email to