On Fri, 05 Apr 2013, Carlos R. Mafra escribió: > On Fri, 5 Apr 2013 at 12:20:28 +0200, BALATON Zoltan wrote: > > > > >There were patches to wmbiff recently. What should I do? Write a patch > > >changing the #define version x.y for wmbiff only and announcing that > > >I'm releasing a new wmbiff? > > > > Or just tag the repository with a tag wmbiff-x.y when finished > > merging all the patches and changed the #define in wmbiff to a new > > version. That's what we can call a release: some marked point in the > > repo which can be identified with a version number. > > Ok. I can do that and will do that if that would help how distros > want to do things.
I am not sure about how to do it for Debian. I need read some documents about git + tags + versions. [snip] > > But as I said I don't use the dockapps repo, so it's only a proposal > > and you are free to decide how you do your work and packagers can > > also say if they like this proposal or not. I just though this might > > be an acceptable compromise for both parties. > > I'd like to have some kind of confirmation from packagers that this > could have a chance to work. > > I hope I'm not making things more difficult than they already are, > dockapps.git was meant to simplify things. I think we should remember a bit what happened [1]. We created a repo to pull the "orphaned" dockapps, and have all together, but IMO because that was better for us, (as upstream developers). But, probably that idea was not the best for packagers (for example, the debian/watch file cannot be used to test new versions). I will check if is possible use tags for debian/watch. http://www.mail-archive.com/[email protected]/msg00277.html -- ||// //\\// Rodolfo "kix" Garcia ||\\// //\\ http://www.kix.es/ -- To unsubscribe, send mail to [email protected].
