[aerogear-dev] Data-Sync: Versioning in JIRA

Matthias Wessendorf matzew at apache.org
Fri Jan 16 04:45:19 EST 2015


Here is a filter, for all the JIRAs that are now labeled as "
sync-1.0.0.alpha.1":

https://issues.jboss.org/issues/?filter=12323088

-Matthias

On Thu, Jan 15, 2015 at 4:29 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> +1
> > On 15 Jan 2015, at 14:35, Lucas Holmquist <lholmqui at redhat.com> wrote:
> >
> > yup,  labels should work
> >> On Jan 15, 2015, at 12:59 AM, Daniel Bevenius <
> daniel.bevenius at gmail.com> wrote:
> >>
> >> +1 Sounds good using a label.
> >>
> >> On 15 January 2015 at 06:21, Matthias Wessendorf <matzew at apache.org>
> wrote:
> >>
> >>
> >> On Wed, Jan 14, 2015 at 8:22 PM, Summers Pittman <supittma at redhat.com>
> wrote:
> >> On 01/14/2015 12:04 PM, Matthias Wessendorf wrote:
> >>> Hi,
> >>>
> >>> moving forward with the data-sync, inside of JIRA, I'd need to create
> versions like:
> >>> *sync-1.0.0.alpha.1
> >>> *sync-1.0.0.alpha.2,
> >>> * ...,
> >>> *...beta.1,
> >>> "sync-1.0.0.final"
> >>>
> >>> Do these versions, across JIRA instances (AGJS, AGDROID, AGOIS and
> AEROGEAR) make sense? Or is there a different preference?
> >> So we would have components in the project with versions separate from
> the release version in the project?
> >>
> >> Good point :-)
> >>
> >> Actually, let's keep the versions as they are (makes things easier) but
> we could use the "sync-1.0.0.alpha.1" etc simply as a label. The benefit
> would be the same: you click on a specific label (e.g. sync-1.0.0.alpha.1)
> and get a list of all JIRA tickets, labeled with that label, across
> different JIRA instances.
> >>
> >> So new things for SYNC would be still versioned AGDROID-2.x.y, but just
> get a "sync-1.0.0.alpha.1" label.
> >>
> >> For the 1.0.0.Final of UPS we used the same process, and it worked very
> well
> >>
> >>>
> >>> Thanks,
> >>> Matthias
> >>>
> >>>
> >>> --
> >>> Matthias Wessendorf
> >>>
> >>> blog: http://matthiaswessendorf.wordpress.com/
> >>> sessions: http://www.slideshare.net/mwessendorf
> >>> twitter: http://twitter.com/mwessendorf
> >>>
> >>>
> >>> _______________________________________________
> >>> aerogear-dev mailing list
> >>>
> >>> aerogear-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >>
> >> --
> >> Summers Pittman
> >> >>Phone:
> >> 404 941 4698
> >>
> >> >>Java is my crack.
> >>
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150116/927f4f9b/attachment.html 


More information about the aerogear-dev mailing list